More highlighting of new features;

also, loose is mostly used as an adjective

manual/Tasks/concat.html

@@ -36,7 +36,7 @@
         list is empty and ignoreempty is true.
       </p>
 
-      <p><strong>Since Apache Ant 1.7.1</strong>, this task can be used as a
+      <p><em>Since Apache Ant 1.7.1</em>, this task can be used as a
         <a href="../Types/resources.html#collection">Resource Collection</a>
         that will return exactly one
         <a href="../Types/resources.html">resource</a>.

manual/Tasks/copy.html

@@ -80,7 +80,7 @@ operation as <a href="../Types/filterset.html">filtersets</a>.
       specified in the <code>&lt;fileset&gt;</code>, or if the
       <code>file</code> attribute is also specified, then only
       <code>todir</code> is allowed.<br/>
-      <em>Prior to Apache Ant 1.8.2</em> the <code>tofile</code> attribute
+      Prior to Apache Ant 1.8.2, the <code>tofile</code> attribute
       only supported filesystem resources top copy from.</td>
   </tr>
   <tr>
@@ -186,7 +186,7 @@ operation as <a href="../Types/filterset.html">filtersets</a>.
 <p><a href="../Types/resources.html#collection">Resource
 Collection</a>s are used to select groups of files to copy.  To use a
 resource collection, the <code>todir</code> attribute must be set.</p>
-<p>Prior to Ant 1.7 only <code>&lt;fileset&gt;</code> has been
+<p>Prior to Ant 1.7, only <code>&lt;fileset&gt;</code> has been
 supported as a nested element.</p>
 
 <h4>mapper</h4>

manual/Tasks/cvstagdiff.html

@@ -101,9 +101,9 @@ operation may fail when using such an incompatible client.
   <tr>
     <td valign="top">package</td>
     <td valign="top">the package/module to analyze.<br>
-    Since Ant 1.6
+    <em>Since Ant 1.6</em>
     multiple packages separated by spaces are possible.
-    aliases corresponding to different modules are also possible
+    aliases corresponding to different modules are also possible.
     Use a nested &lt;module&gt; element if you want to specify a module with
     spaces in its name.</td>
     <td align="center" valign="top">No</td>

manual/Tasks/ear.html

@@ -74,7 +74,7 @@ to a value other than its default, <code>&quot;add&quot;</code>.</b></p>
     <td valign="top">For entries coming from existing archives (like
     nested <em>zipfileset</em>s or while updating the archive), keep
     the compression as it has been originally instead of using the
-    <em>compress</em> attribute.  Defaults false.  <em>Since Apache Ant
+    <em>compress</em> attribute.  Defaults to false.  <em>Since Apache Ant
     1.6</em></td>
     <td align="center" valign="top">No</td>
   </tr>
@@ -209,7 +209,7 @@ to a value other than its default, <code>&quot;add&quot;</code>.</b></p>
     that the permissions haven't been stored at all rather than real
     permissions and will instead apply its own default values.<br/>
     Set this attribute to true if you really want to preserve the
-      original permission field. <em>since Ant 1.8.0</em>
+      original permission field. <em>Since Ant 1.8.0</em>
     </td>
     <td valign="top" align="center">No, default is false</td>
   </tr>

manual/Tasks/get.html

@@ -131,9 +131,8 @@ plain text' authentication is used. This is only secure over an HTTPS link.
   </tr>
   <tr>
     <td valign="top">useragent</td>
-    <td valign="top">User-Agent HTTP header to send, starting with Ant
-      1.9.3 Ant will specify a User-Agent header of "Apache Ant VERSION"
-      unless overridden by this attribute<br/>
+    <td valign="top">User-Agent HTTP header to send,
+      defaults to "Apache Ant VERSION"<br/>
       <em>since Ant 1.9.3</em></td>
     <td align="center" valign="top">No</td>
   </tr>

manual/Tasks/jar.html

@@ -125,7 +125,7 @@ in the <a href="#jep238-example">JEP 238 example</a>. If you want to tune this k
     <td valign="top">For entries coming from existing archives (like
     nested <em>zipfileset</em>s or while updating the archive), keep
     the compression as it has been originally instead of using the
-    <em>compress</em> attribute.  Defaults false.  <em>Since Ant
+    <em>compress</em> attribute.  Defaults to false.  <em>Since Ant
     1.6</em></td>
     <td align="center" valign="top">No</td>
   </tr>

manual/Tasks/javadoc.html

