more lowercasing and other style adjustments

7 years ago · ecc6994f7e
--- a/manual/Tasks/ejb.html
+++ b/manual/Tasks/ejb.html
@@ -534,7 +534,7 @@ to extract all dependent classes. This means that, in addition to the classes th
 the deployment descriptor, any classes that these depend on are also automatically included in the
 jar file.</p>

 <h3 id="naming">Naming Convention</h3>
 <h3 id="naming">Naming convention</h3>

 <code>Ejbjar</code> handles the processing of multiple beans, and it uses a set of naming
 conventions to determine the name of the generated EJB jars. The naming convention that is used is
@@ -716,7 +716,7 @@ not, <code>ejbjar</code> will drop back to the behaviour corresponding to the va
 <p>In addition to the vendor specific nested elements, the <code>ejbjar</code> task provides three
 nested elements.</p>

 <h4>Classpath</h4>
 <h4>classpath</h4>

 <p>The <code>&lt;classpath&gt;</code> nested element allows the classpath to be set. It is useful
 when setting the classpath from a reference path. In all other respects the behaviour is the same as
--- a/manual/Tasks/ftp.html
+++ b/manual/Tasks/ftp.html
@@ -393,7 +393,7 @@ files to be retrieved, or deleted, or listed, or whose mode you want to change.<
 to <q>false</q>.</em>  On remote filesets hidden files are not checked for being symbolic links.
 Hidden files are currently assumed to not be symbolic links.</p>

 <h3>Sending Files</h3>
 <h3>Sending files</h3>
 <p>The easiest way to describe how to send files is with a couple of examples:</p>
 <pre>
 &lt;ftp server="ftp.apache.org"
@@ -465,7 +465,7 @@ the <samp>/pub/incoming</samp> directory. The files are transferred in text mode
 password <samp>java1</samp> and uploads all HTML files in the <samp>htdocs/manual</samp> directory
 to the <samp>c:\uploads</samp> directory.  Progress messages are displayed as each file is
 uploaded.</p>
 <h3>Getting Files</h3>
 <h3>Getting files</h3>
 <p>Getting files from an FTP server works pretty much the same way as sending them does.  The only
 difference is that the nested filesets use the <var>remotedir</var> attribute as the base directory
 for the files on the FTP server, and the <var>dir</var> attribute as the local directory to put the
@@ -514,7 +514,7 @@ names in Standard European format, as <samp>anonymous</samp>, and recursively do
 all <samp>.html</samp> files from default directory for that user into
 the <samp>htdocs/manual</samp> directory on the local machine.</p>

 <h3>Deleting Files</h3>
 <h3>Deleting files</h3>
 <p>As you've probably guessed by now, you use nested fileset elements to select the files to delete
 from the remote FTP server.  Again, the filesets are relative to the remote directory, not a local
 directory.  In fact, the <var>dir</var> attribute of the fileset is ignored completely.</p>
@@ -546,7 +546,7 @@ to delete a file, a BuildException is thrown.</p>
 relative to the default directory of the <samp>anonymous</samp> user. The listing is in whatever
 format the FTP server normally lists files.</p>

 <h3>Creating Directories</h3>
 <h3>Creating directories</h3>
 <p>Note that with the <q>mkdir</q> action, the directory to create is specified using
 the <var>remotedir</var> attribute.</p>
 <pre>
@@ -558,7 +558,7 @@ the <var>remotedir</var> attribute.</p>
 <p>This creates the directory <samp>some/remote/dir</samp> beneath the default root directory.  As
 with all other actions, the directory separator character must be correct according to the desires
 of the FTP server.</p>
 <h3>Removing Directories</h3>
 <h3>Removing directories</h3>
 <p>This action uses nested fileset elements to select the directories to remove from the remote FTP
 server.  The filesets are relative to the remote directory, not a local directory.
 The <var>dir</var> attribute of the fileset is ignored completely.  The directories to be removed
