src/java.desktop/share/classes/java/awt/im/spi/package-info.java

@@ -31,11 +31,11 @@
  * using thousands of different characters - on keyboards with far fewer keys.
  * However, this package also allows the development of input methods for other
  * languages and the use of entirely different input mechanisms, such as
  * handwriting recognition.
  *
- * <h2><a name="Packaging"></a>Packaging Input Methods</h2>
+ * <h2><a id="Packaging"></a>Packaging Input Methods</h2>
  * Input methods can be made available by adding them to the application's class
  * path. The main JAR file of an input method must contain the file:
  * <pre>
  *     META-INF/services/java.awt.im.spi.InputMethodDescriptor
  * </pre>

@@ -59,18 +59,18 @@
  * class implementing the {@code java.awt.im.spi.InputMethod} interface. The
  * input method should separate the implementations for these interfaces, so
  * that loading of the class implementing {@code InputMethod} can be deferred
  * until actually needed.
  *
- * <h2><a name="Loading"></a>Loading Input Methods</h2>
+ * <h2><a id="Loading"></a>Loading Input Methods</h2>
  * The input method framework will usually defer loading of input  method
  * classes until they are absolutely needed. It loads only the
  * {@code InputMethodDescriptor} implementations during AWT initialization. It
  * loads an {@code InputMethod} implementation when the input method has been
  * selected.
  *
- * <h2><a name="PeeredComponents"></a>Java Input Methods and Peered Text
+ * <h2><a id="PeeredComponents"></a>Java Input Methods and Peered Text
  * Components</h2>
  * The Java input method framework intends to support all combinations of input
  * methods (host input methods and Java input methods) and components (peered
  * and lightweight). However, because of limitations in the underlying platform,
  * it may not always be possible to enable the communication between Java input