Bugzilla #39846, #39847:

Nits
Submitted by: Patrick Paul <ppaul_apache.at.yahoo.ca>

git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@415932 13f79535-47bb-0310-9956-ffa450edef68

examples/fo/build.xml

@@ -105,7 +105,7 @@
     </antcall>
   </target>
   <!-- =================================================================== -->
-  <!-- Produces new test areatree files                                         -->
+  <!-- Produces new test areatree files                                    -->
   <!-- =================================================================== -->
   <target name="newAT" depends="init" description="Creates a new set of AreaTree XML test files">
     <antcall target="newTestFiles">
@@ -121,7 +121,7 @@
     <compare referenceDirectory="${referenceDir}" testDirectory="${testDir}" filenames="normal.pdf,table.pdf,list.pdf,link.pdf,border.pdf,images.pdf,extensive.pdf,readme.pdf,fonts.pdf,bordershorthand.pdf,character.pdf,corresprop.pdf,hyphen.pdf,inhprop.pdf,instream.pdf,leader.pdf,newlinktest.pdf,normalex.pdf,pdfoutline.pdf,simple.pdf,textdeko.pdf,tableunits.pdf"/>
   </target>
   <!-- =================================================================== -->
-  <!-- Produces new reference pdf files                                         -->
+  <!-- Produces new reference pdf files                                    -->
   <!-- =================================================================== -->
   <target name="referencePDF" depends="init">
     <antcall target="newTestFiles">

src/documentation/content/xdocs/dev/conventions.xml

@@ -27,7 +27,7 @@
       <title>Subversion Repository</title>
       <p>Conventions in this section apply to Repository content, regardless of type:</p>
       <ul>
-        <li>Files checked in must conform to the code conventions for that type of file (java files must conform to java requirements, xml to xml requirements, etc.). If a submitted patch does not conform, it is the responsibility of the committer to bring it into conformance before checking it in. Developers submitting patches are encouraged to follow the code conventions to reduce the work load on the the committers.</li>
+        <li>Files checked in must conform to the code conventions for that type of file (java files must conform to java requirements, xml to xml requirements, etc.). If a submitted patch does not conform, it is the responsibility of the committer to bring it into conformance before checking it in. Developers submitting patches are encouraged to follow the code conventions to reduce the work load on the committers.</li>
         <li>To reduce the amount of spurious deltas, all text (non-binary) files checked into SVN must have Unix-style line endings (LF only). Many IDEs and editors (even on non-Unix platforms) have settings that can facilitate this convention.</li>
         <li>In order to be able to discern commits from a committer from those where a committer applied a patch from a contributor, the commit message must contain a separate line following this pattern: <strong>"Submitted by: [contributor's name] &lt;[contributor's obfuscated e-mail address]&gt;"</strong>. This also helps doing audits on the repository.</li>
       </ul>