--- a/manual/Tasks/image.html
+++ b/manual/Tasks/image.html
@@ -117,7 +117,7 @@ and <code>&lt;patternset&gt;</code> elements.</p>

 <h4>ImageOperation</h4>
 <p>Adds an ImageOperation to chain.</p>
 <h5>Nested Elements</h5>
 <h5>Nested elements</h5>
 <p>ImageOperation can handle
 nested <code>Rotate</code>, <code>Draw</code>, <code>Rectangle</code>, <code>Text</code>
 and <code>Scale</code> objects.</p>
--- a/manual/Tasks/import.html
+++ b/manual/Tasks/import.html
@@ -65,7 +65,7 @@
    overridden target's name instead of the <var>name</var> attribute of the <code>project</code>
    tag.</p>

  <h4>Special Properties</h4>
  <h4>Special properties</h4>

  <p>Imported files are treated as they are present in the main buildfile. This makes it easy to
    understand, but it makes it impossible for them to reference files and resources relative to
--- a/manual/Tasks/include.html
+++ b/manual/Tasks/include.html
@@ -62,7 +62,7 @@
  <p><code>&lt;import&gt;</code> contribute to the prefix as well, but only if their <var>as</var>
    attribute has been specified.

    <h4>Special Properties</h4>
  <h4>Special properties</h4>

  <p>Included files are treated as they are present in the main buildfile. This makes it easy to
    understand, but it makes it impossible for them to reference files and resources relative to
--- a/manual/Tasks/javac.html
+++ b/manual/Tasks/javac.html
@@ -668,7 +668,7 @@ compilation module set.  The <code>{ ... , ... }</code> express alternates for e
 compilation uses application modules located in <code>modules</code> folder.The source level
 is <q>9</q> to enable modules.</p>

 <h3>Jikes Notes</h3>
 <h3>Jikes notes</h3>

 <p>You need Jikes 1.15 or later.</p>

@@ -710,13 +710,13 @@ are <q>false</q>.</p>
  </tr>
 </table>

 <h3>Jvc Notes</h3>
 <h3>Jvc notes</h3>

 <p><q>Jvc</q> will enable Microsoft extensions unless you set the
 property <code>build.compiler.jvc.extensions</code> to <q>false</q> before
 invoking <code>&lt;javac&gt;</code>.</p>

 <h3 id="bootstrap">Bootstrap Options</h3>
 <h3 id="bootstrap">Bootstrap options</h3>
 <p>The Sun <code>javac</code> compiler has a <code>bootclasspath</code> command line
 option&mdash;this corresponds to the <var>bootclasspath</var> attribute/element of
 the <code>&lt;javac&gt;</code> task. The Sun compiler also allows more control over the boot
@@ -733,7 +733,7 @@ references to strings that can by used in an OS independent fashion
  &lt;compilerarg arg="-Xbootclasspath/p:${toString:lib.path.ref}"/&gt;
 &lt;/javac&gt;</pre>

 <h3>OpenJDK Notes</h3>
 <h3>OpenJDK notes</h3>
 <p>The <a href="http://openjdk.java.net/">openjdk</a> project has provided
 the <code>javac</code> <a href="http://openjdk.java.net/groups/compiler/">compiler</a> as an open
 source project. The output of this project is a <code>javac.jar</code> which contains
--- a/manual/Tasks/jjtree.html
+++ b/manual/Tasks/jjtree.html
@@ -160,7 +160,7 @@ file as the JJTree grammar file with a suffix <samp>.jj</samp>.</p>
 file, <samp>Parser.jj</samp>, file to <samp>build/src</samp>. The grammar option NODE_USES_PARSER is
 set to <q>true</q> when invoking JJTree.</p>

 <h3>Comparison output locations between command line JJTree and different Ant <code>taskdef</code>
 <h3>Comparison of output locations between command line JJTree and different Ant <code>taskdef</code>
 versions</h3>

 <table>