@@ -209,7 +209,7 @@ to &lt;javadoc&gt; using <tt>classpath</tt>, <tt>classpathref</tt> attributes or
     <td valign="top">Generate output using JDK 1.1 emulating
       doclet.<br>
       <strong>Note</strong>: <em>Since Ant 1.8.0</em> this attribute has no
-      effect since javadoc of Java 1.4 and later
+      effect because javadoc of Java 1.4 and later
       does not support the -1.1 switch anymore.</td>
     <td align="center" valign="top">1.2</td>
     <td align="center" valign="top">No</td>

manual/Tasks/junitreport.html

@@ -37,8 +37,8 @@ for more information.</p>
 <p>The task needs Apache <a
 href="http://xml.apache.org/xalan-j/">Xalan 2.4.1+ or Xalan XSLTC</a>
 (JDK 1.4 contains a version of Xalan 2.x, while JDK 1.5 ships with a
-version of XSLTC). Since version 1.4.2-01, JDK ships with a bundled
-Xalan 2.4.1+, meaning that JDK prior to version 1.4.2-01 won't work
+version of XSLTC). JDK 1.4.2-01 and later ships with a bundled
+Xalan 2.4.1+, meaning that JDKs prior to version 1.4.2-01 won't work
 out of the box. The table below summarize the compatibility status.
 </p>
 <table>
@@ -50,9 +50,9 @@ out of the box. The table below summarize the compatibility status.
 </table>
 
 <p>In Ant 1.6.2, we had to decide between supporting Xalan 1/Xalan 2.4.1-
-and Xalan 2.4.1+/XSLTC, since there was no way to support both couples at the same
+and Xalan 2.4.1+/XSLTC, because there was no way to support both couples at the same
 time.</p>
-<p><em>Since Ant 1.7</em>, we dropped support for Xalan 1, since Xalan 1 was not
+<p><em>Since Ant 1.7</em>, we dropped support for Xalan 1, because Xalan 1 was not
 available anymore for quite some time.</p>
 
 <h3>Parameters</h3>

manual/Tasks/manifest.html

@@ -86,7 +86,7 @@ line.</p>
       in different manifests (if updating).  If false, only the
       attribute of the most recent manifest will be preserved.
       <em>Since Ant 1.8.0</em>.
-      <br/>unless you also set flattenAttributes to true this may
+      <br/>Unless you also set flattenAttributes to true this may
       result in manifests containing multiple Class-Path attributes
       which violates the manifest specification.</td>
     <td align="center" valign="top">No, default is false</td>

manual/Tasks/property.html

@@ -58,7 +58,7 @@ properties. These references are resolved at the time these properties are set.
 This also holds for properties loaded from a property file.</p>
 <p>A list of predefined properties can be found <a
 href="../properties.html#built-in-props">here</a>.</p>
-<p>Since Apache Ant 1.8.0 it is possible to load properties defined in xml
+<p><em>Since Apache Ant 1.8.0</em>, it is possible to load properties defined in xml
 according to <a href="http://java.sun.com/dtd/properties.dtd">Suns DTD</a>,
 if Java 5+ is present. For this the name of the file, resource or url has
 to end with <tt>.xml</tt>.</p>
@@ -177,21 +177,21 @@ SYSTEM).
 </p>
 
 <h4>Any OS except OpenVMS</h4>
-<p>Starting with Ant 1.8.2 if Ant detects it is running of a Java 5
-  VM (or better) Ant will use <code>System.getenv</code> rather than
+<p><em>Since Ant 1.8.2</em>, if Ant detects it is running on a Java 5
+  or newer VM, Ant will use <code>System.getenv</code> rather than
   its own OS dependent native implementation.  For some OSes this
   causes minor differences when compared to older versions of Ant.
   For a full list
   see <a href="https://issues.apache.org/bugzilla/show_bug.cgi?id=49366">Bugzilla
   Issue 49366</a>.  In particular:</p>
 <ul>
-  <li>On Windows Ant will now return additional "environment
+  <li>On Windows, Ant will now return additional "environment
     variables" that correspond to the drive specific current working
     directories when Ant is run from the command line.  The keys of
     these variables starts with an equals sign.</li>
   <li>Some users reported that some Cygwin specific variables (in
     particular PROMPT) was no longer present.</li>
-  <li>On OS/2 Ant no longer returns the BEGINLIBPATH variable.</li>
+  <li>On OS/2, Ant no longer returns the BEGINLIBPATH variable.</li>
 </ul>
 
 <h3>Parameters specified as nested elements</h3>

