--- a/html/DOM3-Events.html	Fri May 23 07:45:46 2014 -0700
+++ b/html/DOM3-Events.html	Fri May 23 08:07:00 2014 -0700
@@ -269,12 +269,16 @@
 				<dd><ul>
 					<li>Names of key values are shown as: <code class="key">'='</code> (e.g., the value of 
 						<a href="#widl-KeyboardEvent-key"><code>KeyboardEvent.key</code></a>).
+						</li>
 					<li>Names of key codes are shown as: <code class="code">'Equal'</code> (e.g., the value of 
 						<a href="#widl-KeyboardEvent-code"><code>KeyboardEvent.code</code></a>).
+						</li>
 					<li>Character values of keys are shown as: <code class="char">'\u003d'</code> (e.g., the code point 
 						of the key value).
+						</li>
 					<li>Glyphs representing character values are shown as: <code class="glyph">'='</code> (e.g., the
 						<a href="#key-legends"><em>key cap</em></a> or font associated with a character value).
+						</li>
 				</ul></dd>
 			</dl>
 
@@ -3892,14 +3896,17 @@
 							<p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a pointing device is moved while it is over an element.  The frequency
 								rate of events while the pointing device is moved is implementation-, device-, and platform-specific, but multiple consecutive <a class="eventtype" href="#event-type-mousemove">
 								<code>mousemove</code></a> events SHOULD be fired for sustained pointer-device movement, rather than a single event for each instance of mouse movement.  Implementations
-								are encouraged to determine the optimal frequency rate to balance responsiveness with performance.</p>
+								are encouraged to determine the optimal frequency rate to balance responsiveness with performance.
+								</p>
 
 							<p class="note"><strong>Authoring Note: </strong>In some implementation environments, such as a browser, <a class="eventtype"><code>mousemove</code></a> events can continue
-								to fire if the user began a drag operation (e.g., a mouse button is pressed) and the pointing device has left the boundary of the user agent.</p>
+								to fire if the user began a drag operation (e.g., a mouse button is pressed) and the pointing device has left the boundary of the user agent.
+								</p>
 
 							<p class="note" id="mousemove-now-cancelable"><strong>Note: </strong>This event was formerly specified to be non-cancelable in DOM Level 2 Events
 								[<a href="#references-DOM2Events">DOM2 Events</a>], but was changed to reflect existing interoperability between 
 								user agents.
+								</p>
 						</dd>
 					</dl>
 				</div>
@@ -5430,7 +5437,7 @@
 						<tr>
 							<td class="cell-number"></td>
 							<th>Event Name</th>
-							<th><a href="#widl-CompositionEvent-data"><code>CompositionEvent<br>data</code></a></th>
+							<th><a href="#widl-CompositionEvent-data"><code>CompositionEvent<br/>data</code></a></th>
 							<th>Notes</th>
 						</tr>
 						<tr>
@@ -10581,7 +10588,7 @@
 
 			<dt id="glossary-body-element"><dfn>body element</dfn></dt>
 			<dd>In HTML or XHTML documents, the body element represents the contents of the document. In a well-formed HTML document, the body element is a first descendant of 
-				the <a href="#glossary-root-element">root element</a>.
+				the <a href="#glossary-root-element">root element</a>.</dd>
 				
 			<dt id="glossary-bubbling-phase"><dfn>bubbling phase</dfn></dt>
 			<dd>The process by which an <a class="def" href="#glossary-event">event</a> can be handled by one of the target's ancestors <em>after</em> being handled by the
@@ -11117,7 +11124,3 @@
 	</script>
   </body>
 </html>
-
-
-<li>Character values of keys are shown as: <code class="char">'\u003d'</code>.
-					<li>Glyphs representing character values are shown as: <code class="glyph">'='</code>.
\ No newline at end of file