--- a/manual/Tasks/junitreport.html
+++ b/manual/Tasks/junitreport.html
@@ -119,7 +119,7 @@ using the nested <a href="../Types/fileset.html"><code>&lt;FileSet&gt;</code></a
 <p>Custom versions of <samp>junit-frames.xsl</samp> or <samp>junit-noframes.xsl</samp> must adhere
 to the above conventions.</p>

 <h3>Nested Element of the report tag</h3>
 <h3>Nested element of the report tag</h3>
 <h4>param</h4>
 <p><em>Since Ant 1.7</em>, the <var>report</var> tag supports nested <code>param</code> tags.  These
 tags can pass XSL parameters to the stylesheet.</p>
@@ -189,15 +189,15 @@ nested <code>&lt;factory&gt;</code> can be used to specify factory settings.</p>
 <p>would generate a <samp>TESTS-TestSuites.xml</samp> file in the directory <samp>reports</samp> and
 generate the default framed report in the directory <samp>report/html</samp>.</p>

 <h3>Example of report with xsl params</h3>
 <h3>Example of report with XSL params</h3>
 <pre>
 &lt;junitreport todir="${outputdir}"&gt;
    &lt;fileset dir="${jrdir}"&gt;
        &lt;include name="TEST-*.xml"/&gt;
    &lt;/fileset&gt;
    &lt;report todir="${outputdir}/html"
        styledir="junitreport"
        format="frames"&gt;
            styledir="junitreport"
            format="frames"&gt;
        &lt;param name="key1" expression="value1"/&gt;
        &lt;param name="key2" expression="value2"/&gt;
    &lt;/report&gt;
--- a/manual/Tasks/macrodef.html
+++ b/manual/Tasks/macrodef.html
@@ -82,7 +82,7 @@
      properties.</p>
    <p>The case of the attribute is ignored, so <code>@{myAttribute}</code> is treated the same
      as <code>@{MyAttribute}</code>.</p>
    <h3>Parameters</h3>
    <h5>Parameters</h5>
    <table class="attr">
      <tr>
        <th>Attribute</th>
@@ -117,7 +117,7 @@
    <p>This is used to specify nested elements of the new task.  The contents of the nested elements
      of the task instance are placed in the templated task at the tag name.</p>
    <p>The case of the <code>element</code> name is ignored.</p>
    <h3>Parameters</h3>
    <h5>Parameters</h5>
    <table class="attr">
      <tr>
        <th>Attribute</th>
@@ -155,7 +155,7 @@
      the <code>text</code> element is present, then the name becomes an attribute that gets set to
      the nested text of the macro invocation.  <em>Since Ant 1.6.1</em>.</p>
    <p>The case of the <code>text</code> name is ignored.</p>
    <h3>Parameters</h3>
    <h5>Parameters</h5>
    <table class="attr">
      <tr>
        <th>Attribute</th>
--- a/manual/Tasks/property.html
+++ b/manual/Tasks/property.html
@@ -236,7 +236,7 @@ personal settings with a file per user.</p>
 <pre>&lt;property name=&quot;foo&quot; location=&quot;my/file.txt&quot; relative=&quot;true&quot; basedir=&quot;cvs&quot;/&gt;</pre>
 <p>Stores the relative path in <code>foo</code>: <samp>cvs/my/file.txt</samp></p>

 <h3>Property Files</h3>
 <h3>Property files</h3>

 <p>As stated, this task will load in a properties file stored in the file system, or as a resource
 on a classpath. Here are some interesting facts about this feature</p>
--- a/manual/Tasks/pvcstask.html
+++ b/manual/Tasks/pvcstask.html
@@ -166,7 +166,7 @@ project within the PVCS repository to extract files from.  By nesting
 multiple <code>&lt;pvcsproject&gt;</code> elements under the <code>&lt;pvcs&gt;</code> task,
 multiple projects can be specified.</p>

 <h3>Parameters</h3>
 <h5>Parameters</h5>

 <table class="attr">
  <tr>