manual/Tasks/propertyfile.html

@@ -61,7 +61,7 @@ file are preserved.</p>
 <tr>
   <td width="12%" valign="top">jdkproperties</td>
   <td width="78%" valign="top">Use java.lang.Properties, which will
-    loose comments and layout of file (default is 'false').  <em>since
+    lose comments and layout of file (default is 'false').  <em>since
     Ant 1.8.0</em></td>
   <td width="10%" valign="top">no</td>
 </tr>

manual/Tasks/replaceregexp.html

@@ -109,7 +109,7 @@ value, in the file <code>${src}/build.properties</code></p>
 <h3>Parameters specified as nested elements</h3>
 <p>This task supports a nested <a href="../Types/fileset.html">FileSet</a>
    element.</p>
-<p>Since Ant 1.8.0 this task supports any filesystem
+<p><em>Since Ant 1.8.0</em>, this task supports any filesystem
   based <a href="../Types/resources.html#collection">resource
     collections</a> as nested elements.</p>
 <p>This task supports a nested <i><a href="../Types/regexp.html">Regexp</a></i> element to specify

manual/Tasks/signjar.html

@@ -287,8 +287,8 @@ SHA256withRSA.
 With trusted timestamping, users can verify that signing occurred before a certificate's expiration or revocation. Without this timestamp, users can only verify the signature as of their current date.</p>
 
 <p>
-Timestamped JAR files were introduced in Java 5 and supported in Ant since
-Ant 1.7. Since Ant 1.9.5, Ant can use unauthenticated proxies for this signing process.
+Timestamped JAR files were introduced in Java 5 and supported <em>since Ant 1.7</em>.
+<em>Since Ant 1.9.5</em>, Ant can use unauthenticated proxies for this signing process.
 </p>
 
 <p>Common public timestamp authorities include</p>

manual/Tasks/sql.html

@@ -46,7 +46,7 @@ and <b>abort</b> execution and transaction and fail task.</p>
 <p>
 <b>Proxies</b>. Some JDBC drivers (including the Oracle thin driver),
     use the JVM's proxy settings to route their JDBC operations to the database.
-    Since Apache Ant 1.7, Ant running on Java 5 or later defaults to
+    <em>Since Apache Ant 1.7</em>, Ant running on Java 5 or later defaults to
     <a href="../proxy.html">using
     the proxy settings of the operating system</a>.
     Accordingly, the OS proxy settings need to be valid, or Ant's proxy
@@ -123,7 +123,7 @@ and <b>abort</b> execution and transaction and fail task.</p>
 </tr>
 <tr>
   <td width="12%" valign="top">output</td>
-  <td width="78%" valign="top">Output file for result sets (defaults to System.out)
+  <td width="78%" valign="top">Output file for result sets (defaults to System.out).
     <em>Since Ant 1.8</em> can specify any Resource that supports output (see
     <a href="../develop.html#set-magic">note</a>).
   </td>

manual/Tasks/sshexec.html

@@ -65,7 +65,7 @@ and won't work with versions of jsch earlier than
   <tr>
     <td valign="top">commandResource</td>
     <td valign="top">The resource (file) that contains the commands to run on the remote host.
-    Since Ant 1.7.1</td>
+      <em>Since Ant 1.7.1</em></td>
     <td valign="top" align="center">Either this or command must be set</td>
   </tr>
   <tr>

manual/Tasks/war.html

@@ -107,7 +107,7 @@ to a value other than its default, <code>&quot;add&quot;</code>.</b></p>
     <td valign="top">For entries coming from existing archives (like
     nested <em>zipfileset</em>s or while updating the archive), keep
     the compression as it has been originally instead of using the
-    <em>compress</em> attribute.  Defaults false.  <em>Since Ant
+    <em>compress</em> attribute.  Defaults to false.  <em>Since Ant
     1.6</em></td>
     <td align="center" valign="top">No</td>
   </tr>

manual/Tasks/zip.html

@@ -418,7 +418,7 @@ archive.</p>
 
 <ul>
   <li><em>never</em> means no Zip64 extra fields will ever be
-    written, this is the behavior of Ant 1.8.x and earlier and the
+    written. This is the behavior of Ant prior to 1.9.0 and the
     default behavior of <code>jar</code>, <code>ear</code>
     and <code>war</code> <em>since Ant 1.9.1</em>.</li>
   <li><em>always</em> means Zip64 extra fields are written for all