Review and cleanup of N&N content. (#57)

Cleanup and fix validation errors

4.25/index.html

@@ -19,11 +19,9 @@ <h1>Eclipse 4.25 - New and Noteworthy</h1>
     The Eclipse installer and other packages can be downloaded from the <a href="https://www.eclipse.org/downloads/packages/installer">Eclipse Installer</a> page.
   </p>
 
-  <!--
   <p>
   	The 4.25 release notes for the Eclipse SDK project can be found <a href="https://www.eclipse.org/eclipse/development/readme_eclipse_4.25.php">here</a>.
   </p>
-  -->
 
   <p>Here are some of the more noteworthy items available in this release.</p>
 

4.25/jdt.html

@@ -26,10 +26,10 @@ <h2>Java development tools</h2>
 	<!--<li><a href="#JavaXX">Java&trade; XX Support</a></li>-->
 	<li><a href="#JUnit">JUnit</a></li>
 	<li><a href="#JavaEditor">Java Editor</a></li>
-	<li><a href="#JavaViewsAndDialogs">Java Views and Dialogs</a></li>
-	<li><a href="#JavaFormatter">Java Formatter</a></li>
+	<!--<li><a href="#JavaViewsAndDialogs">Java Views and Dialogs</a></li>-->
+	<!--<li><a href="#JavaFormatter">Java Formatter</a></li>-->
 	<li><a href="#Debug">Debug</a></li>
-	<li><a href="#JDTDev">JDT Developers</a></li>
+	<!--<li><a href="#JDTDev">JDT Developers</a></li>-->
 </ul>
 
 <!-- ****************** START OF N&N TABLE ****************** -->
@@ -58,11 +58,12 @@ <h2>JUnit</h2>
   </tr>
 
   <tr id="junit5-test-suite-wizard-support"> <!-- https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/168 -->
-    <td class="title"><a href="#junit5-test-suite-wizard-support">test suite wizard JUnit 5 support</a></td>
+    <td class="title"><a href="#junit5-test-suite-wizard-support">Test Suite wizard supports JUnit 5</a></td>
     <td class="content">
-      The <b>New JUnit Test Suite Wizard</b> has been enhanced to now allow the creation of a JUnit 5 test suite using the <b>@Suite</b> annotation.  To open the <b>New JUnit Test Suite Wizard</b> for the current package, go to <b>New &gt; Other &gt; Java &gt; JUnit &gt; JUnit Test Suite</b>.
+      The <b>New JUnit Test Suite Wizard</b> has been enhanced to now allow the creation of a JUnit 5 test suite using the <b>@Suite</b> annotation. 
+      To open the <b>New JUnit Test Suite Wizard</b> for the current package, go to <b>New &gt; Other &gt; Java &gt; JUnit &gt; JUnit Test Suite</b>.
 
-      <p
+      <p>
         The following shows what the wizard now looks like:
       </p>
       <p><img src="images/test-suite-wizard-junit5.png" alt="Test Suite Wizard"/></p>
@@ -85,7 +86,8 @@ <h2>Java Editor </h2>
   <tr id="while-to-enhanced-for"> <!-- https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/55 -->
     <td class="title"><a href="#while-to-enhanced-for">Convert while loops to enhanced for loops</a></td>
     <td class="content">
-      The clean-up to convert to use enhanced for loops where possible has been enhanced to convert eligible while statements that use an iterator into enhanced for loops.  The current clean-up already support converting for loops using an iterator into an enhanced for loop.
+      The clean-up to convert to enhanced 'for' loops where possible has been enhanced to convert eligible while statements that use an iterator into enhanced for loops. 
+      The current clean-up already supports converting 'for' loops using an iterator into an enhanced 'for' loop.
       <p>
         To apply the cleanup, select the Java 5 <b>Convert to enhanced 'for' loops</b> checkbox on the <b>Java Feature</b> tab in your cleanup profile.
       </p>
@@ -105,7 +107,8 @@ <h2>Java Editor </h2>
   <tr id="convert-to-switch-expression"> <!-- https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/106 -->
     <td class="title"><a href="#convert-to-switch-expression">Convert to switch expression</a></td>
     <td class="content">
-      The clean-up to convert to use a switch expression where possible has been enhanced to recognize switch statements that have every case either end in a return statement or a throw of an exception.  In such a case the switch statement is converted into a return of a switch expression.
+      The clean-up to convert to a switch expression where possible has been enhanced to recognize switch statements that have every case either end in a return statement or a throw of an exception. 
+      In such a case the switch statement is converted into a return of a switch expression.
       <p>
         To apply the cleanup, select the Java 14 <b>Convert to switch expression where possible</b> checkbox on the <b>Java Feature</b> tab in your cleanup profile.
       </p>
@@ -114,38 +117,14 @@ <h2>Java Editor </h2>
       </p>
       <p><img src="images/convert-to-switch-expression-before.png" alt="Before"/></p>
       <p>
-        Is changed to:
+        is changed to:
       </p>
       <p><img src="images/convert-to-switch-expression-after.png" alt="After"/></p>
     </td>
   </tr>
 
   <!-- ******************* End of Java Editor ************************************* -->
 
-  <!-- ******************* Java Views and Dialogs ************************************* -->
-  <tr>
-    <td id="JavaViewsAndDialogs" class="section" colspan="2">
-    <h2>Java Views and Dialogs</h2>
-    </td>
-  </tr>
-  <!-- ******************* End of Java Views and Dialogs ************************************* -->
-
-  <!-- ******************* Java Compiler ************************************* -->
-  <tr>
-    <td id="JavaCompiler" class="section" colspan="2">
-    <h2>Java Compiler</h2>
-    </td>
-  </tr>
-  <!-- ******************* End of Java Compiler ************************************* -->
-
-  <!-- ******************* Java Formatter ************************************* -->
-  <tr>
-    <td id="JavaFormatter" class="section" colspan="2">
-    <h2>Java Formatter </h2>
-    </td>
-  </tr>
-  <!-- ******************* End of Java Formatter ************************************* -->
-
   <!-- *********************** Debug ******************************** -->
   <tr>
     <td id="Debug" class="section" colspan="2">
@@ -154,24 +133,16 @@ <h2>Debug</h2>
   </tr>
 
   <tr id="doubleclick-in-debug-popups"> <!-- https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/85 -->
-    <td class="title"><a href="#doubleclick-in-debug-popups">Double clicking in the "AllReferences and "AllInstances" popup navigates to the type</a></td>
+    <td class="title"><a href="#doubleclick-in-debug-popups">Double click in "All References and "All Instances" pop-up to navigate to Type</a></td>
     <td class="content">
-      <p>
-        Previously, the "All References" and "All Instances" popup wasn't acted on clicking on any of the shown items, this is improved, so if the selected variable or field type's source code is available, the editor tries to open it, and navigate to the declaration.
-      </p>
+       Previously, clicking on any of the shown items in the "All References" and "All Instances" popup wasn't acted upon. 
+       This is now improved - if the selected variable or field type's source code is available, the editor tries to open it, and navigate to the declaration.
       <p><img src="images/all-references-popup.png" alt="Popup"/></p>
     </td>
   </tr>
 
   <!--************************ End of Debug ******************************** -->
 
-  <!-- *********************** JDT Developers ******************************** -->
-  <tr>
-    <td id="JDTDev" class="section" colspan="2">
-    <h2>JDT Developers</h2>
-    </td>
-  </tr>
-  <!-- *********************** End of JDT Developers ******************************** -->
   <tr><td colspan="2"/></tr>
 </tbody>
 </table>

4.25/pde.html

@@ -23,10 +23,10 @@
 <body>
 <h2>Plug-in Development Environment</h2>
 <ul>
-	<li><a href="#dialogs-wizards-views">Dialogs, Wizards and Views</a></li>
+	<!--<li><a href="#dialogs-wizards-views">Dialogs, Wizards and Views</a></li>
 	<li><a href="#editors">Editors</a></li>
 	<li><a href="#APITools">API Tools</a></li>
-	<li><a href="#pde-compiler">PDE Compiler</a></li>
+	<li><a href="#pde-compiler">PDE Compiler</a></li> -->
 	<li><a href="#GeneralUpdates">General Updates</a></li>
 </ul>
 
@@ -37,29 +37,6 @@ <h2>Plug-in Development Environment</h2>
   <col />
 </colgroup>
 <tbody>
-  <!-- ******************** Dialogs, Wizard and Views ********************** -->
-  <tr>
-    <td id="dialogs-wizards-views" class="section" colspan="2"><h2>Dialogs, Wizards and Views</h2></td>
-  </tr>
-  <!-- ******************** End ofDialogs, Wizard and Views ********************** -->
-
-  <!-- ******************** Editors ********************** -->
-  <tr>
-    <td id="editors" class="section" colspan="2"><h2>Editors</h2></td>
-  </tr>
-  <!-- ******************** End of Editors ********************** -->
-
-  <!-- ******************** APITools ********************** -->
-  <tr>
-    <td id="APITools" class="section" colspan="2"><h2>API Tools</h2></td>
-  </tr>
-  <!-- ******************** End of APITools ********************** -->
-
-   <!-- ******************** PDE Compiler ********************** -->
-  <tr>
-    <td id="pde-compiler" class="section" colspan="2"><h2>PDE Compiler</h2></td>
-  </tr>
-   <!-- ******************** End of PDE Compiler ********************** --> 
    <!-- ******************* General Updates ************************************* -->
   <tr>
     <td id="GeneralUpdates" class="section" colspan="2"><h2>General Updates </h2> </td>
@@ -78,11 +55,11 @@ <h2>Plug-in Development Environment</h2>
 	<tr id="default-osgi-annotations">
 		<td class="title"><a href="#default-osgi-annotations">Support for the OSGi Bundle and Versioning Annotations</a></td>
 		<td class="content">
-			<p>PDE now supports the <a href="https://docs.osgi.org/specification/osgi.core/7.0.0/framework.api.html#org.osgi.annotation.bundle">OSGi Bundle</a> and 
+			PDE now supports the <a href="https://docs.osgi.org/specification/osgi.core/7.0.0/framework.api.html#org.osgi.annotation.bundle">OSGi Bundle</a> and 
 			<a href="https://docs.osgi.org/specification/osgi.core/7.0.0/framework.api.html#org.osgi.annotation.versioning">OSGi Versioning</a> annotations to be used in a Plugin Project.
-			</p>
 			<p>
-			To <b>enable</b> the annotations one only needs to add them to the target platform e.g. with the following locations:
+			To enable the annotations you only need to add them to the target platform e.g. with the following locations:
+			</p>
 			<pre>
 &lt;target name="annotations"&gt;
 	&lt;locations&gt;
@@ -110,9 +87,9 @@ <h2>Plug-in Development Environment</h2>
 &lt;/target&gt;
 			</pre>
 			but of course any other source is accepted (e.g. directory locations or update-sites).
-			</p>
 			<p>
-			You can now <b>use</b> them for example the following way on a package-info.java:
+			For example, you can now <b>use</b> them in the following way on a package-info.java:
+			</p>
 			<pre>
 @org.osgi.annotation.bundle.Export
 @org.osgi.annotation.versioning.Version("1.0")
@@ -128,18 +105,21 @@ <h2>Plug-in Development Environment</h2>
 }
 			</pre>
 			and then they can be processed by other tools (e.g. bnd or tycho).
-			</p>
+			PDE now also supports the <code>@Export</code> and <code>@Version</code> annotations, if you put them on a <code>package-info.java</code> file like this:
 			<p>
-			<b>PDE</b> has now also support for the <code>@Export</code> and <code>@Version</code> annotations, if you put them on a <code>package-info.java</code> file like this:
-			<img src="images/bunde-export-version-header.png" />
+			<img src="images/bunde-export-version-header.png" alt=""/>
+			</p>
 			the <code>MANIFEST.MF</code> is updated accordingly
-			<img src="images/manifest-example.png" />
+			<p>
+			<img src="images/manifest-example.png" alt=""/>
 			</p>
 			<p>
 			The same works for <code>@Header</code> annotation, adding this like this:
-			<img src="images/header-example.png" />
-			this results in an extra header added to the <code>MANIFEST.MF</code>
-			<img src="images/manifest-example2.png" /> 
+			<img src="images/header-example.png" alt=""/>
+			</p>
+			this results in an extra header being added to the <code>MANIFEST.MF</code>
+			<p>
+			<img src="images/manifest-example2.png" alt=""/> 
 			</p>
 		</td>
 	</tr>