--- a/manual/Tasks/replace.html
+++ b/manual/Tasks/replace.html
@@ -138,7 +138,7 @@ based <a href="../Types/resources.html#collection">resource collections</a> as n
 <p>If either the text you want to replace or the replacement text cross line boundaries, you can use
 nested elements to specify them.</p>
 <p>The elements support attributes:</p>
 <table>
 <table class="attr">
  <tr>
    <th>Attribute</th>
    <th>Description</th>
--- a/manual/Tasks/rmic.html
+++ b/manual/Tasks/rmic.html
@@ -72,11 +72,10 @@ documentation to learn how to use it.</p>

 <h4>CORBA support</h4>

 <p>Java 11 removes the CORBA and JavaEE packages and rmic no longer
  supports either <code>iiop</code> nor <code>idl</code>. Starting
  with Ant 1.10.3 the rmic task will fail when using either while
  running Java11+ unless you fork the task and explicitly specify an
  executable.</p>
 <p>Java 11 removes the CORBA and JavaEE packages and <code>rmic</code> no longer supports
 either <code>iiop</code> nor <code>idl</code>. Starting with Ant 1.10.3, the <code>rmic</code> task
 will fail when using either while running Java 11+ unless you fork the task and explicitly specify an
 executable.</p>

 <h3>Parameters</h3>
 <table class="attr">
@@ -163,8 +162,8 @@ documentation to learn how to use it.</p>
  </tr>
  <tr>
    <td>iiop</td>
    <td>indicates that portable (RMI/IIOP) stubs should be
      generated.<br/>  See the note on CORBA support above.</td>
    <td>indicates that portable (RMI/IIOP) stubs should be generated.<br/>  See the note on CORBA
      support above.</td>
    <td>No</td>
  </tr>
  <tr>
@@ -174,8 +173,8 @@ documentation to learn how to use it.</p>
  </tr>
  <tr>
    <td>idl</td>
    <td>indicates that IDL output files should be generated.<br/>  See
      the note on CORBA support above.</td>
    <td>indicates that IDL output files should be generated.<br/>  See the note on CORBA support
      above.</td>
    <td>No</td>
  </tr>
  <tr>
--- a/manual/Tasks/scriptdef.html
+++ b/manual/Tasks/scriptdef.html
@@ -280,7 +280,7 @@ beanshell jar.</p>
 &lt;b1 a="this is an 'a'"/&gt;
 &lt;b2 a2="this is an 'a2' for b2"/&gt;</pre>

 <h3>Testing Scripts</h3>
 <h3>Testing scripts</h3>

 <p>The easiest way to test scripts is to use
 the <a href="https://ant.apache.org/antlibs/antunit/">AntUnit</a> Ant library.  This will run all
--- a/manual/Tasks/serverdeploy.html
+++ b/manual/Tasks/serverdeploy.html
@@ -91,6 +91,8 @@ classpath.</p>

 <h3>Vendor-specific nested elements</h3>

 <p>Also supported are nested vendor-specific elements.</p>

 <h3>Parameters used for all tools</h3>
 <table class="attr">
  <tr>
@@ -121,8 +123,6 @@ classpath.</p>
  </tr>
 </table>

 <p>Also supported are nested vendor-specific elements.</p>

 <h3 id="serverdeploy_generic">Generic element</h3>
 <p>This element is provided for generic Java-based deployment tools.  The generic task accepts (but
 does not require) nested <code>arg</code> and <code>jvmarg</code> elements.  A JVM will be spawned
@@ -142,7 +142,7 @@ generic one if at all possible.</p>
  </tr>
 </table>

 <h3>Nested Elements</h3>
 <h4>Nested elements</h4>
 <p>The generic element supports nested <code>&lt;arg&gt;</code> and <code>&lt;jvmarg&gt;</code>
 elements.</p>

