add proper link to latest release

minor typos

Author: duncdrum

src/main/xar-resources/data/upgrading.xml

@@ -30,7 +30,7 @@
         </section>
         <section id="binary-compatible-upgrades">
             <title>Binary Compatible Upgrades</title>
-            <para>Follow these steps if the new version of eXist is binary-compatible with the your old version. Check the new version's release notes to find out whether it is binary compatibility with your old version.</para>
+            <para>Follow these steps if the new version of eXist is binary-compatible with the your old version. Check the new version's release notes to find out whether it is binary compatible with your old version.</para>
             <procedure>
                 <step>
                     <para>Stop the old installation of eXist, if it is running.</para>
@@ -39,14 +39,14 @@
                     <para>Create a <ulink url="backup.xml">backup</ulink> of the data from your old installation of eXist.</para>
                 </step>
                 <step>
-                    <para>Install the new version of eXist. Do not install one eXist version over another one. 
+                    <para>Install the new version of eXist. Do not install one eXist version over another one.
                         Always install the new version into a fresh new directory.</para>
                 </step>
                 <step>
-                    <para>Remove the <emphasis>empty</emphasis> <code>data</code> directory from the new installation. 
-                        Typically the data directory is located in <code>webapp/WEB-INF/data</code>. 
-                        If you are not sure where the data directory is located, 
-                        you can check the <ulink url="troubleshooting.xml#logs"><code>exist.log</code></ulink>, 
+                    <para>Remove the <emphasis>empty</emphasis> <code>data</code> directory from the new installation.
+                        Typically the data directory is located in <code>webapp/WEB-INF/data</code>.
+                        If you are not sure where the data directory is located,
+                        you can check the <ulink url="troubleshooting.xml#logs"><code>exist.log</code></ulink>,
                         searching for entires after startup pertaining to <code>DATA_DIR</code>.
                     </para>
                 </step>
@@ -63,10 +63,10 @@
         </section>
         <section id="non-binary-compatible-upgrades">
             <title>Binary Non-compatible Upgrades</title>
-            <para>Follow these steps if the new version of eXist is not binary-compatible with the your old version. 
-                (Check the new version's release notes to find out whether it is binary compatibility with your old version.) 
-                Additional steps are required when upgrading to a new version of eXist whose database format is not binary-compatible with your old installation. 
-                The key difference is that you must perform a <emphasis>full restore</emphasis> of your backed up data onto the new installation of eXist, 
+            <para>Follow these steps if the new version of eXist is not binary-compatible with the your old version.
+                (Check the new version's release notes to find out whether it is binary compatibility with your old version.)
+                Additional steps are required when upgrading to a new version of eXist whose database format is not binary-compatible with your old installation.
+                The key difference is that you must perform a <emphasis>full restore</emphasis> of your backed up data onto the new installation of eXist,
                 rather than simply copying the data directory to the new installation.</para>
             <procedure>
                 <step>
@@ -76,7 +76,7 @@
                             <para>Use Backup Central from the Dashboard (with "Zip" option for databases with less then 4GB)</para>
                         </listitem>
                         <listitem>
-                            <para>The Emergency Backup Tool (GUI) for installer based systems:</para> 
+                            <para>The Emergency Backup Tool (GUI) for installer based systems:</para>
                             <programlisting language="shell">java -jar start.jar -Xmx2048m org.exist.backup.ExportGUI</programlisting> <!--listing in backup.xml has no -Xmx parameter DP-->
                         </listitem>
                         <listitem>
@@ -93,10 +93,10 @@
                         </listitem>
                     </orderedlist>
                     </para>
-                    <para>Once the backup is complete, you should check the backup report in the <code>export</code> directory 
-                        within either the data directory (for backups created via the Dashboard, or Xquery) or 
+                    <para>Once the backup is complete, you should check the backup report in the <code>export</code> directory
+                        within either the data directory (for backups created via the Dashboard, or Xquery) or
                         <code>$EXIST-HOME</code> (for Backups created by the Emergency Backup Tool).</para>
-                    <para>Normally this just contains the list of collections which were backed up. If you see any warnings or errors, 
+                    <para>Normally this report just contains the list of collections which were backed up. If you see any warnings or errors,
                         it is especially important that you perform a “full restore” of your backed-up data onto the new installation of eXist.</para>
                 </step>
                 <step>
@@ -120,14 +120,14 @@
                 <tgroup cols="2">
                     <tbody>
                 <tr>
-                    <td>3.6</td>
-                    <td><ulink url="http://exist-db.org/exist/apps/wiki/blogs/eXist/">release notes</ulink></td> <!--needs update with next breaking release DP-->
+                    <td>latest</td>
+                    <td><ulink url="http://exist-db.org/exist/apps/wiki/blogs/eXist/search.html?field=tags&amp;q=release">release notes</ulink></td>
                 </tr>
-                <tr>
+                <tr> <!-- add new row with next binary incompatible release -->
                     <td>3.0</td>
                     <td><ulink url="incompatibilities.xml#v3.0">special notes</ulink></td>
                 </tr>
-                <tr> 
+                <tr>
                     <td>2.2</td>
                     <td><ulink url="incompatibilities.xml#v2.2">special notes</ulink></td>
                 </tr>
@@ -143,4 +143,4 @@
             </table>
         </section>
     </chapter>
-</book>
+</book>