Bug 578890 - N&N for 4.23

Add anchor tags

Change-Id: I7b73d23f2f5948ebd48f857170aa969ec22bb4af
Reviewed-on: https://git.eclipse.org/r/c/platform/eclipse.platform.common/+/191312
Tested-by: Lakshmi P Shanmugam <lshanmug@in.ibm.com>
Reviewed-by: Lakshmi P Shanmugam <lshanmug@in.ibm.com>
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html b/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
index 4338bc4..7cbc5c9 100644
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
@@ -127,7 +127,7 @@
   </tr>
   <tr id="formatter-switch-case"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=578122  -->
                                   <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=578446  -->
-    <td class="title">New options for switch/case constructs</td>
+    <td class="title"><a href="formatter-switch-case">New options for switch/case constructs</a></td>
     <td class="content">
       A few new settings have been implemented in the <b>Java Formatter</b> that allow more control over switch constructs introduced in Java 14.
       <p>In the <b>Line Wrapping</b> section, we can decide to allow <b>wrapping in switch cases: before or after an arrow,
@@ -140,7 +140,7 @@
     </td>
   </tr>
   <tr id="formatter-wrap-invocation"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=578115  -->
-    <td class="title">Method invocation wrapping indentation</td>
+    <td class="title"><a href="formatter-wrap-invocation">Method invocation wrapping indentation</a></td>
     <td class="content">
       It turns out that it's not obvious how to indent a wrapped method invocation when the preceding expression itself is complex enough to also be wrapped into multiple lines.
       Should the indentation be added to the existing indentation at the end of the expression, or just reset and assume that only the indentation of expression's first line matters?
@@ -160,7 +160,7 @@
   </tr>
   
   <tr id="finalFields"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=577564  -->
-    <td class="title">Warning about changing final fields</td>
+    <td class="title"><a href="finalFields">Warning about changing final fields</a></td>
     <td class="content">
       Since Eclipse 3.1 <b>Eclipse Java debugger</b> allows changes on final field values.
       While technically possible, the consequences of such changes are not trivial, 
@@ -176,7 +176,7 @@
   </tr>
 
   <tr id="labels-in-expressions-view"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=577103  -->
-    <td class="title">Highlight labelled objects in the "Expressions" view too</td>
+    <td class="title"><a href="labels-in-expressions-view">Highlight labelled objects in the "Expressions" view too</a></td>
     <td class="content">
       Since Eclipse 4.22, the <b>Java debugger</b> allows to label object instances with custom strings.
       This feature has been extended to show those labels in the <b>Expressions</b> view, highlighted with red color by default.
@@ -186,7 +186,7 @@
   </tr>
 
   <tr id="open-field-declaration"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=577622 -->
-    <td class="title">Open field declaration</td>
+    <td class="title"><a href="open-field-declaration">Open field declaration</a></td>
     <td class="content">
       During debugging, for a variable, previously it was only possible to navigate to the actual or to the declared type of that variable.
       With the new <b>Open Field Declaration</b> context menu item, it is extended to go to the declaration of that field. This can be especially helpful,
@@ -196,7 +196,7 @@
   </tr>
   
   <tr id="lambda-entry-declaration"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=486264 -->
-    <td class="title">Lambda Entry Breakpoint</td>
+    <td class="title"><a href="lambda-entry-declaration">Lambda Entry Breakpoint</a></td>
     <td class="content">
       During debugging, you can now add entry breakpoints for Lambda expressions which will enable the debugger to stop at the entry of lambda expression instead of stopping at the first expression of the line.
       You can see the breakpoint in the <b>Breakpoints</b> view indicated by the implemented functional interface. Double clicking the breakpoint in Breakpoints view will display the associated Lambda Expression in the editor.