@@ -269,7 +269,7 @@ tool.</p>
  </tr>
 </table>

 <h3>Nested Elements</h3>
 <h4>Nested elements</h4>
 <p>The <code>jonas</code> element supports nested <code>&lt;arg&gt;</code>
 and <code>&lt;jvmarg&gt;</code> elements.</p>

--- a/manual/Tasks/sound.html
+++ b/manual/Tasks/sound.html
@@ -41,10 +41,11 @@ executed.</p>
 <h3>Parameters specified as nested elements</h3>
 <h4>success</h4>
 <p>Specifies the sound to be played if the build succeeded.</p>

 <h4>fail</h4>
 <p>Specifies the sound to be played if the build failed.</p>

 <h3>Nested element parameters</h3>
 <h4>Nested element parameters</h4>
 <p>The following attributes may be used on the <code>&lt;success&gt;</code>
 and <code>&lt;fail&gt;</code> elements:</p>
 <table class="attr">
--- a/manual/Tasks/sync.html
+++ b/manual/Tasks/sync.html
@@ -101,7 +101,7 @@ present in one of the source directories.</p>
 support the <var>dir</var> attribute and the <var>usedefaultexcludes</var> attribute defaults
 to <q>false</q>.</p>

 <h5>Additional Parameters</h5>
 <h5>Additional parameters</h5>
 <table class="attr">
  <tr>
    <th>Attribute</th>
--- a/manual/Tasks/xmlproperty.html
+++ b/manual/Tasks/xmlproperty.html
@@ -38,7 +38,7 @@
 <p>By default, this load does <em>no</em> processing of the input.  In particular, unlike
 the <a href="property.html">Property task</a>, property references (i.e., <samp>${foo}</samp>) are
 not resolved.</p>
 <h3 id="semanticAttributes">Semantic Attributes</h3>
 <h3 id="semanticAttributes">Semantic attributes</h3>
 <p>Input processing can be enabled by using the <var>semanticAttributes</var> attribute.  If this
 attribute is set to <q>true</q> (its default is <q>false</q>), the following processing occurs as
 the input XML file is loaded:/p>
@@ -143,9 +143,9 @@ perform entity resolution.</p>

 <h3 id="examples">Examples</h3>

 <h4>Non-semantic Attributes</h4>
 <h4>Non-semantic attributes</h4>

 <p>Here is an example xml file that does not have any semantic attributes.</p>
 <p>Here is an example XML file that does not have any semantic attributes.</p>

 <pre>
 &lt;root-tag myattr="true"&gt;
@@ -163,7 +163,7 @@ root-tag.inner-tag=Text
 root-tag.inner-tag(someattr)=val
 root-tag.a2.a3.a4=false</pre>

 <h5>collapseAttributes=false</h5>
 <h5><var>collapseAttributes</var>=<q>false</q></h5>
 <p>This entry in a build file:</p>
 <pre>&lt;xmlproperty file="somefile.xml" collapseAttributes="true"/&gt;</pre>
 <p>is equivalent to the following properties:</p>
@@ -173,7 +173,7 @@ root-tag.inner-tag=Text
 root-tag.inner-tag.someatt=val
 root-tag.a2.a3.a4=false</pre>

 <h5>keepRoot=false</h5>
 <h5><var>keepRoot</var>=<q>false</q></h5>
 <p>This entry in a build file:</p>
 <pre>&lt;xmlproperty file="somefile.xml" keepRoot="false"/&gt;</pre>
 <p>is equivalent to the following properties:</p>
@@ -182,9 +182,9 @@ inner-tag=Text
 inner-tag(someattr)=val
 a2.a3.a4=false</pre>

 <h4>Semantic Attributes</h4>
 <h4>Semantic attributes</h4>

 <p>Here is an example xml file that has semantic attributes.</p>
 <p>Here is an example XML file that has semantic attributes.</p>
 <pre>
 &lt;root-tag&gt;
  &lt;version value="0.0.1"/&gt;
