--- a/html/DOM3-Events.html	Tue Nov 12 07:15:08 2013 +0800
+++ b/html/DOM3-Events.html	Tue Nov 12 07:21:20 2013 +0800
@@ -141,7 +141,7 @@
 			<p>Within this specification, the key words <q>MUST</q>, <q>MUST NOT</q>, <q>REQUIRED</q>,
 				<q>SHALL</q>, <q>SHALL NOT</q>, <q>SHOULD</q>, <q>SHOULD NOT</q>,
 				<q>RECOMMENDED</q>, <q>MAY</q>, and <q>OPTIONAL</q> are to be interpreted as described in
-				<a href="http://www.ietf.org/rfc/rfc2119.txt">RFC 2119</a> [<a href="#ref-rfc2119">RFC2119</a>].</p>
+				[<a href="#RFC2119">RFC2119</a>].</p>
 
 			<p>This specification is to be understood in the context of the DOM Level 3 Core specification [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>]
 				and the general considerations for DOM implementations apply. For example, handling of <a class="def" href="#glossary-namespaceURI">namespace URIs</a> is discussed in
@@ -2346,7 +2346,7 @@
 						</tr>
 						<tr>
 							<td class="cell-number">1.</td>
-							<td><a class="eventtype" href="#event-type-focusin"><code>focusin</code></a></td>
+							<td><a class="eventtype" href="#event-type-focusIn"><code>focusin</code></a></td>
 							<td>Sent before first target element receives focus</td>
 						</tr>
 						<tr>
@@ -2365,7 +2365,7 @@
 						</tr>
 						<tr>
 							<td class="cell-number">4.</td>
-							<td><a class="eventtype" href="#event-type-focusin"><code>focusin</code></a></td>
+							<td><a class="eventtype" href="#event-type-focusIn"><code>focusin</code></a></td>
 							<td>Sent before second target element receives focus</td>
 						</tr>
 						<tr>
@@ -6089,13 +6089,13 @@
 			<section id="keys-IME">
 				<h3>Input Method Editors</h3>
 
-				<p>This specification includes a model for <a class="def" href="#glossary-ime">input method editors (IMEs)</a>, through the <a href="#interface-CompositionEvents">CompositionEvent</a>
+				<p>This specification includes a model for <a class="def" href="#glossary-ime">input method editors (IMEs)</a>, through the <a href="#interface-CompositionEvent">CompositionEvent</a>
 					interface and events.  However, Composition Events and Keyboard Events do not necessarily map as a one-to-one relationship.  As an example, receiving a <a class="eventtype"
 					href="#event-type-keydown"><code>keydown</code></a> for the <a href="#key-Accept"><code class="key">'Accept'</code></a> key value does not necessarily imply
 					that the text currently selected in the <a class="def" href="#glossary-ime">IME</a> is being accepted, but indicates only that a keystroke happened, disconnected
 					from the <a class="def" href="#glossary-ime">IME</a> Accept functionality (which would normally result in a <a class="eventtype" href="#event-type-compositionend">
 					<code>compositionend</code></a> event in most <a class="def" href="#glossary-ime">IME</a> systems).  Keyboard events cannot be used to determine the current
-					state of the input method editor, which can be obtained through the <a href="#widl-CompositionEvent-data"><code>data</code></a> attribute of the <a href="#interface-CompositionEvents">
+					state of the input method editor, which can be obtained through the <a href="#widl-CompositionEvent-data"><code>data</code></a> attribute of the <a href="#interface-CompositionEvent">
 					CompositionEvent</a> interface.  Additionally, <a class="def" href="#glossary-ime">IME</a> systems and devices vary in their functionality, and in which keys
 					are used for activating that functionality, such that the <code class="key">'Convert'</code> and <code class="key">'Accept'</code> keys MAY be represented
 					by other available keys. Keyboard events correspond to the events generated by the input device after the keyboard layout mapping.</p>
@@ -8267,7 +8267,7 @@
 					</tr>
 					<tr>
 						<td class="cell-number">1.</td>
-						<td><a class="eventtype" href="#event-type-focusin"><code>focusin</code></a></td>
+						<td><a class="eventtype" href="#event-type-focusIn"><code>focusin</code></a></td>
 						<td>Sent before first target element receives focus</td>
 					</tr>
 					<tr>
@@ -8291,7 +8291,7 @@
 					</tr>
 					<tr>
 						<td class="cell-number">5.</td>
-						<td><a class="eventtype" href="#event-type-focusin"><code>focusin</code></a></td>
+						<td><a class="eventtype" href="#event-type-focusIn"><code>focusin</code></a></td>
 						<td>Sent before second target element receives focus</td>
 					</tr>
 					<tr>
@@ -9476,7 +9476,8 @@
 				<dd><cite><a href="http://www.oracle.com/technetwork/java/index.html">The Java Language Specification</a></cite>, J. Gosling, B. Joy, and G. Steele, Authors. Addison-Wesley, September
 					1996. Available at http://java.sun.com/docs/books/jls </dd>
 
-				<dt id="ref-rfc2119"><strong>[<a id="RFC2119">RFC2119</a>]</strong> Key words for use in RFCs to indicate Requirement Levels</dt>
+				<!-- Automatically assigned id="RFC2119". -->
+				<dt><strong>[RFC2119]</strong> Key words for use in RFCs to indicate Requirement Levels</dt>
 				<dd>S Bradner, 1997. The specification for how to use English to specify normativity, as if it were a technical language. Available at <a href="http://www.ietf.org/rfc/rfc2119.txt">
 					http://www.ietf.org/rfc/rfc2119.txt </a></dd>