--- a/html/Note-KeyProps.html	Wed Sep 05 05:03:58 2012 +0900
+++ b/html/Note-KeyProps.html	Wed Sep 05 05:20:32 2012 +0900
@@ -159,7 +159,7 @@
     <hr />
     <div class="body">
       <h1><a id="intro" href="#intro">1. Introduction</a></h1>
-      <p>Browser support for keyboards has traditionally relied on two ad-hoc event interface properties, <code class="attr-name">keyCode</code>, and <code class="attr-name">charCode</code>.  The values for these properties, and the availability of the attribute, is inconsistent across platforms, keyboard languages and layouts, <a class="def" href="#glossary-user-agent">user agents</a>, versions, and even event types.  A significant amount of legacy content, including script libraries, relies upon detecting the <a class="def" href="#glossary-user-agent">user agent</a> and acting accordingly, and any changes to <code class="attr-name">keyCode</code>, or <code class="attr-name">charCode</code> risk breaking as much content as they fix or enable.  Additionally, these properties are not suitable for international usage, or accessibility concerns.  Therefore, the DOM Level 3 Events  [<a href="#references-DOM3Events">DOM3 Events</a>] specification does not normatively define the <code class="attr-name">keyCode</code>, and <code class="attr-name">charCode</code> properties, relying instead only on the more robust key values, which can be used safely and consistently in any <a class="def" href="#glossary-user-agent">user agent</a> which conforms to that specification.  However, for the purpose of documenting the current state of these properties and their relation to equivalent key values, this note contains the following table, which is to be used as an informative reference only, and does not document the full range of values for <code class="attr-name">keyCode</code>, and <code class="attr-name">charCode</code>.</p>
+      <p>Browser support for keyboards has traditionally relied on two ad-hoc event interface properties, <code class="attr-name">keyCode</code>, and <code class="attr-name">charCode</code>.  The values for these properties, and the availability of the attribute, is inconsistent across platforms, keyboard languages and layouts, user agents, versions, and even event types.  A significant amount of legacy content, including script libraries, relies upon detecting the user agent and acting accordingly, and any changes to <code class="attr-name">keyCode</code>, or <code class="attr-name">charCode</code> risk breaking as much content as they fix or enable.  Additionally, these properties are not suitable for international usage, or accessibility concerns.  Therefore, the DOM Level 3 Events  [<a href="#references-DOM3Events">DOM3 Events</a>] specification does not normatively define the <code class="attr-name">keyCode</code>, and <code class="attr-name">charCode</code> properties, relying instead only on the more robust key values, which can be used safely and consistently in any user agent which conforms to that specification.  However, for the purpose of documenting the current state of these properties and their relation to equivalent key values, this note contains the following table, which is to be used as an informative reference only, and does not document the full range of values for <code class="attr-name">keyCode</code>, and <code class="attr-name">charCode</code>.</p>
 
       <div>
         <h2><a id="keyset-keyCode-charCode" href="#keyset-keyCode-charCode">1.1. Key values, keyCode, and charCode</a></h2>