@@ -206,7 +206,7 @@ a2.a3.a4=false</pre>
  &lt;/run-time&gt;
 &lt;/root-tag&gt;</pre>

 <h5>default loading (semanticAttributes=true)</h5>
 <h5>default loading (<var>semanticAttributes</var>=<q>true</q>)</h5>
 <p>This entry in a build file:</p>
 <pre>
 &lt;xmlproperty file="somefile.xml" keepRoot="false"
@@ -229,7 +229,7 @@ a2.a3.a4=false</pre>
  &lt;pathelement path="${run-time.jars}"/&gt;
 &lt;/path&gt;</pre>

 <h5>includeSemanticAttribute="true"</h5>
 <h5><var>includeSemanticAttribute</var>=<q>true</q></h5>
 <p>This entry in a build file:</p>
 <pre>
 &lt;xmlproperty file="somefile.xml"
--- a/manual/Tasks/zip.html
+++ b/manual/Tasks/zip.html
@@ -258,7 +258,7 @@ extract an Ant generated ZIP archive.</p>
  </tr>
 </table>

 <h3 id="encoding">Encoding of File Names</h3>
 <h3 id="encoding">Encoding of file names</h3>

 <p>Traditionally the ZIP archive format uses CodePage 437 as encoding for file name, which is not
 sufficient for many international character sets.</p>
@@ -300,7 +300,7 @@ filenames that cannot be encoded using the specified encoding.</p>
 name information from them, unless you set the optional
 attribute <var>scanForUnicodeExtraFields</var> to <q>false</q>.</p>

 <h4>Recommendations for Interoperability</h4>
 <h4>Recommendations for interoperability</h4>

 <p>The optimal setting of flags depends on the archivers you expect as consumers/producers of the
 ZIP archives.  Below are some test results which may be superseded with later versions of each
--- a/manual/Types/classfileset.html
+++ b/manual/Types/classfileset.html
@@ -55,7 +55,7 @@ the <a href="fileset.html">standard fileset</a>:
  </tr>
 </table>

 <h3>Nested Elements</h3>
 <h3>Nested elements</h3>

 <h4>Root</h4>
 <p>
--- a/manual/Types/custom-programming.html
+++ b/manual/Types/custom-programming.html
@@ -41,7 +41,7 @@
    <p>
      The old methods of defining custom components are still supported.
    </p>
    <h3>Definition and use</h3>
    <h3>Definition and Use</h3>
    <p>
      A custom component is a normal Java class that implements a particular
      interface or extends a particular class, or has been adapted to the
--- a/manual/Types/extensionset.html
+++ b/manual/Types/extensionset.html
@@ -31,7 +31,7 @@ file <samp>guide/extensions/versioning.html</samp> or online
 at <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/versioning/spec/versioning2.html#wp90779">Package
 Versioning documentation.</a></p>

 <h3>Nested Elements</h3>
 <h3>Nested elements</h3>

 <h4>extension</h4>
 <p><a href="extension.html">Extension</a> object to add to set.</p>
@@ -40,7 +40,7 @@ Versioning documentation.</a></p>
 <p><a href="fileset.html">FileSet</a>s all files contained contained within set that are jars
 and implement an extension are added to extension set.</p>

 <h4>LibFileSet</h4>
 <h4>libfileset</h4>
 <p>All files contained contained within set that are jars and implement an extension are added
 to extension set. However, the extension information may be modified by attributes of
 libfileset.</p>
--- a/manual/Types/filelist.html
+++ b/manual/Types/filelist.html
@@ -50,10 +50,10 @@ support this feature or as stand-alone types.</p>
    <td>Yes, unless there is a nested file element</td>
  </tr>
 </table>
 <h4>Nested Element: file</h4>
 <h4>Nested element: file</h4>
 <p><em>Since Apache Ant 1.6.2</em></p>
 <p>This represents a file name. The nested element allows filenames containing white space and
 commas.</p>
 <p><em>Since Apache Ant 1.6.2</em></p>
 <table class="attr">
  <tr>
    <th>Attribute</th>
--- a/manual/Types/filterchain.html
+++ b/manual/Types/filterchain.html
@@ -136,7 +136,7 @@ implement <code>org.apache.tools.type.Parameterizable</code>.</p>
  </tr>
 </table>

 <h4>Nested Elements</h4>
 <h4>Nested elements</h4>
 <p><code>&lt;filterreader&gt;</code> supports <code>&lt;classpath&gt;</code>
 and <code>&lt;param&gt;</code> as nested elements.  Each <code>&lt;param&gt;</code> element may
 take in the following attributes&mdash;<var>name</var>, <var>type</var> and <var>value</var>.</p>
--- a/manual/Types/multirootfileset.html
+++ b/manual/Types/multirootfileset.html
@@ -123,7 +123,7 @@ an <code>&lt;and&gt;</code> selector container.</p>
 <p>In addition basedirs for the MultiRootFileSet can be specified as nested <code>basedir</code>
 elements that have a single <var>file</var> attribute.</p>

 <h4>Examples</h4>
 <h3>Examples</h3>

 <pre>
 &lt;multirootfileset basedirs=&quot;${build.dir},${other.project.dir}&quot;&gt;
--- a/manual/Types/namespace.html
+++ b/manual/Types/namespace.html
@@ -95,7 +95,7 @@
      element and all its descendants.
    </p>

    <h3>Default namespace</h3>
    <h3>Default Namespace</h3>
    <p>
      The default namespace used by Ant is <code>antlib:org.apache.tools.ant</code>.
    </p>
--- a/manual/Types/xmlcatalog.html
+++ b/manual/Types/xmlcatalog.html
@@ -89,7 +89,7 @@ and <code>URI</code> respectively.  By contrast, external catalog files may use
 types defined in
 the <a href="https://www.oasis-open.org/committees/download.php/14809/xml-catalogs.html">OASIS
 specification</a>.</p>
 <h3 id="ResolverAlgorithm">Entity/DTD/URI Resolution Algorithm</h3>
 <h3 id="ResolverAlgorithm">Entity/DTD/URI resolution algorithm</h3>
 <p>When an entity, DTD, or URI is looked up by the XML processor, the XMLCatalog searches its
 list of entries to see if any match.  That is, it attempts to match the <var>publicId</var>
 attribute of each entry with the PublicID or URI of the entity to be resolved.  Assuming a
--- a/manual/conceptstypeslist.html
+++ b/manual/conceptstypeslist.html
@@ -53,7 +53,7 @@
 <li><a href="Types/filterset.html">FilterSet</a></li>
 <li><a href="Types/multirootfileset.html">MultiRootFileSet</a></li>
 <li><a href="Types/patternset.html">PatternSet</a></li>
 <li><a href="using.html#path">PATH-like Structures</a></li>
 <li><a href="using.html#path">Path-like Structures</a></li>
 <li><a href="Types/permissions.html">Permissions</a></li>
 <li><a href="Types/propertyset.html">PropertySet</a></li>
 <li><a href="Types/redirector.html">I/O Redirectors</a></li>
--- a/manual/dirtasks.html
+++ b/manual/dirtasks.html
@@ -198,7 +198,7 @@ selection criteria for the files the task should work with. See
 the <a href="Types/selectors.html">Selector</a> documentation for
 more information.</p>

 <h3 id="tasklist">Standard Tasks/Filesets</h3>
 <h3 id="tasklist">Standard Tasks/FileSets</h3>
 <p>Many of the standard tasks in ant take one or more filesets which follow
 the rules given here. This list, a subset of those, is a list of standard ant
 tasks that can act as an implicit fileset:</p>