[html5] r1664 - /

whatwg at whatwg.org whatwg at whatwg.org
Thu May 22 03:44:38 PDT 2008


Author: ianh
Date: 2008-05-22 03:44:38 -0700 (Thu, 22 May 2008)
New Revision: 1664

Modified:
   index
   source
Log:
[e] (0) run a spellchecker...

Modified: index
===================================================================
--- index	2008-05-22 09:33:20 UTC (rev 1663)
+++ index	2008-05-22 10:44:38 UTC (rev 1664)
@@ -1770,7 +1770,7 @@
 
      <li><a href="#namespaces"><span class=secno>8.3 </span>Namespaces</a>
 
-     <li><a href="#serialising"><span class=secno>8.4 </span>Serialising HTML
+     <li><a href="#serializing"><span class=secno>8.4 </span>Serializing HTML
       fragments</a>
 
      <li><a href="#parsing2"><span class=secno>8.5 </span>Parsing HTML
@@ -1808,8 +1808,8 @@
     with this specification because they are better handled using other
     technologies that are further described herein</a>
     <ul class=toc>
-     <li><a href="#localisation"><span class=secno>10.1
-      </span>Localisation</a>
+     <li><a href="#localization"><span class=secno>10.1
+      </span>Localization</a>
 
      <li><a href="#declarative"><span class=secno>10.2 </span>Declarative 2D
       vector graphics and animation</a>
@@ -1854,7 +1854,7 @@
    applications.
 
   <p>The scope of this specification does not include providing mechanisms
-   for media-specific customisation of presentation (although default
+   for media-specific customization of presentation (although default
    rendering rules for Web browsers are included at the end of this
    specification, and several mechanisms for hooking into CSS are provided as
    part of the language).
@@ -1977,7 +1977,7 @@
    <dt><a href="#syntax">The Language Syntax</a>
 
    <dd>All of these features would be for naught if they couldn't be
-    represented in a serialised form and sent to other people, and so this
+    represented in a serialized form and sent to other people, and so this
     section defines the syntax of HTML, along with rules for how to parse
     HTML.
   </dl>
@@ -2180,7 +2180,7 @@
     <p>When an authoring tool is used to edit a non-conforming document, it
      may preserve the conformance errors in sections of the document that
      were not edited during the editing session (i.e. an editing tool is
-     allowed to round-trip errorneous content). However, an authoring tool
+     allowed to round-trip erroneous content). However, an authoring tool
      must not claim that the output is conformant if errors have been so
      preserved.</p>
 
@@ -2270,10 +2270,10 @@
   <h4 id=common><span class=secno>1.3.1 </span>Common conformance
    requirements for APIs exposed to JavaScript</h4>
 
-  <p class=big-issue>A lot of arrays/lists/<span>collection</span>s in this
-   spec assume zero-based indexes but use the term "<var
-   title="">index</var>th" liberally. We should define those to be zero-based
-   and be clearer about this.
+  <p class=big-issue>A lot of arrays/lists/<a href="#collections0"
+   title=collections>collection</a>s in this spec assume zero-based indexes
+   but use the term "<var title="">index</var>th" liberally. We should define
+   those to be zero-based and be clearer about this.
 
   <p>Unless otherwise specified, if a DOM attribute that is a floating point
    number type (<code title="">float</code>) is assigned an Infinity or
@@ -2309,7 +2309,7 @@
    <dd>
     <p>Implementations that support XHTML5 must support some version of XML,
      as well as its corresponding namespaces specification, because XHTML5
-     uses an XML serialisation with namespaces. <a href="#refsXML">[XML]</a>
+     uses an XML serialization with namespaces. <a href="#refsXML">[XML]</a>
      <a href="#refsXMLNAMES">[XMLNAMES]</a></p>
 
    <dt>XML Base
@@ -2558,7 +2558,7 @@
   <p class=note>This specification does not define a mechanism for
    interacting with plugins, as it is expected to be user-agent- and
    platform-specific. Some UAs might opt to support a plugin mechanism such
-   as the Netscape Plugin API; others might use remote content convertors or
+   as the Netscape Plugin API; others might use remote content converters or
    have built-in support for certain types. <a href="#refsNPAPI">[NPAPI]</a>
 
   <p class=warning>Browsers should take extreme care when interacting with
@@ -2841,7 +2841,7 @@
   <p>The <code>Document</code>'s source file's last modification date and
    time must be derived from relevant features of the networking protocols
    used, e.g. from the value of the HTTP <code title="">Last-Modified</code>
-   header of the document, or from metadata in the filesystem for local
+   header of the document, or from metadata in the file system for local
    files. If the last modification date and time are not known, the attribute
    must return the string <code title="">01/01/1970 00:00:00</code>.
 
@@ -2877,7 +2877,7 @@
   <p>Documents have an associated <dfn id=character1 title="document's
    character encoding">character encoding</dfn>. When a <code>Document</code>
    object is created, the <a href="#character1">document's character
-   encoding</a> must be initialised to UTF-16. Various algorithms during page
+   encoding</a> must be initialized to UTF-16. Various algorithms during page
    loading affect this value, as does the <code title=dom-document-charset><a
    href="#charset0">charset</a></code> setter. <a
    href="#refsIANACHARSET">[IANACHARSET]</a> <!-- XXX
@@ -3114,12 +3114,12 @@
    (<code>float</code>) and the content attribute is defined to contain a
    time offset, then, on getting, the content attribute must be parsed
    according to <a href="#rules4" title="rules for parsing time offsets">the
-   rules for parsing time ofsets</a>, and if that is successful, the
+   rules for parsing time offsets</a>, and if that is successful, the
    resulting value, in seconds, must be returned. If that fails, or if the
    attribute is absent, the default value must be returned, or the
    not-a-number value (NaN) if there is no default value. On setting, the
    given value, interpreted as a time offset in seconds, must be converted to
-   a string using the <a href="#time-offset">time offset serialisation
+   a string using the <a href="#time-offset">time offset serialization
    rules</a>, and that string must be used as the new content attribute
    value.
 
@@ -3200,12 +3200,12 @@
    <code><a href="#img">img</a></code> elements, and rooted at the root of
    the document.
 
-  <p>The <span>collection</span> then <dfn id=represents title="representated
-   by the collection">represents</dfn> a <a href="#live">live</a> view of the
-   subtree rooted at the collection's root, containing only nodes that match
-   the given filter. The view is linear. In the absence of specific
-   requirements to the contrary, the nodes within the collection must be
-   sorted in <a href="#tree-order">tree order</a>.
+  <p>The <a href="#collections0" title=collections>collection</a> then <dfn
+   id=represents title="represented by the collection">represents</dfn> a <a
+   href="#live">live</a> view of the subtree rooted at the collection's root,
+   containing only nodes that match the given filter. The view is linear. In
+   the absence of specific requirements to the contrary, the nodes within the
+   collection must be sorted in <a href="#tree-order">tree order</a>.
 
   <p class=note>The <code title=dom-table-rows><a
    href="#rows">rows</a></code> list is not in tree order.
@@ -3216,7 +3216,8 @@
   <h5 id=htmlcollection><span class=secno>2.3.1.1. </span>HTMLCollection</h5>
 
   <p>The <code><a href="#htmlcollection0">HTMLCollection</a></code> interface
-   represents a generic <span>collection</span> of elements.
+   represents a generic <a href="#collections0"
+   title=collections>collection</a> of elements.
 
   <pre class=idl>interface <dfn id=htmlcollection0>HTMLCollection</dfn> {
   readonly attribute unsigned long <a href="#length" title=dom-HTMLCollection-length>length</a>;
@@ -3226,7 +3227,8 @@
 
   <p>The <dfn id=length
    title=dom-HTMLCollection-length><code>length</code></dfn> attribute must
-   return the number of nodes <span>represented by the collection</span>.
+   return the number of nodes <a href="#represents">represented by the
+   collection</a>.
 
   <p>The <dfn id=itemindex title=dom-HTMLCollection-item><code>item(<var
    title="">index</var>)</code></dfn> method must return the <var
@@ -3262,7 +3264,8 @@
 
   <p>The <code><a
    href="#htmlformcontrolscollection0">HTMLFormControlsCollection</a></code>
-   interface represents a <span>collection</span> of form controls.
+   interface represents a <a href="#collections0"
+   title=collections>collection</a> of form controls.
 
   <pre
    class=idl>interface <dfn id=htmlformcontrolscollection0>HTMLFormControlsCollection</dfn> {
@@ -3273,8 +3276,8 @@
 
   <p>The <dfn id=length0
    title=dom-HTMLFormControlsCollection-length><code>length</code></dfn>
-   attribute must return the number of nodes <span>represented by the
-   collection</span>.
+   attribute must return the number of nodes <a
+   href="#represents">represented by the collection</a>.
 
   <p>The <dfn id=itemindex0
    title=dom-HTMLFormControlsCollection-item><code>item(<var
@@ -3332,16 +3335,16 @@
 
   <p>On getting, the <dfn id=length1
    title=dom-HTMLOptionsCollection-length><code>length</code></dfn> attribute
-   must return the number of nodes <span>represented by the
-   collection</span>.
+   must return the number of nodes <a href="#represents">represented by the
+   collection</a>.
 
   <p>On setting, the behavior depends on whether the new value is equal to,
-   greater than, or less than the number of nodes <span>represented by the
-   collection</span> at that time. If the number is the same, then setting
-   the attribute must do nothing. If the new value is greater, then <var
-   title="">n</var> new <code>option</code> elements with no attributes and
-   no child nodes must be appended to the <code>select</code> element on
-   which the <code><a
+   greater than, or less than the number of nodes <a
+   href="#represents">represented by the collection</a> at that time. If the
+   number is the same, then setting the attribute must do nothing. If the new
+   value is greater, then <var title="">n</var> new <code>option</code>
+   elements with no attributes and no child nodes must be appended to the
+   <code>select</code> element on which the <code><a
    href="#htmloptionscollection0">HTMLOptionsCollection</a></code> is rooted,
    where <var title="">n</var> is the difference between the two numbers (new
    value minus old value). If the new value is lower, then the last <var
@@ -3554,7 +3557,7 @@
   <pre class=idl>interface <dfn id=domstringmap0>DOMStringMap</dfn> {
   [NameGetter] DOMString <a href="#xxx1name" title=dom-stringmap-XXX1>XXX1</a>(in DOMString name); <!-- XXX DOMB -->
   [NameSetter] void <a href="#xxx2name" title=dom-stringmap-XXX2>XXX2</a>(in DOMString name, in DOMString value); <!-- XXX DOMB -->
-  [XXX] bool <a href="#xxx3name" title=dom-stringmap-XXX3>XXX3</a>(in DOMString name); <!-- XXX DOMB -->
+  [XXX] boolean <a href="#xxx3name" title=dom-stringmap-XXX3>XXX3</a>(in DOMString name); <!-- XXX DOMB -->
 };</pre>
 
   <p>The <dfn id=xxx1name title=dom-stringmap-XXX1><code>XXX1(<var
@@ -3605,7 +3608,7 @@
   <p class=note>The interfaces defined in this specification are not always
    supersets of the interfaces defined in DOM2 HTML; some features that were
    formerly deprecated, poorly supported, rarely used or considered
-   unnecessary have been removed. Therefore it is not guarenteed that an
+   unnecessary have been removed. Therefore it is not guaranteed that an
    implementation that supports "<code title="">HTML</code>"
    "<code>5.0</code>" also supports "<code title="">HTML</code>"
    "<code>2.0</code>".
@@ -4100,7 +4103,7 @@
   <p>In HTML, the <dfn id=innerhtml0
    title=dom-innerHTML-HTML><code>innerHTML</code></dfn> DOM attribute of all
    <code><a href="#htmlelement">HTMLElement</a></code> and <code><a
-   href="#htmldocument">HTMLDocument</a></code> nodes returns a serialisation
+   href="#htmldocument">HTMLDocument</a></code> nodes returns a serialization
    of the node's children using the <span>HTML syntax</span><!-- XXX xref
   -->.
    On setting, it replaces the node's children with new nodes that result
@@ -4108,7 +4111,7 @@
 
   <p>On getting, the <code title=dom-innerHTML-HTML><a
    href="#innerhtml0">innerHTML</a></code> DOM attribute must return the
-   result of running the <a href="#html-fragment">HTML fragment serialisation
+   result of running the <a href="#html-fragment">HTML fragment serialization
    algorithm</a> on the node.
 
   <p>On setting, if the node is a document, the <code
@@ -4135,7 +4138,7 @@
     <p>Create a new <a href="#html-0">HTML parser</a>, in its initial state,
      and associate it with the <code>Document</code> node.</p>
    </li>
-   <!-- redundant, the document is forcably already so labeled if we get here
+   <!-- redundant, the document is forcibly already so labeled if we get here
    <li>
 
     <p>Mark the <code>Document</code> object as being an <span
@@ -4241,15 +4244,15 @@
    href="#htmldocument">HTMLDocument</a></code>s must return a string in the
    form of a <a href="http://www.w3.org/TR/xml/#sec-well-formed">document
    entity</a>. The string returned must be XML namespace-well-formed and must
-   be an isomorphic serialisation of all of that node's child nodes, in
+   be an isomorphic serialization of all of that node's child nodes, in
    document order. User agents may adjust prefixes and namespace declarations
-   in the serialisation (and indeed might be forced to do so in some cases to
+   in the serialization (and indeed might be forced to do so in some cases to
    obtain namespace-well-formed XML). If any of the elements in the
-   serialisation are in the null namespace, the default namespace in scope
+   serialization are in the null namespace, the default namespace in scope
    for those elements must be explicitly declared as the empty string. <a
    href="#refsXML">[XML]</a> <a href="#refsXMLNS">[XMLNS]</a>
 
-  <p>If any of the following cases are found in the DOM being serialised, the
+  <p>If any of the following cases are found in the DOM being serialized, the
    user agent must raise an <code>INVALID_STATE_ERR</code> exception:
 
   <ul>
@@ -4284,7 +4287,7 @@
     string "<code title="">?></code>".
   </ul>
 
-  <p class=note>These are the only ways to make a DOM unserialisable. The DOM
+  <p class=note>These are the only ways to make a DOM unserializable. The DOM
    enforces all the other XML constraints; for example, trying to set an
    attribute with a name that contains an equals sign (=) will raised an
    <code>INVALID_CHARACTER_ERR</code> exception.
@@ -4364,7 +4367,7 @@
   <p>For <a href="#html-">HTML documents</a>, and for <a
    href="#html-elements">HTML elements</a> in <a href="#html-">HTML
    documents</a>, certain APIs defined in DOM3 Core become case-insensitive
-   or case-changing, as sometimes defined in DOM3 Core, and as summarised or
+   or case-changing, as sometimes defined in DOM3 Core, and as summarized or
    required below. <a href="#refsDOM3CORE">[DOM3CORE]</a>.
 
   <p>This does not apply to <a href="#xml-documents">XML documents</a> or to
@@ -4921,7 +4924,7 @@
    <li>Parse <var title="">string</var> according to the <a
     href="#rules1">rules for parsing floating point number values</a>, to
     obtain <var title="">number</var>. This step cannot fail (<var
-    title="">string</var> is guarenteed to be a <a href="#valid1">valid
+    title="">string</var> is guaranteed to be a <a href="#valid1">valid
     floating point number</a>).
 
    <li>Return <var title="">number</var>.
@@ -5929,7 +5932,7 @@
 
   <p class=big-issue><dfn id=valid6>valid time offset</dfn>, <dfn
    id=rules4>rules for parsing time offsets</dfn>, <dfn id=time-offset>time
-   offset serialisation rules</dfn>; in the format "5d4h3m2s1ms" or "3m 9.2s"
+   offset serialization rules</dfn>; in the format "5d4h3m2s1ms" or "3m 9.2s"
    or "00:00:00.00" or similar.
 
   <h4 id=tokens><span class=secno>3.2.6 </span>Tokens</h4>
@@ -6406,7 +6409,7 @@
   <h5 id=flow-content><span class=secno>3.3.3.2. </span>Flow content</h5>
 
   <p>Most elements that are used in the body of documents and applications
-   are categorised as <dfn id=flow-content0>flow content</dfn>.
+   are categorized as <dfn id=flow-content0>flow content</dfn>.
 
   <p>As a general rule, elements whose content model allows any <a
    href="#flow-content0">flow content</a> should have either at least one
@@ -6461,8 +6464,8 @@
    href="#del">del</a></code> elements must not be counted as contributing to
    the ancestors of the <code><a href="#del">del</a></code> element.
 
-  <p class=note>Most elements that are categorised as phrasing content can
-   only contain elements that are themselves categorised as phrasing content,
+  <p class=note>Most elements that are categorized as phrasing content can
+   only contain elements that are themselves categorized as phrasing content,
    not any flow content.
 
   <p>Text nodes that are not <a href="#inter-element">inter-element
@@ -6905,7 +6908,7 @@
 
   <p>User agents may use the element's language to determine proper
    processing or rendering (e.g. in the selection of appropriate fonts or
-   pronounciations, or for dictionary selection). <!--User
+   pronunciations, or for dictionary selection). <!--User
   agents must not use the element's language to determine text
   directionality. (commented out because text directionality is a
   rendering-level concern.)-->
@@ -7064,7 +7067,7 @@
    Mutating the <code>CSSStyleDeclaration</code> object must create a <code
    title=attr-font-style>style</code> attribute on the element (if there
    isn't one already) and then change its value to be a value representing
-   the serialised form of the <code>CSSStyleDeclaration</code> object. <a
+   the serialized form of the <code>CSSStyleDeclaration</code> object. <a
    href="#refsCSSOM">[CSSOM]</a>
 
   <div class=example>
@@ -7360,26 +7363,27 @@
   key events.</p>
 
   <p>The <dfn><code>moveFocusForward</code></dfn> method uses the
-  <code>'nav-index'</code> property and the <code>tabindex</code>
-  attribute to find the next focusable element and focuses it.</p>
+  <code>'nav-index'</code> property and the <code
+  title="attr-tabindex">tabindex</code> attribute to find the next
+  focusable element and focuses it.</p>
 
   <p>The <dfn><code>moveFocusBackward</code></dfn> method uses the
-  <code>'nav-index'</code> property and the <code>tabindex</code>
-  attribute to find the previous focusable element and focuses
-  it.</p>
+  <code>'nav-index'</code> property and the <code
+  title="attr-tabindex>tabindex</code> attribute to find the previous
+  focusable element and focuses it.</p>
 
   <p>The <dfn><code>moveFocusUp</code></dfn> method uses the
-  <code>'nav-up'</code> property and the <code>tabindex</code>
-  attribute to find an appropriate focusable element and focuses
-  it.</p>
+  <code>'nav-up'</code> property and the <code
+  title="attr-tabindex>tabindex</code> attribute to find an
+  appropriate focusable element and focuses it.</p>
 
   <p>In a similar manner, the <dfn><code>moveFocusRight</code></dfn>,
   <dfn><code>moveFocusDown</code></dfn>, and
   <dfn><code>moveFocusLeft</code></dfn> methods use the
   <code>'nav-right'</code>, <code>'nav-down'</code>, and
-  <code>'nav-left'</code> properties (respectively), and the
-  <code>tabindex</code> attribute, to find an appropriate focusable
-  element and focus it.</p>
+  <code>'nav-left'</code> properties (respectively), and the <code
+  title="attr-tabindex>tabindex</code> attribute, to find an
+  appropriate focusable element and focus it.</p>
 
   <p>The <code>'nav-index'</code>, <code>'nav-up'</code>,
   <code>'nav-right'</code>, <code>'nav-down'</code>, and
@@ -7950,21 +7954,21 @@
    <dd>If the <code title=attr-meta-charset><a
     href="#charset1">charset</a></code> attribute is present, or if the
     element is in the <a href="#encoding"
-    title=attr-meta-http-equiv-content-type>Encoding declaraton state</a>: as
-    the first element in a <code><a href="#head">head</a></code> element.
+    title=attr-meta-http-equiv-content-type>Encoding declaration state</a>:
+    as the first element in a <code><a href="#head">head</a></code> element.
 
    <dd>If the <code title=attr-meta-http-equiv><a
     href="#http-equiv0">http-equiv</a></code> attribute is present, and the
     element is not in the <a href="#encoding"
-    title=attr-meta-http-equiv-content-type>Encoding declaraton state</a>: in
-    a <code><a href="#head">head</a></code> element.
+    title=attr-meta-http-equiv-content-type>Encoding declaration state</a>:
+    in a <code><a href="#head">head</a></code> element.
 
    <dd>If the <code title=attr-meta-http-equiv><a
     href="#http-equiv0">http-equiv</a></code> attribute is present, and the
     element is not in the <a href="#encoding"
-    title=attr-meta-http-equiv-content-type>Encoding declaraton state</a>: in
-    a <code><a href="#noscript">noscript</a></code> element that is a child
-    of a <code><a href="#head">head</a></code> element.
+    title=attr-meta-http-equiv-content-type>Encoding declaration state</a>:
+    in a <code><a href="#noscript">noscript</a></code> element that is a
+    child of a <code><a href="#head">head</a></code> element.
 
    <dd>If the <code title=attr-meta-name><a href="#name">name</a></code>
     attribute is present: where <a href="#metadata0">metadata content</a> is
@@ -8009,7 +8013,7 @@
    href="#name">name</a></code> attribute, pragma directives with the <code
    title=attr-meta-http-equiv><a href="#http-equiv0">http-equiv</a></code>
    attribute, and the file's <a href="#character2">character encoding
-   declaration</a> when an HTML document is serialised to string form (e.g.
+   declaration</a> when an HTML document is serialized to string form (e.g.
    for transmission over the network or for disk storage) with the <code
    title=attr-meta-charset><a href="#charset1">charset</a></code> attribute.
 
@@ -8312,7 +8316,7 @@
 
     <p>For <code><a href="#meta0">meta</a></code> elements in the <a
      href="#encoding" title=attr-meta-http-equiv-content-type>Encoding
-     declaraton state</a>, the <code title=attr-meta-content><a
+     declaration state</a>, the <code title=attr-meta-content><a
      href="#content0">content</a></code> attribute must have a value that is
      a case-insensitive<!-- ASCII
     XXX--> match of a string that consists
@@ -8324,7 +8328,7 @@
 
     <p>If the document contains a <code><a href="#meta0">meta</a></code>
      element in the <a href="#encoding"
-     title=attr-meta-http-equiv-content-type>Encoding declaraton state</a>
+     title=attr-meta-http-equiv-content-type>Encoding declaration state</a>
      then that element must be the first element in the document's <code><a
      href="#head">head</a></code> element, and the document must not contain
      a <code><a href="#meta0">meta</a></code> element with the <code
@@ -8332,7 +8336,7 @@
      present.</p>
 
     <p>The <a href="#encoding"
-     title=attr-meta-http-equiv-content-type>Encoding declaraton state</a>
+     title=attr-meta-http-equiv-content-type>Encoding declaration state</a>
      may be used in <a href="#html5" title=HTML5>HTML documents</a> only,
      elements in that state must not be used in <a href="#xhtml5"
      title=XHTML>XML documents</a>.</p>
@@ -8522,14 +8526,14 @@
 
   <ul>
    <li>The character encoding name given must be the name of the character
-    encoding used to serialise the file.
+    encoding used to serialize the file.
 
    <li>The value must be a valid character encoding name, and must be the
     preferred name for that encoding. <a
     href="#refsIANACHARSET">[IANACHARSET]</a> <!-- XXX
    http://www.iana.org/assignments/character-sets -->
 
-   <li>The encoding name must be serialised without the use of <a
+   <li>The encoding name must be serialized without the use of <a
     href="#character3" title=syntax-charref>character references</a> or
     character escapes of any kind.
   </ul>
@@ -8548,7 +8552,7 @@
    element with a <code title=attr-meta-charset><a
    href="#charset1">charset</a></code> attribute or a <code><a
    href="#meta0">meta</a></code> element in the <a href="#encoding"
-   title=attr-meta-http-equiv-content-type>Encoding declaraton state</a>.
+   title=attr-meta-http-equiv-content-type>Encoding declaration state</a>.
 
   <p>Authors should not use JIS_X0212-1990, x-JIS0208, and encodings based on
    EBCDIC. Authors should not use UTF-32. Authors must not use the CESU-8,
@@ -9445,8 +9449,8 @@
    href="#h1">h1</a></code> elements, or to use elements of the appropriate
    <a href="#rank">rank</a> for the section's nesting level.
 
-  <p>Authors are also encouraged to explictly wrap sections in elements of <a
-   href="#sectioning0">sectioning content</a>, instead of relying on the
+  <p>Authors are also encouraged to explicitly wrap sections in elements of
+   <a href="#sectioning0">sectioning content</a>, instead of relying on the
    implicit sections generated by having multiple heading in one element of
    <a href="#sectioning0">sectioning content</a>.
 
@@ -9524,7 +9528,7 @@
 
    <li>
     <p>Create a stack to hold elements, which is used to handle nesting.
-     Initialise this stack to empty.
+     Initialize this stack to empty.
 
    <li>
     <p>As you walk over the DOM in <a href="#tree-order">tree order</a>,
@@ -9561,7 +9565,7 @@
        for the <var title="">current outlinee</var> element.</p>
 
       <p>Let there be a new outline for the new <var title="">current
-       outlinee</var>, initialised with just the new <var title="">current
+       outlinee</var>, initialized with just the new <var title="">current
        section</var> as the only section in the outline.</p>
 
      <dt>When exiting a <a href="#sectioning0">sectioning content</a>
@@ -10006,7 +10010,7 @@
    conventions rather than by elements.
 
   <p class=note><strong>In the <span title="">HTML
-   serialisation</span><!-- XXX xref -->, a leading newline character
+   serialization</span><!-- XXX xref -->, a leading newline character
    immediately following the <code><a href="#pre">pre</a></code> element
    start tag is stripped.</strong>
 
@@ -10209,7 +10213,7 @@
 
   <p>The <dfn id=cite0 title=dom-quote-cite><code>cite</code></dfn> DOM
    attribute must <a href="#reflect">reflect</a> the element's <code
-   title="">cite</code> content attribte.
+   title="">cite</code> content attribute.
 
   <p class=note>The best way to represent a conversation is not with the
    <code><a href="#cite2">cite</a></code> and <code><a
@@ -11186,7 +11190,7 @@
   <p>The <code><a href="#em">em</a></code> element represents stress emphasis
    of its contents.
 
-  <p>The level of emphasis that a particlar piece of content has is given by
+  <p>The level of emphasis that a particular piece of content has is given by
    its number of ancestor <code><a href="#em">em</a></code> elements.
 
   <p>The placement of emphasis changes the meaning of the sentence. The
@@ -11199,7 +11203,7 @@
 
    <pre><p>Cats are cute animals.</p></pre>
 
-   <p>By emphasising the first word, the statement implies that the kind of
+   <p>By emphasizing the first word, the statement implies that the kind of
     animal under discussion is in question (maybe someone is asserting that
     dogs are cute):</p>
 
@@ -11217,17 +11221,17 @@
    <pre><p>Cats are <em>cute</em> animals.</p></pre>
 
    <p>Similarly, if someone asserted that cats were vegetables, someone
-    correcting this might emphasise the last word:</p>
+    correcting this might emphasize the last word:</p>
 
    <pre><p>Cats are cute <em>animals</em>.</p></pre>
 
-   <p>By emphasising the entire sentence, it becomes clear that the speaker
+   <p>By emphasizing the entire sentence, it becomes clear that the speaker
     is fighting hard to get the point across. This kind of emphasis also
     typically affects the punctuation, hence the exclamation mark here.</p>
 
    <pre><p><em>Cats are cute animals!</em></p></pre>
 
-   <p>Anger mixed with emphasising the cuteness could lead to markup such as:</p>
+   <p>Anger mixed with emphasizing the cuteness could lead to markup such as:</p>
 
    <pre><p><em>Cats are <em>cute</em> animals!</em></p></pre>
   </div>
@@ -11315,7 +11319,7 @@
    copyrights or other disadvantages), or other side comments.
 
   <p class=note>The <code><a href="#small">small</a></code> element does not
-   "de-emphasise" or lower the importance of text emphasised by the <code><a
+   "de-emphasize" or lower the importance of text emphasised by the <code><a
    href="#em">em</a></code> element or marked as important with the <code><a
    href="#strong">strong</a></code> element.
 
@@ -11486,7 +11490,7 @@
 <p>When a wormhole is created, a vortex normally forms.
 <strong>Warning: The vortex caused by the wormhole opening will
 annihilate anything in its path.</strong> Vortexes can be avoided when
-using sufficently advanced dialing technology.</p>
+using sufficiently advanced dialing technology.</p>
 
 <p><mark>An obstruction in a gate will prevent it from accepting a
 wormhole connection.</mark></p></pre>
@@ -11661,7 +11665,7 @@
 backfill the <abbr>WHATWG</abbr> issue graph.</p></pre>
   </div>
 
-  <p>If an abbreviation is pluralised, the expansion's grammatical number
+  <p>If an abbreviation is pluralized, the expansion's grammatical number
    (plural vs singular) must match the grammatical number of the contents of
    the element.
 
@@ -11791,7 +11795,7 @@
   <div class=example>
    <p>In the following snippet:</p>
 
-   <pre><p>Our first date was <time datetime="2006-09-23">a saturday</time>.</p></pre>
+   <pre><p>Our first date was <time datetime="2006-09-23">a Saturday</time>.</p></pre>
 
    <p>...the <code><a href="#time">time</a></code> element's <code
     title=dom-time-date><a href="#date0">date</a></code> attribute would have
@@ -12176,7 +12180,7 @@
   <p>There is no explicit way to specify units in the <code><a
    href="#meter">meter</a></code> element, but the units may be specified in
    the <code title=attr-title><a href="#title">title</a></code> attribute in
-   freeform text.
+   free-form text.
 
   <div class=example>
    <p>The example above could be extended to mention the units:</p>
@@ -12448,7 +12452,7 @@
 
   <p>The <code><a href="#code">code</a></code> element represents a fragment
    of computer code. This could be an XML element name, a filename, a
-   computer program, or any other string that a computer would recognise.
+   computer program, or any other string that a computer would recognize.
 
   <p>Although there is no formal way to indicate the language of computer
    code being marked up, authors who wish to mark <code><a
@@ -12486,7 +12490,7 @@
   </div>
 
   <p class=note>See the <code><a href="#pre">pre</a></code> element for more
-   detais.
+   details.
 
   <h4 id=the-var><span class=secno>3.10.14 </span>The <dfn
    id=var><code>var</code></dfn> element</h4>
@@ -12556,7 +12560,7 @@
    output from a program or computing system.
 
   <p class=note>See the <code><a href="#pre">pre</a></code> and <code><a
-   href="#kbd">kbd</a></code> elements for more detais.
+   href="#kbd">kbd</a></code> elements for more details.
 
   <div class=example>
    <p>This example shows the <code><a href="#samp">samp</a></code> element
@@ -12831,7 +12835,7 @@
   <p class=note>Style sheets can be used to format <code><a
    href="#i">i</a></code> elements, just like any other element can be
    restyled. Thus, it is not the case that content in <code><a
-   href="#i">i</a></code> elements will necessarily be italicised.
+   href="#i">i</a></code> elements will necessarily be italicized.
 
   <h4 id=the-b><span class=secno>3.10.20 </span>The <dfn
    id=b><code>b</code></dfn> element</h4>
@@ -12978,7 +12982,7 @@
 
   <h4 id=usage><span class=secno>3.10.22 </span>Usage summary</h4>
 
-  <p class=big-issue>We need to summarise the various elements, in particular
+  <p class=big-issue>We need to summarize the various elements, in particular
    to distinguish b/i/em/strong/var/q/mark/cite.</p>
   <!-- XXX when you do this, also reorder the elements in this section
   to bring the related ones closer together. -->
@@ -12998,7 +13002,7 @@
  <dt>Customer
  <dd>Hello! I wish to register a complaint. Hello. Miss?
  <dt>Shopkeeper
- <dd><span title="Coloquial pronounciation of 'What do you'"
+ <dd><span title="Colloquial pronunciation of 'What do you'"
  >Watcha</span> mean, miss?
  <dt>Customer
  <dd>Uh, I'm sorry, I have a cold. I wish to make a complaint.
@@ -13470,7 +13474,7 @@
 <img src="promblem-packed-action.png" alt="ROUGH COPY! Promblem-Packed Action!">
 
 <p>...was aired. A lawyer, armed with a Bigger Notebook, launched a
-pre-emptive strike using snowballs. A complete copy of the trailer is
+preemptive strike using snowballs. A complete copy of the trailer is
 included with Exhibit B.</p>
 
 <figure>
@@ -13648,7 +13652,7 @@
 </p></pre>
     </div>
 
-    <p>It is important to realise that the alternative text is a
+    <p>It is important to realize that the alternative text is a
      <em>replacement</em> for the image, not a description of the image.</p>
 
    <dt>Icons: a short phrase or label with an alternative graphical
@@ -13656,7 +13660,7 @@
 
    <dd>
     <p>A document can contain information in iconic form. The icon is
-     intended to help users of visual browsers to recognise features at a
+     intended to help users of visual browsers to recognize features at a
      glance.</p>
 
     <p>In some cases, the icon is supplemental to a text label conveying the
@@ -13707,7 +13711,7 @@
     </div>
 
     <p>Many pages include logos, insignia, flags, or emblems, which stand for
-     a particular entity such as a company, organisation, project, band,
+     a particular entity such as a company, organization, project, band,
      software package, country, or some such.</p>
 
     <p>If the logo is being used to represent the entity, the <code
@@ -13743,7 +13747,7 @@
  <h2>News</h2>
  <p>We have recently been looking at buying the <strong><img src="alpha.gif"
  alt=""> ΑΒΓ company</strong>, a small Greek company
- specialising in our type of product.</p></pre>
+ specializing in our type of product.</p></pre>
 
      <p>In this third snippet, we have a logo being used in an aside, as part
       of the larger article discussing the acquisition:</p>
@@ -13944,7 +13948,7 @@
     <p>When an image is included in a communication (such as an HTML e-mail)
      aimed at someone who is known to be able to view images, the <code
      title=attr-img-alt><a href="#alt">alt</a></code> attribute may be
-     omitted. However, even in such cases it is stongly recommended that
+     omitted. However, even in such cases it is strongly recommended that
      alternative text be included (as appropriate according to the kind of
      image involved, as described in the above entries), so that the e-mail
      is still usable should the user use a mail client that does not support
@@ -14647,8 +14651,8 @@
    for the purposes of this element.
 
   <p class=warning>Plugins are disabled in sandboxed browsing contexts
-   because they might not honour the restrictions imposed by the sandbox
-   (e.g. they might allow scripting even when scripting in the sandbox is
+   because they might not honor the restrictions imposed by the sandbox (e.g.
+   they might allow scripting even when scripting in the sandbox is
    disabled). User agents should convey the danger of overriding the sandbox
    to the user if an option to do so is provided.
 
@@ -15005,7 +15009,7 @@
      element's <a href="#fallback">fallback content</a>.
   </ol>
 
-  <p id=object-plugin>When the algorihm above instantiates a <a
+  <p id=object-plugin>When the algorithm above instantiates a <a
    href="#plugin">plugin</a>, the user agent should pass the names and values
    of all the <span title=concept-param-parameter>parameters</span> given by
    <code><a href="#param">param</a></code> elements that are children of the
@@ -15281,7 +15285,7 @@
    playback position</a> changes such that the last frame rendered is no
    longer the frame corresponding to the <a href="#current0">current playback
    position</a> in the video, the new frame must be rendered. Similarly, any
-   audio associated with the video must, if played, be played synchronised
+   audio associated with the video must, if played, be played synchronized
    with the <a href="#current0">current playback position</a>, at the
    specified <a href="#volume" title=dom-media-volume>volume</a> with the
    specified <a href="#muted" title=dom-media-muted>mute state</a>.
@@ -15482,7 +15486,7 @@
 
   <p>When an <code><a href="#audio1">audio</a></code> element is <a
    href="#actively">actively playing</a>, it must have its audio data played
-   synchronised with the <a href="#current0">current playback position</a>,
+   synchronized with the <a href="#current0">current playback position</a>,
    at the specified <a href="#volume" title=dom-media-volume>volume</a> with
    the specified <a href="#muted" title=dom-media-muted>mute state</a>.
 
@@ -16012,7 +16016,7 @@
    <dt><dfn id=empty title=dom-media-EMPTY><code>EMPTY</code></dfn> (numeric
     value 0)
 
-   <dd>The element has not yet been initialised. All attributes are in their
+   <dd>The element has not yet been initialized. All attributes are in their
     initial states.
 
    <dt><dfn id=loading0 title=dom-media-LOADING><code>LOADING</code></dfn>
@@ -16463,7 +16467,7 @@
 
   <p>The <dfn id=buffered
    title=dom-media-buffered><code>buffered</code></dfn> attribute must return
-   a static <a href="#normalised">normalised <code>TimeRanges</code>
+   a static <a href="#normalized">normalized <code>TimeRanges</code>
    object</a> that represents the ranges of the <a href="#media10">media
    resource</a>, if any, that the user agent has downloaded, at the time the
    attribute is evaluated.
@@ -16474,7 +16478,7 @@
 
   <p>The <dfn id=bufferedbytes
    title=dom-media-bufferedBytes><code>bufferedBytes</code></dfn> attribute
-   must return a static <a href="#normalised0">normalised
+   must return a static <a href="#normalized0">normalized
    <code>ByteRanges</code> object</a> that represents the ranges of the <a
    href="#media10">media resource</a>, if any, that the user agent has
    downloaded, at the time the attribute is evaluated.
@@ -16730,7 +16734,7 @@
     title=dom-media-DATA_UNAVAILABLE><a
     href="#dataunavailable">DATA_UNAVAILABLE</a></code> state. In video, this
     corresponds to the user agent having data for the current frame and the
-    next frame. In audio, this corresponds ot the user agent having data
+    next frame. In audio, this corresponds to the user agent having data
     beyond the <a href="#current0">current playback position</a>.
 
    <dt><dfn id=canplaythrough
@@ -16824,7 +16828,7 @@
    and thus without firing the <code title=event-canshowcurrentframe><a
    href="#canshowcurrentframe0">canshowcurrentframe</a></code> and <code
    title=event-canplay><a href="#canplay0">canplay</a></code> events. The
-   only state that is guarenteed to be reached is the <code
+   only state that is guaranteed to be reached is the <code
    title=dom-media-CAN_SHOW_CURRENT_FRAME><a
    href="#canshowcurrentframe">CAN_SHOW_CURRENT_FRAME</a></code> state, which
    is reached as part of the <code title=dom-media-load><a
@@ -17148,7 +17152,7 @@
    <a href="#ended">ended playback</a>, and false otherwise.
 
   <p>The <dfn id=played title=dom-media-played><code>played</code></dfn>
-   attribute must return a static <a href="#normalised">normalised
+   attribute must return a static <a href="#normalized">normalized
    <code>TimeRanges</code> object</a> that represents the ranges of the <a
    href="#media10">media resource</a>, if any, that the user agent has so far
    rendered, at the time the attribute is evaluated.
@@ -17263,7 +17267,7 @@
 
   <p>The <dfn id=seekable
    title=dom-media-seekable><code>seekable</code></dfn> attribute must return
-   a static <a href="#normalised">normalised <code>TimeRanges</code>
+   a static <a href="#normalized">normalized <code>TimeRanges</code>
    object</a> that represents the ranges of the <a href="#media10">media
    resource</a>, if any, that the user agent is able to seek to, at the time
    the attribute is evaluated, notwithstanding the looping attributes (i.e.
@@ -17356,7 +17360,7 @@
   <ol>
    <li>
     <p>Let <var title="">current ranges</var> be an ordered list of <a
-     href="#cue-ranges0" title="cue range">cue ranges</a>, initialised to
+     href="#cue-ranges0" title="cue range">cue ranges</a>, initialized to
      contain all the <a href="#cue-ranges0" title="cue range">cue ranges</a>
      of the <a href="#media7">media element</a> whose start times are less
      than or equal to the <a href="#current0">current playback position</a>
@@ -17365,7 +17369,7 @@
 
    <li>
     <p>Let <var title="">other ranges</var> be an ordered list of <a
-     href="#cue-ranges0" title="cue range">cue ranges</a>, initialised to
+     href="#cue-ranges0" title="cue range">cue ranges</a>, initialized to
      contain all the <a href="#cue-ranges0" title="cue range">cue ranges</a>
      of the <a href="#media7">media element</a> that are not present in <var
      title="">current ranges</var>, in the order they were added to the
@@ -17436,7 +17440,7 @@
   <p>The <dfn id=handleevent
    title=dom-voidCallback-handleEvent><code>handleEvent</code></dfn> method
    of objects implementing the <code><a
-   href="#voidcallback">VoidCallback</a></code> interface is the entrypoint
+   href="#voidcallback">VoidCallback</a></code> interface is the entry point
    for the callback represented by the object.
 
   <h5 id=user-interface><span class=secno>3.12.10.10. </span>User interface</h5>
@@ -17536,7 +17540,7 @@
    the number of ranges represented by the object.
 
   <p>When a <code><a href="#timeranges">TimeRanges</a></code> object is said
-   to be a <dfn id=normalised>normalised <code>TimeRanges</code>
+   to be a <dfn id=normalized>normalized <code>TimeRanges</code>
    object</dfn>, the ranges it represents must obey the following criteria:
 
   <ul>
@@ -17592,7 +17596,7 @@
    the number of ranges represented by the object.
 
   <p>When a <code><a href="#byteranges">ByteRanges</a></code> object is said
-   to be a <dfn id=normalised0>normalised <code>ByteRanges</code>
+   to be a <dfn id=normalized0>normalized <code>ByteRanges</code>
    object</dfn>, the ranges it represents must obey the following criteria:
 
   <ul>
@@ -18067,7 +18071,7 @@
    href="#width0">width</a></code> and <code title=attr-canvas-height><a
    href="#height0">height</a></code> attributes are set (whether to a new
    value or to the previous value), the bitmap and any associated contexts
-   must be cleared back to their initial state and reinitialised with the
+   must be cleared back to their initial state and reinitialized with the
    newly specified coordinate space dimensions.
 
   <p>The <dfn id=width1 title=dom-canvas-width><code>width</code></dfn> and
@@ -18088,7 +18092,7 @@
   context.fillRect(100,0,50,50); // only this square remains</pre>
   </div>
 
-  <p>When the canvas is initialised it must be set to fully transparent
+  <p>When the canvas is initialized it must be set to fully transparent
    black.
 
   <p>To draw on the canvas, authors must first obtain a reference to a <dfn
@@ -18187,7 +18191,7 @@
    title=canvas-context-2d><a href="#d">2d</a></code> argument a second time
    must return the same object.
 
-  <p>The 2D context represents a flat cartesian surface whose origin (0,0) is
+  <p>The 2D context represents a flat Cartesian surface whose origin (0,0) is
    at the top left corner, with the coordinate space having <var
    title="">x</var> values increasing when going right, and <var
    title="">y</var> values increasing when going down.
@@ -18597,7 +18601,7 @@
   </dl>
 
   <p>These values are all case-sensitive — they must be used exactly as
-   shown. User agents must not recognise values that do not exactly match the
+   shown. User agents must not recognize values that do not exactly match the
    values given above.
 
   <p>The operators in the above list must be treated as described by the
@@ -18609,7 +18613,7 @@
         <dd><cite>Compositing Digital Images</cite>, SIGGRAPH '84: Proceedings of the 11th annual conference on Computer graphics and interactive techniques, Volume 18, Number 3, T. Porter, T Duff. ACM Press, July 1984. ISBN 0-89791-138-5.</dd>
   -->
 
-  <p>On setting, if the user agent does not recognise the specified value, it
+  <p>On setting, if the user agent does not recognize the specified value, it
    must be ignored, leaving the value of <code
    title=dom-context-2d-globalCompositeOperation><a
    href="#globalcompositeoperation">globalCompositeOperation</a></code>
@@ -18641,8 +18645,8 @@
    href="#canvaspattern0">CanvasPattern</a></code>, then it must be ignored,
    and the attribute must retain its previous value.
 
-  <p>On getting, if the value is a color, then the <a href="#serialisation"
-   title="serialisation of a color">serialisation of the color</a> must be
+  <p>On getting, if the value is a color, then the <a href="#serialization"
+   title="serialization of a color">serialization of the color</a> must be
    returned. Otherwise, if it is not a color but a <code><a
    href="#canvasgradient0">CanvasGradient</a></code> or <code><a
    href="#canvaspattern0">CanvasPattern</a></code>, then the respective
@@ -18650,7 +18654,7 @@
    useful for assigning to other attributes or for comparison to other
    gradients or patterns.)
 
-  <p>The <dfn id=serialisation>serialisation of a color</dfn> for a color
+  <p>The <dfn id=serialization>serialization of a color</dfn> for a color
    value is a string, computed as follows: if it has alpha equal to 1.0, then
    the string is a lowercase six-digit hex value, prefixed with a "#"
    character (U+0023 NUMBER SIGN), with the first two digits representing the
@@ -18721,7 +18725,7 @@
    href="#createlineargradient">createLinearGradient()</a></code> are
    infinite or NaN, the method must raise an <code>INDEX_SIZE_ERR</code>
    exception. Otherwise, the method must return a linear <code><a
-   href="#canvasgradient0">CanvasGradient</a></code> initialised with the
+   href="#canvasgradient0">CanvasGradient</a></code> initialized with the
    specified line.
 
   <p>Linear gradients must be rendered such that at and before the starting
@@ -18736,8 +18740,8 @@
    title="">y<sub>0</sub></var> = <var
    title="">y<sub>1</sub></var></span>, then the linear gradient must paint
    nothing.</p>
-  <!-- XXX could make this paint the start colour,
-  or the end colour, or raise an exception -->
+  <!-- XXX could make this paint the start color,
+  or the end color, or raise an exception -->
 
   <p>The <dfn id=createradialgradient
    title=dom-context-2d-createRadialGradient><code>createRadialGradient(<var
@@ -18752,7 +18756,7 @@
    title="">r1</var> are negative, or if any of the arguments are infinite or
    NaN, an <code>INDEX_SIZE_ERR</code> exception must be raised. Otherwise,
    the method must return a radial <code><a
-   href="#canvasgradient0">CanvasGradient</a></code> initialised with the two
+   href="#canvasgradient0">CanvasGradient</a></code> initialized with the two
    specified circles, after transforming them according to the <a
    href="#transformations0" title=dom-context-2d-transformation>current
    transformation matrix</a>.
@@ -18769,7 +18773,7 @@
      title="">r<sub>1</sub></var></span>, then the radial gradient must paint
      nothing. Abort these steps.</p>
     <!-- XXX could make this
-   paint the start colour, or the end colour, or a circle of one in
+   paint the start color, or the end color, or a circle of one in
    the other, or raise an exception -->
     
 
@@ -18845,12 +18849,12 @@
    following values: <code title="">repeat</code>, <code
    title="">repeat-x</code>, <code title="">repeat-y</code>, <code
    title="">no-repeat</code>. If the empty string or null is specified, <code
-   title="">repeat</code> must be assumed. If an unrecognised value is given,
+   title="">repeat</code> must be assumed. If an unrecognized value is given,
    then the user agent must raise a <code>SYNTAX_ERR</code> exception. User
-   agents must recognise the four values described above exactly (e.g. they
+   agents must recognize the four values described above exactly (e.g. they
    must not do case folding). The method must return a <code><a
    href="#canvaspattern0">CanvasPattern</a></code> object suitably
-   initialised.
+   initialized.
 
   <p>The <var title="">image</var> argument must be an instance of an
    <code><a href="#htmlimageelement">HTMLImageElement</a></code> or <code><a
@@ -18868,7 +18872,7 @@
 
   <p>If the <var title="">image</var> argument is an <code><a
    href="#htmlcanvaselement">HTMLCanvasElement</a></code> object with either
-   a horizonal dimension or a vertical dimension equal to zero, then the
+   a horizontal dimension or a vertical dimension equal to zero, then the
    implementation must raise an <code>INVALID_STATE_ERR</code> exception.</p>
   <!-- drawImage() has an equivalent paragraph -->
 
@@ -18972,7 +18976,7 @@
 
   <p>The <code>miter</code> value means that a second filled triangle must
    (if it can given the miter length) be rendered at the join, with one line
-   being the line between the two aforementioned corners, abuting the first
+   being the line between the two aforementioned corners, abutting the first
    triangle, and the other two being continuations of the outside edges of
    the two joining lines, as long as required to intersect without going over
    the miter length.
@@ -19030,8 +19034,8 @@
    href="#shadowcolor">shadowColor</a></code> attribute initially must be
    fully-transparent black.
 
-  <p>On getting, the <a href="#serialisation" title="serialisation of a
-   color">serialisation of the color</a> must be returned.
+  <p>On getting, the <a href="#serialization" title="serialization of a
+   color">serialization of the color</a> must be returned.
 
   <p>On setting, the new value must be parsed as a CSS <color> value
    and the color assigned. If the value is not a valid color, then it must be
@@ -19423,13 +19427,13 @@
    region, without affecting the actual subpaths. The new clipping region
    replaces the current clipping region.
 
-  <p>When the context is initialised, the clipping region must be set to the
+  <p>When the context is initialized, the clipping region must be set to the
    rectangle with the top left corner at (0,0) and the width and height of
    the coordinate space.</p>
   <!-- XXXv4
    Jordan OSETE suggests:
     * support ways of extending the clipping region (union instead of intersection)
-       - also "add", "substract", "replace", "intersect" and "xor"
+       - also "add", "subtract", "replace", "intersect" and "xor"
     * support ways of resetting the clipping region without save/restore
   -->
 
@@ -19465,10 +19469,10 @@
    very ugly.
 
   <p>On getting, the <code title=dom-context-2d-font><a
-   href="#font">font</a></code> attribute must return the serialised form of
+   href="#font">font</a></code> attribute must return the serialized form of
    the current font of the context. <a
    href="#refsCSSOM">[CSSOM]</a><!-- XXX ensure that this
-  defines serialisation of 'font' -->
+  defines serialization of 'font' -->
 
   <p>When the context is created, the font of the context must be set to 10px
    sans-serif. When the 'font-size' component is set to lengths using
@@ -19610,7 +19614,7 @@
      hypothetical width of the inline box in the hypothetical line box is
      greater than <var title="">maxWidth</var> CSS pixels, then change <var
      title="">font</var> to have a more condensed font (if one is available
-     or if a reasonably readable one can be synthesised by applying a
+     or if a reasonably readable one can be synthesized by applying a
      horizontal scale factor to the font) or a smaller font, and return to
      the previous step.
 
@@ -19792,7 +19796,7 @@
    in the hypothetical line box is greater than <var
    title="">maxHeight</var> CSS pixels, then change <var
    title="">font</var> to have a more condensed font (if one is
-   available or if a reasonably readable one can be synthesised by
+   available or if a reasonably readable one can be synthesized by
    applying an appropriate scale factor to the font) or a smaller
    font, and return to the previous step.</p></li>
 
@@ -19984,7 +19988,7 @@
   <!-- createPattern() has an equivalent paragraph -->
   <!-- handled by the next paragraph
   <p>If the <var title="">image</var> argument is an
-  <code>HTMLCanvasElement</code> object with either a horizonal
+  <code>HTMLCanvasElement</code> object with either a horizontal
   dimension or a vertical dimension equal to zero, then the
   implementation must raise an <code>INVALID_STATE_ERR</code>
   exception.</p>
@@ -20067,7 +20071,7 @@
    title="">sx</var>, <var title="">sy</var>, <var title="">sw</var>, <var
    title="">sh</var>)</code></dfn> method must return an <code><a
    href="#imagedata">ImageData</a></code> object representing the underlying
-   pixel data for the area of the canvas denoted by the rectanglewhose
+   pixel data for the area of the canvas denoted by the rectangle whose
    corners are the four points (<var title="">sx</var>, <var
    title="">sy</var>), (<span><var title="">sx</var>+<var
    title="">sw</var></span>, <var title="">sy</var>), (<span><var
@@ -20087,14 +20091,14 @@
    exception.
 
   <p><code><a href="#imagedata">ImageData</a></code> objects must be
-   initialised so that their <dfn id=width3
+   initialized so that their <dfn id=width3
    title=dom-imagedata-width><code>width</code></dfn> attribute is set to
    <var title="">w</var>, the number of physical device pixels per row in the
    image data, their <dfn id=height2
    title=dom-imagedata-height><code>height</code></dfn> attribute is set to
    <var title="">h</var>, the number of rows in the image data, and the <dfn
    id=data1 title=dom-imagedata-data><code>data</code></dfn> attribute is
-   initialised to an array of <var title="">h</var>×<var
+   initialized to an array of <var title="">h</var>×<var
    title="">w</var>×4 integers. The pixels must be represented in this
    array in left-to-right order, row by row, starting at the top left, with
    each pixel's red, green, blue, and alpha components being given in that
@@ -20130,7 +20134,7 @@
    method writes data from <code><a href="#imagedata">ImageData</a></code>
    structures back to the canvas.
 
-  <p>If the first argment to the method is null or not an <code><a
+  <p>If the first argument to the method is null or not an <code><a
    href="#imagedata">ImageData</a></code> object that was returned by <code
    title=dom-context-2d-createImageData><a
    href="#createimagedata">createImageData()</a></code> or <code
@@ -20218,7 +20222,7 @@
      title="">dirtyWidth</var></span></span> and <span><var
      title="">dirtyY</var> ≤ <var
      title="">y</var> < <span><var title="">dirtyY</var>+<var
-     title="">dirtyHeight</var></span></span>, copy the four channels of thr
+     title="">dirtyHeight</var></span></span>, copy the four channels of the
      pixel with coordinate (<var title="">x</var>, <var title="">y</var>) in
      the <var title="">imagedata</var> data structure to the pixel with
      coordinate (<span><var title="">x<sub>device</sub></var>+<var
@@ -20363,8 +20367,8 @@
    <li>
     <p>Render the shape or image, creating image <var title="">A</var>, as
      described in the previous sections. For shapes, the current fill,
-     stroke, and line styles must be honoured, and the stroke must itself
-     also be subjected to the current transformation matrix.
+     stroke, and line styles must be honored, and the stroke must itself also
+     be subjected to the current transformation matrix.
 
    <li>
     <p>If shadows are supported:</p>
@@ -20403,7 +20407,7 @@
   <h5 id=color><span class=secno>3.12.11.2. </span>Color spaces and color
    correction</h5>
 
-  <p>The <code><a href="#canvas">canvas</a></code> APIs must perform colour
+  <p>The <code><a href="#canvas">canvas</a></code> APIs must perform color
    correction at only two points: when rendering images with their own gamma
    correction and color space information onto the canvas, to convert the
    image to the color space used by the canvas (e.g. using the <code
@@ -20551,7 +20555,7 @@
 };</pre>
   </dl>
 
-  <p>The <code><a href="#map">map</a></code> element, in conjuction with any
+  <p>The <code><a href="#map">map</a></code> element, in conjunction with any
    <code><a href="#area">area</a></code> element descendants, defines an <a
    href="#image">image map</a>.
 
@@ -20715,7 +20719,7 @@
      <td>Non-conforming
   </table>
 
-  <p>The attribute may be ommited. The <i>missing value default</i> is the <a
+  <p>The attribute may be omitted. The <i>missing value default</i> is the <a
    href="#rectangle" title=attr-area-shape-rect>rectangle</a> state.
 
   <p>The <dfn id=coords title=attr-area-coords><code>coords</code></dfn>
@@ -21144,7 +21148,7 @@
   <p>User agents must act as if any MathML element whose contents does not
    match the element's content model was replaced, for the purposes of MathML
    layout and rendering, by an <code title="">merror</code> element in the <a
-   href="#mathml0">MathML namespace</a> containing some appropiate error
+   href="#mathml0">MathML namespace</a> containing some appropriate error
    message.
 
   <p>To enable authors to use MathML tools that only accept MathML in its XML
@@ -21294,7 +21298,7 @@
 
      <li>One or more <code><a href="#tr">tr</a></code> elements. <strong
       class=note>(Only expressible in the <span title="">XML
-      serialisation</span><!-- XXX xref -->.)</strong>
+      serialization</span><!-- XXX xref -->.)</strong>
     </ul>
 
    <li>
@@ -22199,7 +22203,7 @@
    slots from <span><var title="">y</var>=0</span> to <span><var
    title="">y</var>=<var title="">y<sub title="">height</sub></var>-1</span>,
    for a particular value of <var title="">x</var>. Columns can correspond to
-   <code><a href="#col">col</a></code> elements, but in the absense of
+   <code><a href="#col">col</a></code> elements, but in the absence of
    <code><a href="#col">col</a></code> elements are implied.
 
   <p>A <dfn id=row-group title=concept-row-group>row group</dfn> is a set of
@@ -22289,7 +22293,7 @@
    <li> <!-- this step is here just so that we can be sure to have a first
     element in the next step, so that we can set up the "advance"
     exception-handling thingy below; otherwise it'd be more
-    complicated. it's not a perf optimisation per se. -->
+    complicated. it's not a perf optimization per se. -->
     
     <p>If the <code><a href="#table">table</a></code> element has no children
      elements, then return <var title="">the table</var> (which will be
@@ -23035,8 +23039,8 @@
    href="#refsUNICODE">[UNICODE]</a>
 
   <p>User agents may remove <a href="#empty0" title="empty data cell">empty
-   data cells</a> when analysing data in a <span title="concept
-   table">table</span>.
+   data cells</a> when analyzing data in a <a href="#table1"
+   title=concept-table>table</a>.
 
   <h3 id=forms><span class=secno>3.14 </span>Forms</h3>
   <!-- XXX everything in WF2 -->
@@ -23688,9 +23692,9 @@
 
   <p class=note><strong>The <code><a href="#noscript">noscript</a></code>
    element is only effective in the <span title="">HTML
-   serialisation</span><!-- XXX
+   serialization</span><!-- XXX
   xref -->, it has no effect in the <span
-   title="">XML serialisation</span><!-- XXX xref -->.</strong>
+   title="">XML serialization</span><!-- XXX xref -->.</strong>
 
   <p>When used in <a href="#html-">HTML documents</a>, the allowed content
    model is as follows:
@@ -24940,7 +24944,7 @@
 
     <p class=big-issue><!-- select-provider-selection
     XXX-->autoselect
-     some rows when initialised, reflect the selection in the select, reflect
+     some rows when initialized, reflect the selection in the select, reflect
      the multiple attribute somehow.</p>
 
     <p>The data provider must call the <code><a
@@ -25031,7 +25035,7 @@
      href="#getrowmenu">getRowMenu(<var title="">i</var>)</a></code> must
      return the first <code><a href="#menu">menu</a></code> element
      descendant (in the real DOM) of the row's element, that is not also a
-     descendant of another element in the filtered view that is a decsendant
+     descendant of another element in the filtered view that is a descendant
      of the row's element. (This is analogous to the image case above.)</p>
 
     <p><code title=dom-provider-getRowClasses><a
@@ -25626,16 +25630,16 @@
     href="#unchecked">unchecked</a></code> class applies to the cell. If it
     does, the cell is unchecked. Otherwise, the <code
     title=datagrid-cell-class-indeterminate><a
-    href="#indeterminate">indeterminate</a></code> class appplies to the cell
+    href="#indeterminate">indeterminate</a></code> class applies to the cell
     and the cell's checkbox is in an indeterminate state. When the <code
     title=datagrid-cell-class-indeterminate><a
-    href="#indeterminate">indeterminate</a></code> class appplies to the
-    cell, the checkbox is a tristate checkbox, and the user can set it to the
+    href="#indeterminate">indeterminate</a></code> class applies to the cell,
+    the checkbox is a tristate checkbox, and the user can set it to the
     indeterminate state. Otherwise, only the <code
     title=datagrid-cell-class-checked><a href="#checked">checked</a></code>
     and/or <code title=datagrid-cell-class-unchecked><a
     href="#unchecked">unchecked</a></code> classes apply to the cell, and the
-    cell can only be toggled betwen those two states.
+    cell can only be toggled between those two states.
   </dl>
 
   <p>If the data provider ever raises an exception while the <code><a
@@ -25673,7 +25677,7 @@
    match the calls made to the update methods, the user agent may disable the
    <code><a href="#datagrid0">datagrid</a></code>. User agents that do not
    disable the <code><a href="#datagrid0">datagrid</a></code> in inconsistent
-   cases must honour the most recently returned values.
+   cases must honor the most recently returned values.
 
   <p>User agents may cache returned values so that the data provider is never
    asked for data that could contradict earlier data. User agents must not
@@ -25723,7 +25727,7 @@
    title=dom-datagrid-updateRowsInserted><code>updateRowsInserted(<var
    title="">row</var>, <var title="">count</var>)</code></dfn> method is
    called, the user agent must assume that <var title="">count</var> new rows
-   have been inserted, such that the first new row is indentified by <var
+   have been inserted, such that the first new row is identified by <var
    title="">row</var>. The user agent must update its rendering and the
    selection accordingly. The new rows should not be selected.
 
@@ -25863,7 +25867,7 @@
    selected, but this can be changed via the methods described in this
    section. <!--XXX
   select-provider-selection The default data provider, for instance,
-  changes which rows are selected when it is first initialised.-->
+  changes which rows are selected when it is first initialized.-->
 
   <p>The selection of a <code><a href="#datagrid0">datagrid</a></code> is
    represented by its <dfn id=selection0
@@ -26221,7 +26225,7 @@
    happen.
 
   <p class=big-issue> should change all the above so it actually is just
-   trigged by a click event, then we could remove the shadowing click()
+   triggered by a click event, then we could remove the shadowing click()
    method and rely on actual events.
 
   <p class=big-issue>Need to define the command="" attribute
@@ -26368,7 +26372,7 @@
    <li><a href="about.html">About</a></li>
   </menu>
  </li>
-</menubar>
+</menu>
 
 ...
 
@@ -26397,7 +26401,7 @@
    </select>
    <span><input type="submit" value="Go"></span>
   </menu>
- </menubar>
+ </menu>
 </form></pre>
 
 <form ...>
@@ -27704,7 +27708,7 @@
      the mode, and the <var title="">existing nodes</var> lists as the lists
      of existing nodes.
    </li>
-   <!--(for now, since we can't guarentee that we'll reset the dataNode
+   <!--(for now, since we can't guarantee that we'll reset the dataNode
 attribute of nodes that are dynamically moved around between regens,
 we'll just act as if the dataNode attribute is set on creation and
 never reset. This is nice and consistent.)
@@ -27719,7 +27723,7 @@
   <p>The Levenberg algorithm consists of two algorithms that invoke each
    other recursively, the <a href="#levenberg">Levenberg data node
    algorithm</a> and the <a href="#levenberg0">Levenberg template node
-   algorithm</a>. These algorithms use the data structures initialised by the
+   algorithm</a>. These algorithms use the data structures initialized by the
    set of steps described above.
 
   <p>The <dfn id=levenberg>Levenberg data node algorithm</dfn> is as follows.
@@ -28313,7 +28317,7 @@
    contexts</a> must execute on a single conceptual thread. The dispatch of
    events fired by the user agent (e.g. in response to user actions or
    network activity) and the execution of any scripts associated with timers
-   must be serialised so that for each <a href="#unit-of">unit of related
+   must be serialized so that for each <a href="#unit-of">unit of related
    browsing contexts</a> there is only one script being executed at a time.</p>
   <!-- XXX queue concept should be made generic across the spec.
    "Once no other scripts are executing in the <span>unit of
@@ -28337,7 +28341,7 @@
    title="">_blank</code>, <code title="">_self</code>, <code
    title="">_parent</code>, or <code title="">_top</code>.
 
-  <p><dfn id=the-rules>The rules for chosing a browsing context given a
+  <p><dfn id=the-rules>The rules for choosing a browsing context given a
    browsing context name</dfn> are as follows. The rules assume that they are
    being applied in the context of a <a href="#browsing1">browsing
    context</a>.
@@ -28583,7 +28587,7 @@
     title="">w</var>, in unsigned long <var title="">h</var>)</code></dfn>
 
    <dd>
-    <p>When invoked as corstructors, these must return a new <code><a
+    <p>When invoked as constructors, these must return a new <code><a
      href="#htmlimageelement">HTMLImageElement</a></code> object (a new
      <code><a href="#img">img</a></code> element). If the <var
      title="">h</var> argument is present, the new object's <code
@@ -28647,7 +28651,7 @@
 
   <p>When the method is invoked, the user agent must first select a <a
    href="#browsing1">browsing context</a> to navigate by applying <a
-   href="#the-rules">the rules for chosing a browsing context given a
+   href="#the-rules">the rules for choosing a browsing context given a
    browsing context name</a> using the <var title="">target</var> argument as
    the name and the <a href="#browsing1">browsing context</a> of the script
    as the context in which the algorithm is executed, unless the user has
@@ -28669,7 +28673,7 @@
    href="#replacement" title="replacement enabled">replacement must be
    enabled</a>; otherwise, it must not be enabled unless the <a
    href="#browsing1">browsing context</a> was just created as part of the <a
-   href="#the-rules">the rules for chosing a browsing context given a
+   href="#the-rules">the rules for choosing a browsing context given a
    browsing context name</a>. The navigation must be done with the <a
    href="#browsing1">browsing context</a> corresponding to the <code><a
    href="#window">Window</a></code> object that is the <a
@@ -28929,13 +28933,13 @@
 
     <p>When a <code>Document</code> is created, unless stated otherwise
      above, its <a href="#effective3">effective script origin</a> is
-     initialised to the <a href="#origin0">origin</a> of the
+     initialized to the <a href="#origin0">origin</a> of the
      <code>Document</code>. However, the <code title=dom-document-domain><a
      href="#domain">document.domain</a></code> attribute can be used to
      change it.</p>
   </dl>
 
-  <p>The <dfn id=serialisation0>serialisation of an origin</dfn> is the
+  <p>The <dfn id=serialization0>serialization of an origin</dfn> is the
    string obtained by applying the following algorithm to the given <a
    href="#origin0">origin</a>:
 
@@ -29000,7 +29004,7 @@
    restriction</h4>
 
   <p>The <dfn id=domain title=dom-document-domain><code>domain</code></dfn>
-   attribute on <code>Document</code> objects must be initialised to <a
+   attribute on <code>Document</code> objects must be initialized to <a
    href="#domain0">the document's domain</a>, if it has one, and the empty
    string otherwise. On getting, the attribute must return its current value,
    unless the document was created by <code>XMLHttpRequest</code>, in which
@@ -29793,8 +29797,8 @@
     <p>The three arguments passed to the function are all
      <code>DOMString</code>s; the first must give the message that the UA is
      considering reporting, the second must give the URI to the resource in
-     which the error occured, and the third must give the line number in that
-     resource on which the error occured.</p>
+     which the error occurred, and the third must give the line number in
+     that resource on which the error occurred.</p>
 
     <p>If the function returns false, then the error should not be reported
      to the user. Otherwise, if the function returns another value (or does
@@ -29992,7 +29996,7 @@
 
   <p>These browsing contexts also have an associated <dfn id=return>return
    value</dfn>. The <a href="#return">return value</a> of a browsing context
-   must be initialised to the empty string when the browsing context is
+   must be initialized to the empty string when the browsing context is
    created.
 
   <p>The <dfn id=returnvalue
@@ -30123,7 +30127,7 @@
      <pre>http://example.com/soup?url=http%3A%2F%2Fwww.example.net%2Fchickenk%C3%AFwi.soup</pre>
 
      <p>This site could then fetch the <code>chickenk&#xEF;wi.soup</code>
-      file and do whatever it is that it does with soup (synthesise it and
+      file and do whatever it is that it does with soup (synthesize it and
       ship it to the user, or whatever).</p>
     </div>
 
@@ -30188,9 +30192,9 @@
    User agents should gracefully handle such hostile attempts, protecting the
    user.
 
-  <p><strong>Misleading titles.</strong> User agents should not rely wholy on
-   the <var title="">title</var> argument to the methods when presenting the
-   registered handlers to the user, since sites could easily lie. For
+  <p><strong>Misleading titles.</strong> User agents should not rely wholly
+   on the <var title="">title</var> argument to the methods when presenting
+   the registered handlers to the user, since sites could easily lie. For
    example, a site <code>hostile.example.net</code> could claim that it was
    registering the "Cuddly Bear Happy Content Handler". User agents should
    therefore use the handler's domain in any UI along with any title.
@@ -30428,7 +30432,7 @@
     </dl>
 
     <p class=note>A URI in the list can be flagged with multiple different
-     types, and thus an entry can end up being categorised as multiple
+     types, and thus an entry can end up being categorized as multiple
      entries. For example, an entry can be an explicit entry and a dynamic
      entry at the same time.</p>
 
@@ -30599,7 +30603,7 @@
 
   <ol>
    <li>
-    <p>The user agent must decode the bytestream corresponding with the
+    <p>The user agent must decode the byte stream corresponding with the
      manifest to be parsed, treating it as UTF-8. Bytes or sequences of bytes
      that are not valid UTF-8 sequences must be interpreted as a U+FFFD
      REPLACEMENT CHARACTER. <!--All U+0000 NULL characters must
@@ -30625,7 +30629,7 @@
 
    <li>
     <p>Let <var title="">input</var> be the decoded text of the manifest's
-     bytestream.
+     byte stream.
 
    <li>
     <p>Let <var title="">position</var> be a pointer into <var
@@ -30854,7 +30858,7 @@
 
    <li>
     <p>If there is already a resource with the URI of <var title="">manifest
-     URI</var> in <var title="">cache</var>, and that resource is categorised
+     URI</var> in <var title="">cache</var>, and that resource is categorized
      as a <a href="#the-manifest"
      title=concept-appcache-manifest>manifest</a>, then this is an <dfn
      id=upgrade title=concept-appcache-upgrade>upgrade attempt</dfn>.
@@ -31028,7 +31032,7 @@
      <li>
       <p>Fetch the resource. If this is an <a href="#upgrade"
        title=concept-appcache-upgrade>upgrade attempt</a>, then use <var
-       title="">cache</var> as an HTTP cache, and honour HTTP caching
+       title="">cache</var> as an HTTP cache, and honor HTTP caching
        semantics (such as expiration, ETags, and so forth) with respect to
        that cache. User agents may also have other caches in place that are
        also honored. If the resource in question is already being downloaded
@@ -31055,34 +31059,34 @@
 
      <li>
       <p>If the URI being processed was flagged as an "explicit entry" in
-       <var title="">file list</var>, then categorise the entry as an <a
+       <var title="">file list</var>, then categorize the entry as an <a
        href="#explicit" title=concept-appcache-explicit>explicit entry</a>.
 
      <li>
       <p>If the URI being processed was flagged as a "fallback entry" in <var
-       title="">file list</var>, then categorise the entry as a <a
+       title="">file list</var>, then categorize the entry as a <a
        href="#fallback0" title=concept-appcache-fallback>fallback entry</a>.
 
      <li>
       <p>If the URI being processed was flagged as a "opportunistic entry" in
-       <var title="">file list</var>, then categorise the entry as an <a
+       <var title="">file list</var>, then categorize the entry as an <a
        href="#opportunistically"
        title=concept-appcache-oppcache>opportunistically cached entry</a>.
 
      <li>
       <p>If the URI being processed was flagged as an "implicit entry" in
-       <var title="">file list</var>, then categorise the entry as a <a
+       <var title="">file list</var>, then categorize the entry as a <a
        href="#implicit" title=concept-appcache-implicit>implicit entry</a>.
 
      <li>
       <p>If the URI being processed was flagged as an "dynamic entry" in <var
-       title="">file list</var>, then categorise the entry as a <a
+       title="">file list</var>, then categorize the entry as a <a
        href="#dynamic3" title=concept-appcache-dynamic>dynamic entry</a>.
     </ol>
 
    <li>
     <p>Store <var title="">manifest</var> in <var title="">new cache</var>,
-     if it's not there already, and categorise this entry (whether newly
+     if it's not there already, and categorize this entry (whether newly
      added or not) as <a href="#the-manifest"
      title=concept-appcache-manifest>the manifest</a>.
 
@@ -31218,7 +31222,7 @@
     href="#top-level">top-level browsing context</a>
 
    <dd>
-    <p>As an optimisation, if the resource was loaded from an <a
+    <p>As an optimization, if the resource was loaded from an <a
      href="#application0">application cache</a>, and the manifest URI of that
      cache doesn't match the manifest URI with which the algorithm was
      invoked, then the user agent should mark the entry in that application
@@ -31278,9 +31282,9 @@
       <p>If there is already an <a href="#application0">application cache</a>
        identified by this manifest URI, and the most up to date version of
        that <a href="#application0">application cache</a> contains a resource
-       with the URI of the manifest, and that resource is categorised as a <a
+       with the URI of the manifest, and that resource is categorized as a <a
        href="#the-manifest" title=concept-appcache-manifest>manifest</a>,
-       then: store the resource in the matching cache, categorised as an <a
+       then: store the resource in the matching cache, categorized as an <a
        href="#implicit" title=concept-appcache-implicit>implicit entry</a>,
        associate the <code>Document</code> with that cache, invoke the <a
        href="#application1">application cache update process</a>, and abort
@@ -31298,9 +31302,9 @@
        identified by this manifest URI, then the most up to date version of
        that <a href="#application0">application cache</a> does not yet
        contain a resource with the URI of the manifest, or it does but that
-       resource is not yet categorised as a <a href="#the-manifest"
+       resource is not yet categorized as a <a href="#the-manifest"
        title=concept-appcache-manifest>manifest</a>: store the resource in
-       that cache, categorised as an <a href="#implicit"
+       that cache, categorized as an <a href="#implicit"
        title=concept-appcache-implicit>implicit entry</a> (replacing the
        file's previous contents if it was already in the cache, but not
        removing any other categories it might have), and abort these steps.
@@ -31310,7 +31314,7 @@
      <li>
       <p>Otherwise, there is no matching <a href="#application0">application
        cache</a>: create a new application cache identified by this manifest
-       URI, store the resource in that cache, categorised as an <a
+       URI, store the resource in that cache, categorized as an <a
        href="#implicit" title=concept-appcache-implicit>implicit entry</a>,
        and then invoke the <a href="#application1">application cache update
        process</a>.
@@ -31473,7 +31477,7 @@
      cache</a> whose group is in the <i>idle</i> <span
      title=concept-appcache-states>update status</span>, and that application
      cache is the newest cache in its group that contains a resource
-     categorised as a <a href="#the-manifest"
+     categorized as a <a href="#the-manifest"
      title=concept-appcache-manifest>manifest</a>.
 
    <dt><dfn id=checking
@@ -31505,7 +31509,7 @@
      cache</a> whose group is in the <i>idle</i> <span
      title=concept-appcache-states>update status</span>, but that application
      cache is <em>not</em> the newest cache in its group that contains a
-     resource categorised as a <a href="#the-manifest"
+     resource categorized as a <a href="#the-manifest"
      title=concept-appcache-manifest>manifest</a>.
   </dl>
 
@@ -31560,7 +31564,7 @@
      href="#application0">application cache</a> with which the <code><a
      href="#applicationcache">ApplicationCache</a></code> object is
      associated that has the address <var title="">uri</var>, then ensure
-     that entry is categorised as a <a href="#dynamic3"
+     that entry is categorized as a <a href="#dynamic3"
      title=concept-appcache-dynamic>dynamic entry</a> and return and abort
      these steps.
 
@@ -31589,7 +31593,7 @@
      associated.</p>
 
     <p>Add the fetched resource to the <a href="#application0">application
-     cache</a> and categorise it as a <a href="#dynamic3"
+     cache</a> and categorize it as a <a href="#dynamic3"
      title=concept-appcache-dynamic>dynamic entry</a> before letting any such
      scripts resume.</p>
   </ol>
@@ -31605,11 +31609,11 @@
   <p>The <dfn id=remove1 title=dom-appcache-remove><code>remove(<var
    title="">uri</var>)</code></dfn> method must remove the <a
    href="#dynamic3" title=concept-appcache-dynamic>dynamic entry</a>
-   categorisation of any entry with the address <var title="">uri</var> in
+   categorization of any entry with the address <var title="">uri</var> in
    the <a href="#application0">application cache</a> with which the <code><a
    href="#applicationcache">ApplicationCache</a></code> object is associated.
    <span class=big-issue>Resolve relative URIs... (ignore syntax
-   errors)</span> If this removes the last categorisation of an entry in that
+   errors)</span> If this removes the last categorization of an entry in that
    cache, then the entry must be removed entirely (such that if it is
    re-added, it will be loaded from the network again). If the <code><a
    href="#applicationcache">ApplicationCache</a></code> object is not
@@ -31657,7 +31661,7 @@
 
    <li>
     <p>Check that there is an application cache in the same group as <var
-     title="">cache</var> which has an entry categorised as a <a
+     title="">cache</var> which has an entry categorized as a <a
      href="#the-manifest" title=concept-appcache-manifest>manifest</a> that
      has is newer than <var title="">cache</var>. If there is not, then raise
      an <code>INVALID_STATE_ERR</code> exception and abort these steps.
@@ -31665,7 +31669,7 @@
    <li>
     <p>Let <var title="">new cache</var> be the newest <a
      href="#application0">application cache</a> in the same group as <var
-     title="">cache</var> which has an entry categorised as a <a
+     title="">cache</var> which has an entry categorized as a <a
      href="#the-manifest" title=concept-appcache-manifest>manifest</a>.
 
    <li>
@@ -32351,7 +32355,7 @@
      href="#same-origin">same origin</a> as the URI in question, and that
      have this URI as one of their entries (excluding entries marked as <a
      href="#foreign" title=concept-appcache-foreign>foreign</a>), and that
-     already contain their manifest, categorised as a <a href="#the-manifest"
+     already contain their manifest, categorized as a <a href="#the-manifest"
      title=concept-appcache-manifest>manifest</a>. If so, then the user agent
      must then fetch the resource from the <a href="#select0"
      title=concept-appcache-selection>most appropriate application cache</a>
@@ -32423,7 +32427,7 @@
        didn't cancel the request, the user agent must cache the resource in
        all the application caches that have a <a href="#matches"
        title=concept-appcache-matches-oppcache>matching opportunistic caching
-       namespace</a>, categorised as <a href="#opportunistically"
+       namespace</a>, categorized as <a href="#opportunistically"
        title=concept-appcache-oppcache>opportunistically cached entries</a>.
        Meanwhile, the user must continue along these steps.</p>
     </dl>
@@ -33290,7 +33294,7 @@
            title="">index<sub>stream</sub></var> to the next byte in the byte
            stream.</p>
 
-         <dt>Otherwies, if the <var title="">index<sub>stream</sub></var>th
+         <dt>Otherwise, if the <var title="">index<sub>stream</sub></var>th
           byte of the pattern is a "<em>WS</em>" byte:
 
          <dd>
@@ -33703,7 +33707,7 @@
     <p>Otherwise, the sniffed type of the resource is "text/html".
   </ol>
 
-  <p class=note>For efficiency reaons, implementations may wish to implement
+  <p class=note>For efficiency reasons, implementations may wish to implement
    this algorithm and the algorithm for detecting the character encoding of
    HTML documents in parallel.
 
@@ -33723,7 +33727,7 @@
    are multiple Content-Type HTTP headers and one of the other ones is
    syntactically correct). <a href="#refsHTTP">[HTTP]</a>
 
-  <p>For resources fetched from the filesystem, user agents should use
+  <p>For resources fetched from the file system, user agents should use
    platform-specific conventions, e.g. operating system extension/type
    mappings.
 
@@ -33775,7 +33779,7 @@
 
      <dd>
       <p>Return the string between this character and the next earliest
-       occurance of this character.
+       occurrence of this character.
 
      <dt>If it is an unmatched U+0022 QUOTATION MARK ('"')
 
@@ -33860,7 +33864,7 @@
   <p>The second storage mechanism is designed for storage that spans multiple
    windows, and lasts beyond the current session. In particular, Web
    applications may wish to store megabytes of user data, such as entire
-   user-authored documents or a user's mailbox, on the clientside for
+   user-authored documents or a user's mailbox, on the client side for
    performance reasons.
 
   <p>Again, cookies do not handle this case well, because they are
@@ -34218,7 +34222,7 @@
    areas simultaneously in a predictable manner. Scripts must not be able to
    detect any concurrent script execution.
 
-  <p>This is required to guarentee that the <code title=dom-Storage-length><a
+  <p>This is required to guarantee that the <code title=dom-Storage-length><a
    href="#length9">length</a></code> attribute of a <code><a
    href="#storage0">Storage</a></code> object never changes while a script is
    executing, other than in a way that is predictable by the script itself.
@@ -34251,7 +34255,7 @@
   <p class=big-issue>...</p>
   <!-- include an example that does something like the following to show
 you should never embed strings straight into the statement, even when you
-have a variable and unknownable number of literals coming:
+have a variable and unknowable number of literals coming:
    var q = "";
    for each (var i in array)
      q += (q == "" ? "" : ", ") + "?";
@@ -34308,7 +34312,7 @@
    names (e.g. using a hashing algorithm) to the supported set of names.
 
   <p>User agents are expected to use the display name and the estimated
-   database size to optimise the user experience. For example, a user agent
+   database size to optimize the user experience. For example, a user agent
    could use the estimated size to suggest an initial quota to the user. This
    allows a site that is aware that it will try to use hundreds of megabytes
    to declare this upfront, instead of the user agent prompting the user for
@@ -34450,7 +34454,7 @@
      placeholder gets replaced by the <var title="">n</var>th value in the
      <var title="">arguments</var> array.)</p>
 
-    <p>If the second argument is ommitted or null, then treat the <var
+    <p>If the second argument is omitted or null, then treat the <var
      title="">arguments</var> array as empty.</p>
 
     <p>The result is <i>the statement</i>.</p>
@@ -34488,7 +34492,7 @@
 
   <p>The user agent must act as if the database was hosted in an otherwise
    completely empty environment with no resources. For example, attempts to
-   read from or write to the filesystem will fail.
+   read from or write to the file system will fail.
 
   <p>SQL inherently supports multiple concurrent connections. Authors should
    make appropriate use of the transaction features to handle the case of
@@ -34647,7 +34651,7 @@
   <p>The <dfn id=message
    title=dom-SQLError-message><code>message</code></dfn> DOM attribute must
    return an error message describing the error encountered. The message
-   should be localised to the user's language.
+   should be localized to the user's language.
 
   <h5 id=processing3><span class=secno>4.11.2.6. </span>Processing model</h5>
 
@@ -34664,7 +34668,7 @@
      that transaction.
 
    <li>
-    <p>If an error occured in the opening of the transaction, jump to the
+    <p>If an error occurred in the opening of the transaction, jump to the
      last step.
 
    <li>
@@ -34762,7 +34766,7 @@
     <p>Commit the transaction.
 
    <li>
-    <p>If an error occured in the committing of the transaction, jump to the
+    <p>If an error occurred in the committing of the transaction, jump to the
      last step.
 
    <li>
@@ -34774,8 +34778,8 @@
    <li>
     <p>Call the <i>error callback</i> with a newly constructed <code><a
      href="#sqlerror">SQLError</a></code> object that represents the last
-     error to have occured in this transaction. Rollback the transaction. Any
-     still-pending statements in the transaction are discarded.
+     error to have occurred in this transaction. Rollback the transaction.
+     Any still-pending statements in the transaction are discarded.
   </ol>
 
   <h4 id=disk-space><span class=secno>4.11.3 </span>Disk space</h4>
@@ -34860,7 +34864,7 @@
    <li>
     <p>Site-specific white-listing of access to local storage areas and
      databases: user agents may allow sites to access session storage areas
-     in an unrestricted manner, but require the user to authorise access to
+     in an unrestricted manner, but require the user to authorize access to
      local storage areas and databases.</p>
 
    <li>
@@ -34911,7 +34915,7 @@
 
   <h5 id=dns-spoofing><span class=secno>4.11.5.1. </span>DNS spoofing attacks</h5>
 
-  <p>Because of the potential for DNS spoofing attacks, one cannot guarentee
+  <p>Because of the potential for DNS spoofing attacks, one cannot guarantee
    that a host claiming to be in a certain domain really is from that domain.
    To mitigate this, pages can use SSL. Pages using SSL can be sure that only
    pages using SSL that have certificates identifying them as being from the
@@ -35028,7 +35032,7 @@
    are defined below. The <code title=attr-hyperlink-rel><a
    href="#rel3">rel</a></code> attribute has no default value. If the
    attribute is omitted or if none of the values in the attribute are
-   recognised by the UA, then the document has no particular relationship
+   recognized by the UA, then the document has no particular relationship
    with the destination resource other than there being a hyperlink between
    the two.
 
@@ -35080,7 +35084,7 @@
    that has a <code title=attr-hyperlink-target><a
    href="#target3">target</a></code> attribute, then the browsing context
    that is navigated must be chosen by applying <a href="#the-rules">the
-   rules for chosing a browsing context given a browsing context name</a>,
+   rules for choosing a browsing context given a browsing context name</a>,
    using the value of the <code title=attr-hyperlink-target><a
    href="#target3">target</a></code> attribute as the browsing context name.
    If these rules result in the creation of a new <a
@@ -35101,7 +35105,7 @@
    href="#base">base</a></code> element with a <code
    title=attr-base-target><a href="#target">target</a></code> attribute, then
    the browsing context that is navigated must be chosen by applying <a
-   href="#the-rules">the rules for chosing a browsing context given a
+   href="#the-rules">the rules for choosing a browsing context given a
    browsing context name</a>, using the value of the <code
    title=attr-base-target><a href="#target">target</a></code> attribute of
    the first such <code><a href="#base">base</a></code> element as the
@@ -35206,14 +35210,14 @@
     <li>It allows the paranoid user to disable the notifications without
      losing the underlying link functionality.
 
-    <li>It allows the UA to optimise the use of available network bandwidth
+    <li>It allows the UA to optimize the use of available network bandwidth
      so that the target page loads faster.
    </ul>
 
    <p>Thus, while it is possible to track users without this feature, authors
     are encouraged to use the <code title=attr-hyperlink-ping><a
     href="#ping">ping</a></code> attribute so that the user agent can improve
-    <!-- XXX optimise? --> the user experience.</p>
+    <!-- XXX optimize? --> the user experience.</p>
    <!--
    XXX need a better way to end that sentence. It's what I mean, but
    it sounds kooky. -->
@@ -35221,7 +35225,7 @@
 
   <h4 id=linkTypes><span class=secno>4.12.3 </span>Link types</h4>
 
-  <p>The following table summarises the link types that are defined by this
+  <p>The following table summarizes the link types that are defined by this
    specification. This table is non-normative; the actual definitions for the
    link types are given in the next few sections.
 
@@ -35438,7 +35442,7 @@
 
      <td><em>not allowed</em>
 
-     <td>Specifies that the target resource should be pre-emptively cached.
+     <td>Specifies that the target resource should be preemptively cached.
 
     <tr>
      <td><code title=rel-prev><a href="#prev">prev</a></code></td>
@@ -36132,7 +36136,7 @@
    repeated within a <code title=attr-hyperlink-rel><a
    href="#rel3">rel</a></code> attribute to indicate the hierarchical
    distance from the current document to the referenced document. Each
-   occurance of the keyword represents one further level. If the <code
+   occurrence of the keyword represents one further level. If the <code
    title=rel-index><a href="#index0">index</a></code> keyword is also
    present, then the number of <code title=rel-up><a href="#up">up</a></code>
    keywords is the depth of the current page relative to the top of the
@@ -36158,9 +36162,9 @@
    must be taken as giving the depth of the document.
 
   <div class=example>
-   <p>This can be used to mark up a navigation style sometimes known as
-    breadcrumbs. In the following example, the current page can be reached
-    via two paths.</p>
+   <p>This can be used to mark up a navigation style sometimes known as bread
+    crumbs. In the following example, the current page can be reached via two
+    paths.</p>
 
    <pre><nav>
  <p>
@@ -36697,10 +36701,10 @@
    element is not, or if an element is <a href="#editable0">editable</a> and
    it has no parent element, then the element is an <dfn id=editing1>editing
    host</dfn>. Editable elements can be nested. User agents must make editing
-   hosts focusable (which typicially means they enter the <span
-   title=tabindex>tab order</span>). An editing host can contain non-editable
-   sections, these are handled as described below. An editing host can
-   contain non-editable sections that contain further editing hosts.
+   hosts focusable (which typically means they enter the <a href="#tabindex"
+   title=attr-tabindex>tab order</a>). An editing host can contain
+   non-editable sections, these are handled as described below. An editing
+   host can contain non-editable sections that contain further editing hosts.
 
   <p>When an editing host has focus, it must have a <dfn id=caret>caret
    position</dfn> that specifies where the current editing position is. It
@@ -37046,7 +37050,7 @@
    conceptually contain various kinds of data.
 
   <p>When a <code><a href="#datatransfer0">DataTransfer</a></code> object is
-   created, it must be initialised as follows:
+   created, it must be initialized as follows:
 
   <ul>
    <li>The <code><a href="#datatransfer0">DataTransfer</a></code> object must
@@ -37215,7 +37219,7 @@
 
      <td>Empty
 
-     <td><a href="#effectAllowed-initialisation">Same as last event</a>
+     <td><a href="#effectAllowed-initialization">Same as last event</a>
 
      <td><code title="">none</code>
 
@@ -37233,9 +37237,9 @@
 
      <td>Empty
 
-     <td><a href="#effectAllowed-initialisation">Same as last event</a>
+     <td><a href="#effectAllowed-initialization">Same as last event</a>
 
-     <td><a href="#dropEffect-initialisation">Based on
+     <td><a href="#dropEffect-initialization">Based on
       <code>effectAllowed</code> value</a>
 
      <td>Reject <a href="#immediate">immediate user selection</a> as
@@ -37254,7 +37258,7 @@
 
      <td>Empty
 
-     <td><a href="#effectAllowed-initialisation">Same as last event</a>
+     <td><a href="#effectAllowed-initialization">Same as last event</a>
 
      <td><code title="">none</code>
 
@@ -37271,9 +37275,9 @@
 
      <td>Empty
 
-     <td><a href="#effectAllowed-initialisation">Same as last event</a>
+     <td><a href="#effectAllowed-initialization">Same as last event</a>
 
-     <td><a href="#dropEffect-initialisation">Based on
+     <td><a href="#dropEffect-initialization">Based on
       <code>effectAllowed</code> value</a>
 
      <td>Reset the <a href="#current3">current drag operation</a> to "none"
@@ -37290,7 +37294,7 @@
      <td><code>getData()</code> returns data set in <code
       title=dom-dragstart>dragstart</code> event
 
-     <td><a href="#effectAllowed-initialisation">Same as last event</a>
+     <td><a href="#effectAllowed-initialization">Same as last event</a>
 
      <td><a href="#current3">Current drag operation</a>
 
@@ -37307,7 +37311,7 @@
 
      <td>Empty
 
-     <td><a href="#effectAllowed-initialisation">Same as last event</a>
+     <td><a href="#effectAllowed-initialization">Same as last event</a>
 
      <td><a href="#current3">Current drag operation</a>
 
@@ -37321,7 +37325,7 @@
    title=event-drop><a href="#drop">drop</a></code> events, for which the
    contents are set as described in the processing model, below.
 
-  <p id=effectAllowed-initialisation>The <code
+  <p id=effectAllowed-initialization>The <code
    title=dom-DataTransfer-effectAllowed><a
    href="#effectallowed">effectAllowed</a></code> attribute must be set to
    "<code title="">uninitialized</code>" for <code title=event-dragstart><a
@@ -37330,7 +37334,7 @@
    events (only counting events fired by the user agent for the purposes of
    the drag-and-drop model described below).
 
-  <p id=dropEffect-initialisation>The <code
+  <p id=dropEffect-initialization>The <code
    title=dom-DataTransfer-dropEffect><a
    href="#dropeffect">dropEffect</a></code> attribute must be set to "<code
    title="">none</code>" for <code title=event-dragstart><a
@@ -37944,7 +37948,7 @@
    the user had invoked a drag on the current selection. If the drag-and-drop
    operation initiates, then the user agent must act as if the user had
    indicated (as the <a href="#immediate">immediate user selection</a>) a
-   hypothetical application representing the clipbroad. Then, the user agent
+   hypothetical application representing the clipboard. Then, the user agent
    must act as if the user had ended the drag-and-drop operation without
    canceling it. If the drag-and-drop operation didn't get canceled, the user
    agent should then follow the relevant platform-specific conventions for
@@ -38315,7 +38319,7 @@
    that appears to have separate <a href="#undo-transaction" title="undo
    transaction history">undo transaction histories</a> for each form control;
    similarly, it is possible to design systems where the user has access to
-   more undo information than is present in the offical (as described above)
+   more undo information than is present in the official (as described above)
    <a href="#undo-transaction">undo transaction history</a> (such as
    providing a tree-based approach to document state). Such UI models should
    be based upon the single <a href="#undo-transaction">undo transaction
@@ -38397,7 +38401,7 @@
    object.
 
   <pre
-   class=idl>[<a href="#stringinfy" title=dom-selection-toString>Stringifies</a>] interface <dfn id=selection1>Selection</dfn> {
+   class=idl>[<a href="#stringify0" title=dom-selection-toString>Stringifies</a>] interface <dfn id=selection1>Selection</dfn> {
   readonly attribute Node <a href="#anchornode" title=dom-selection-anchorNode>anchorNode</a>;
   readonly attribute long <a href="#anchoroffset" title=dom-selection-anchorOffset>anchorOffset</a>;
   readonly attribute Node <a href="#focusnode" title=dom-selection-focusNode>focusNode</a>;
@@ -38540,7 +38544,7 @@
    (so the newly added range is the new last range). Duplicates are not
    prevented; a range may be added more than once in which case it appears in
    the list more than once, which (for example) will cause <a
-   href="#stringinfy" title=dom-selection-toString>stringification</a> to
+   href="#stringify0" title=dom-selection-toString>stringification</a> to
    return the range's text twice.</p>
   <!-- XXX how does this interact with
   deleteFromDocument() which acts on all ranges? -->
@@ -38560,8 +38564,8 @@
    (and until a new range is added to the list, either through this interface
    or via user interaction).
 
-  <p>Objects implementing this interface must <dfn id=stringinfy
-   title=dom-selection-toString>stringinfy</dfn> to a concatenation of the
+  <p>Objects implementing this interface must <dfn id=stringify0
+   title=dom-selection-toString>stringify</dfn> to a concatenation of the
    results of invoking the <code title="">toString()</code> method of the
    <code>Range</code> object on each of the ranges of the selection, in the
    order they appear in the list (first to last).
@@ -40019,7 +40023,7 @@
 
   <p>The user agent must then begin trying to establish a connection with the
    target host and specified port. (This typically would begin in the
-   backgound, while the script continues to execute.)
+   background, while the script continues to execute.)
 
   <p>If the <var title="">secure</var> boolean argument is set to true, then
    the user agent must establish a secure connection with the target host and
@@ -40633,8 +40637,8 @@
      title=dom-window-postMessage><a
      href="#postmessage">postMessage()</a></code> method, the <code
      title=dom-MessageEvent-origin><a href="#origin1">origin</a></code>
-     attribute must be set to the <a href="#serialisation0"
-     title="serialisation of an origin">serialisation</a> of the <a
+     attribute must be set to the <a href="#serialization0"
+     title="serialization of an origin">serialization</a> of the <a
      href="#origin0">origin</a> of the script that invoked the method, the
      <code title=dom-MessageEvent-lastEventId><a
      href="#lasteventid">lastEventId</a></code> attribute must be set to the
@@ -40752,7 +40756,7 @@
    few sections.
 
   <p>In addition, there are some restrictions on how <span>character encoding
-   declarations</span> are to be serialised, as discussed in the section on
+   declarations</span> are to be serialized, as discussed in the section on
    that topic.
 
   <div class=note>
@@ -41347,8 +41351,8 @@
   <h5 id=cdata-rcdata-restrictions><span class=secno>8.1.2.6.
    </span>Restrictions on the contents of CDATA and RCDATA elements</h5>
 
-  <p>The text in CDATA and RCDATA elements must not contain any occurences of
-   the string "<code title=""></</code>" (U+003C LESS-THAN SIGN, U+002F
+  <p>The text in CDATA and RCDATA elements must not contain any occurrences
+   of the string "<code title=""></</code>" (U+003C LESS-THAN SIGN, U+002F
    SOLIDUS) followed by characters that case-insensitively<!--ASCII--> match
    the tag name of the element followed by one of U+0009 CHARACTER
    TABULATION, U+000A LINE FEED (LF), U+000B LINE TABULATION, U+000C FORM
@@ -41518,7 +41522,7 @@
     of HTML thus returns to a non-SGML basis.</p>
 
    <p>Authors interested in using SGML tools in their authoring pipeline are
-    encouraged to use XML tools and the XML serialisation of HTML5.</p>
+    encouraged to use XML tools and the XML serialization of HTML5.</p>
   </div>
 
   <p>This specification defines the parsing rules for HTML documents, whether
@@ -42184,7 +42188,7 @@
    href="#document.write...">document.write()</a></code> is actually
    inserted. The insertion point is relative to the position of the character
    immediately after it, it is not an absolute offset into the input stream.
-   Initially, the insertion point is uninitialised.
+   Initially, the insertion point is uninitialized.
 
   <p>The "EOF" character in the tables below is a conceptual character
    representing the end of the <a href="#input0">input stream</a>. If the
@@ -42430,7 +42434,7 @@
    stack.
 
   <p>In the <a href="#fragment">fragment case</a>, the <a href="#stack">stack
-   of open elements</a> is initialised to contain an <code><a
+   of open elements</a> is initialized to contain an <code><a
    href="#html">html</a></code> element that is created as part of <a
    href="#html-fragment0" title="html fragment parsing algorithm">that
    algorithm</a>. (The <a href="#fragment">fragment case</a> skips the "<a
@@ -44581,8 +44585,8 @@
 
   <p class=note>The algorithm described below places no limit on the depth of
    the DOM tree generated, or on the length of tag names, attribute names,
-   attribute values, text nodes, etc. While implementators are encouraged to
-   avoid arbitrary limits, it is recognised that <a
+   attribute values, text nodes, etc. While implementors are encouraged to
+   avoid arbitrary limits, it is recognized that <a
    href="#hardwareLimitations">practical concerns</a> will likely force user
    agents to impose nesting depths.
 
@@ -44619,7 +44623,7 @@
   <p>The steps below may also require that the UA insert an HTML element in a
    particular place, in which case the UA must follow the same steps except
    that it must insert or append the new node in the location specified
-   insead of appending it to the <a href="#current5">current node</a>. (This
+   instead of appending it to the <a href="#current5">current node</a>. (This
    happens in particular during the parsing of tables with invalid content.)
 
   <p>When the steps below require the UA to <dfn id=insert1>insert a foreign
@@ -44928,7 +44932,7 @@
      identifier is not missing, then there is a <a href="#parse1">parse
      error</a>. Conformance checkers may, instead of reporting this error,
      switch to a conformance checking mode for another language (e.g. based
-     on the DOCTYPE token a conformance checker could recognise that the
+     on the DOCTYPE token a conformance checker could recognize that the
      document is an HTML4-era document, and defer to an HTML4 conformance
      checker.)</p>
 
@@ -45540,7 +45544,7 @@
       href="#document.write...">document.write()</a></code>:
 
      <dd>
-      <p>Abort the processing of any nested invokations of the tokeniser,
+      <p>Abort the processing of any nested invocations of the tokeniser,
        yielding control back to the caller. (Tokenisation will resume when
        the caller returns to the "outer" tree construction stage.)
 
@@ -48223,16 +48227,16 @@
   <p>The <dfn id=xmlns>XMLNS namespace</dfn> is:
    <code>http://www.w3.org/2000/xmlns/</code>
 
-  <h3 id=serialising><span class=secno>8.4 </span>Serialising HTML fragments</h3>
+  <h3 id=serializing><span class=secno>8.4 </span>Serializing HTML fragments</h3>
 
   <p>The following steps form the <dfn id=html-fragment>HTML fragment
-   serialisation algorithm</dfn>. The algorithm takes as input a DOM
+   serialization algorithm</dfn>. The algorithm takes as input a DOM
    <code>Element</code> or <code>Document</code>, referred to as <var
    title="">the node</var>, and either returns a string or raises an
    exception.
 
-  <p class=note>This algorithm serialises the <em>children</em> of the node
-   being serialised, not the node itself.
+  <p class=note>This algorithm serializes the <em>children</em> of the node
+   being serialized, not the node itself.
 
   <ol>
    <li>
@@ -48278,7 +48282,7 @@
         <p>While the exact order of attributes is UA-defined, and may depend
          on factors such as the order that the attributes were given in the
          original markup, the sort order must be stable, such that
-         consecutive invocations of this algorithm serialise an element's
+         consecutive invocations of this algorithm serialize an element's
          attributes in the same order.</p>
 
         <p>Append a U+003E GREATER-THAN SIGN (<code title="">></code>)
@@ -48299,7 +48303,7 @@
         <!-- also, i guess: image, isindex,
         and keygen, but we don't list those because we don't consider
         those "elements", more "macros", and thus we should never
-        serialise them -->
+        serialize them -->
         <!-- XXX when we get around to it, add
         event-source -->
         <p>If <var title="">current node</var> is a <code><a
@@ -48307,7 +48311,7 @@
          a U+000A LINE FEED (LF) character.</p>
 
         <p>Append the value of running the <a href="#html-fragment">HTML
-         fragment serialisation algorithm</a> on the <var title="">current
+         fragment serialization algorithm</a> on the <var title="">current
          node</var> element (thus recursing into this algorithm for that
          element), followed by a U+003C LESS-THAN SIGN (<code
          title=""><</code>) character, a U+002F SOLIDUS (<code
@@ -48404,11 +48408,11 @@
   <p class=note>It is possible that the output of this algorithm, if parsed
    with an <a href="#html-0">HTML parser</a>, will not return the original
    tree structure. For instance, if a <code>textarea</code> element to which
-   a <code title="">Comment</code> node has been appended is serialised and
+   a <code title="">Comment</code> node has been appended is serialized and
    the output is then reparsed, the comment will end up being displayed in
    the text field. Similarly, if, as a result of DOM manipulation, an element
    contains a comment that contains the literal string "<code
-   title="">--></code>", then when the result of serialising the element
+   title="">--></code>", then when the result of serializing the element
    is parsed, the comment will be truncated at that point and the rest of the
    comment will be interpreted as markup. More examples would be making a
    <code><a href="#script1">script</a></code> element contain a text node
@@ -50809,7 +50813,7 @@
    interface. Only the default view implements the <code><a
    href="#window">Window</a></code> interface. The other views can be reached
    using the <code><a href="#view">view</a></code> attribute of the
-   <code>UIEvent</code> inteface, during event propagation. There is no way
+   <code>UIEvent</code> interface, during event propagation. There is no way
    currently to enumerate all the views.</p>
   <!-- XXX examples! -->
 
@@ -50950,11 +50954,11 @@
    because the features exist in other languages that can be integrated into
    this one. This section covers some of the more common requests.
 
-  <h3 id=localisation><span class=secno>10.1 </span>Localisation</h3>
+  <h3 id=localization><span class=secno>10.1 </span>Localization</h3>
 
-  <p>If you wish to create localised versions of an HTML application, the
+  <p>If you wish to create localized versions of an HTML application, the
    best solution is to preprocess the files on the server, and then use HTTP
-   content negotation to serve the appropriate language.</p>
+   content negotiation to serve the appropriate language.</p>
   <!-- <p>XXX example here</p> -->
   <!--XXXSVG (remove next section)-->
 

Modified: source
===================================================================
--- source	2008-05-22 09:33:20 UTC (rev 1663)
+++ source	2008-05-22 10:44:38 UTC (rev 1664)
@@ -51,7 +51,7 @@
   to dynamic applications.</p>
 
   <p>The scope of this specification does not include providing
-  mechanisms for media-specific customisation of presentation
+  mechanisms for media-specific customization of presentation
   (although default rendering rules for Web browsers are included at
   the end of this specification, and several mechanisms for hooking
   into CSS are provided as part of the language).</p>
@@ -186,7 +186,7 @@
    <dt><a href="#syntax">The Language Syntax</a></dt>
 
    <dd>All of these features would be for naught if they couldn't be
-   represented in a serialised form and sent to other people, and so
+   represented in a serialized form and sent to other people, and so
    this section defines the syntax of HTML, along with rules for how
    to parse HTML.</dd>
 
@@ -419,7 +419,7 @@
     <p>When an authoring tool is used to edit a non-conforming
     document, it may preserve the conformance errors in sections of
     the document that were not edited during the editing session
-    (i.e. an editing tool is allowed to round-trip errorneous
+    (i.e. an editing tool is allowed to round-trip erroneous
     content). However, an authoring tool must not claim that the
     output is conformant if errors have been so preserved.</p>
 
@@ -515,7 +515,7 @@
   <h4>Common conformance requirements for APIs exposed to
   JavaScript</h4>
 
-  <p class="big-issue">A lot of arrays/lists/<span>collection</span>s
+  <p class="big-issue">A lot of arrays/lists/<span title="collections">collection</span>s
   in this spec assume zero-based indexes but use the term "<var
   title="">index</var>th" liberally. We should define those to be
   zero-based and be clearer about this.</p>
@@ -560,7 +560,7 @@
 
     <p>Implementations that support XHTML5 must support some version
     of XML, as well as its corresponding namespaces specification,
-    because XHTML5 uses an XML serialisation with namespaces. <a
+    because XHTML5 uses an XML serialization with namespaces. <a
     href="#refsXML">[XML]</a> <a
     href="#refsXMLNAMES">[XMLNAMES]</a></p>
 
@@ -829,7 +829,7 @@
   interacting with plugins, as it is expected to be user-agent- and
   platform-specific. Some UAs might opt to support a plugin mechanism
   such as the Netscape Plugin API; others might use remote content
-  convertors or have built-in support for certain types. <a
+  converters or have built-in support for certain types. <a
   href="#refsNPAPI">[NPAPI]</a></p>
 
   <p class="warning">Browsers should take extreme care when
@@ -1127,7 +1127,7 @@
   and time must be derived from relevant features of the networking
   protocols used, e.g. from the value of the HTTP <code
   title="">Last-Modified</code> header of the document, or from
-  metadata in the filesystem for local files. If the last modification
+  metadata in the file system for local files. If the last modification
   date and time are not known, the attribute must return the string
   <code title="">01/01/1970 00:00:00</code>.</p>
 
@@ -1170,7 +1170,7 @@
   <p>Documents have an associated <dfn title="document's character
   encoding">character encoding</dfn>. When a <code>Document</code>
   object is created, the <span>document's character encoding</span>
-  must be initialised to UTF-16. Various algorithms during page
+  must be initialized to UTF-16. Various algorithms during page
   loading affect this value, as does the <code
   title="dom-document-charset">charset</code> setter.  <a
   href="#refsIANACHARSET">[IANACHARSET]</a> <!-- XXX
@@ -1413,12 +1413,12 @@
   (<code>float</code>) and the content attribute is defined to contain
   a time offset, then, on getting, the content attribute must be
   parsed according to <span title="rules for parsing time offsets">the
-  rules for parsing time ofsets</span>, and if that is successful, the
+  rules for parsing time offsets</span>, and if that is successful, the
   resulting value, in seconds, must be returned. If that fails, or if
   the attribute is absent, the default value must be returned, or the
   not-a-number value (NaN) if there is no default value. On setting,
   the given value, interpreted as a time offset in seconds, must be
-  converted to a string using the <span>time offset serialisation
+  converted to a string using the <span>time offset serialization
   rules</span>, and that string must be used as the new content
   attribute value.</p>
 
@@ -1502,12 +1502,13 @@
   <code>img</code> elements, and rooted at the root of the
   document.</p>
 
-  <p>The <span>collection</span> then <dfn title="representated by the
-  collection">represents</dfn> a <span>live</span> view of the subtree
-  rooted at the collection's root, containing only nodes that match
-  the given filter. The view is linear. In the absence of specific
-  requirements to the contrary, the nodes within the collection must
-  be sorted in <span>tree order</span>.</p>
+  <p>The <span title="collections">collection</span> then <dfn
+  title="represented by the collection">represents</dfn> a
+  <span>live</span> view of the subtree rooted at the collection's
+  root, containing only nodes that match the given filter. The view is
+  linear. In the absence of specific requirements to the contrary, the
+  nodes within the collection must be sorted in <span>tree
+  order</span>.</p>
 
   <p class="note">The <code title="dom-table-rows">rows</code> list is
   not in tree order.</p>
@@ -1519,7 +1520,7 @@
   <h5>HTMLCollection</h5>
 
   <p>The <code>HTMLCollection</code> interface represents a generic
-  <span>collection</span> of elements.</p>
+  <span title="collections">collection</span> of elements.</p>
 
   <pre class="idl">interface <dfn>HTMLCollection</dfn> {
   readonly attribute unsigned long <span title="dom-HTMLCollection-length">length</span>;
@@ -1567,7 +1568,7 @@
   <h5>HTMLFormControlsCollection</h5>
 
   <p>The <code>HTMLFormControlsCollection</code> interface represents
-  a <span>collection</span> of form controls.</p>
+  a <span title="collections">collection</span> of form controls.</p>
 
   <pre class="idl">interface <dfn>HTMLFormControlsCollection</dfn> {
   readonly attribute unsigned long <span title="dom-HTMLFormControlsCollection-length">length</span>;
@@ -1867,7 +1868,7 @@
   <pre class="idl">interface <dfn>DOMStringMap</dfn> {
   [NameGetter] DOMString <span title="dom-stringmap-XXX1">XXX1</span>(in DOMString name); <!-- XXX DOMB -->
   [NameSetter] void <span title="dom-stringmap-XXX2">XXX2</span>(in DOMString name, in DOMString value); <!-- XXX DOMB -->
-  [XXX] bool <span title="dom-stringmap-XXX3">XXX3</span>(in DOMString name); <!-- XXX DOMB -->
+  [XXX] boolean <span title="dom-stringmap-XXX3">XXX3</span>(in DOMString name); <!-- XXX DOMB -->
 };</pre>
 
   <p>The <dfn title="dom-stringmap-XXX1"><code>XXX1(<var
@@ -1921,7 +1922,7 @@
   always supersets of the interfaces defined in DOM2 HTML; some
   features that were formerly deprecated, poorly supported, rarely
   used or considered unnecessary have been removed. Therefore it is
-  not guarenteed that an implementation that supports "<code
+  not guaranteed that an implementation that supports "<code
   title="">HTML</code>" "<code>5.0</code>" also supports "<code
   title="">HTML</code>" "<code>2.0</code>".</p>
 
@@ -2420,7 +2421,7 @@
   <p>In HTML, the <dfn
   title="dom-innerHTML-HTML"><code>innerHTML</code></dfn> DOM
   attribute of all <code>HTMLElement</code> and
-  <code>HTMLDocument</code> nodes returns a serialisation of the
+  <code>HTMLDocument</code> nodes returns a serialization of the
   node's children using the <span>HTML syntax</span><!-- XXX xref
   -->. On setting, it replaces the node's children with new nodes that
   result from parsing the given value. The formal definitions
@@ -2428,7 +2429,7 @@
 
   <p>On getting, the <code title="dom-innerHTML-HTML">innerHTML</code>
   DOM attribute must return the result of running the <span>HTML
-  fragment serialisation algorithm</span> on the node.</p>
+  fragment serialization algorithm</span> on the node.</p>
 
   <p>On setting, if the node is a document, the <code
   title="dom-innerHTML-HTML">innerHTML</code> DOM attribute must run
@@ -2462,7 +2463,7 @@
 
    </li>
 
-<!-- redundant, the document is forcably already so labeled if we get here
+<!-- redundant, the document is forcibly already so labeled if we get here
    <li>
 
     <p>Mark the <code>Document</code> object as being an <span
@@ -2591,17 +2592,17 @@
   in the form of a <a
   href="http://www.w3.org/TR/xml/#sec-well-formed">document
   entity</a>. The string returned must be XML namespace-well-formed
-  and must be an isomorphic serialisation of all of that node's child
+  and must be an isomorphic serialization of all of that node's child
   nodes, in document order. User agents may adjust prefixes and
-  namespace declarations in the serialisation (and indeed might be
+  namespace declarations in the serialization (and indeed might be
   forced to do so in some cases to obtain namespace-well-formed
-  XML). If any of the elements in the serialisation are in the null
+  XML). If any of the elements in the serialization are in the null
   namespace, the default namespace in scope for those elements must be
   explicitly declared as the empty string. <a
   href="#refsXML">[XML]</a> <a href="#refsXMLNS">[XMLNS]</a></p>
 
   <p>If any of the following cases are found in the DOM being
-  serialised, the user agent must raise an
+  serialized, the user agent must raise an
   <code>INVALID_STATE_ERR</code> exception:</p>
 
   <ul>
@@ -2642,7 +2643,7 @@
   </ul>
 
   <p class="note">These are the only ways to make a DOM
-  unserialisable. The DOM enforces all the other XML constraints; for
+  unserializable. The DOM enforces all the other XML constraints; for
   example, trying to set an attribute with a name that contains an
   equals sign (=) will raised an <code>INVALID_CHARACTER_ERR</code>
   exception.</p>
@@ -2757,7 +2758,7 @@
   <p>For <span>HTML documents</span>, and for <span>HTML
   elements</span> in <span>HTML documents</span>, certain APIs defined
   in DOM3 Core become case-insensitive or case-changing, as sometimes
-  defined in DOM3 Core, and as summarised or required below. <a
+  defined in DOM3 Core, and as summarized or required below. <a
   href="#refsDOM3CORE">[DOM3CORE]</a>.</p>
 
   <p>This does not apply to <span>XML documents</span> or to elements
@@ -3384,7 +3385,7 @@
    <li>Parse <var title="">string</var> according to the <span>rules for
    parsing floating point number values</span>, to obtain
    <var title="">number</var>. This step cannot fail (<var title="">string</var> is
-   guarenteed to be a <span>valid floating point number</span>).</li>
+   guaranteed to be a <span>valid floating point number</span>).</li>
 
    <li>Return <var title="">number</var>.</li>
 
@@ -4399,7 +4400,7 @@
   <h4>Time offsets</h4>
 
   <p class="big-issue"><dfn>valid time offset</dfn>, <dfn>rules for
-  parsing time offsets</dfn>, <dfn>time offset serialisation
+  parsing time offsets</dfn>, <dfn>time offset serialization
   rules</dfn>; in the format "5d4h3m2s1ms" or "3m 9.2s" or "00:00:00.00"
   or similar.</p>
 
@@ -4900,7 +4901,7 @@
   <h5>Flow content</h5>
 
   <p>Most elements that are used in the body of documents and
-  applications are categorised as <dfn>flow content</dfn>.</p>
+  applications are categorized as <dfn>flow content</dfn>.</p>
 
   <p>As a general rule, elements whose content model allows any
   <span>flow content</span> should have either at least one
@@ -4957,8 +4958,8 @@
   counted as contributing to the ancestors of the <code>del</code>
   element.</p>
 
-  <p class="note">Most elements that are categorised as phrasing
-  content can only contain elements that are themselves categorised as
+  <p class="note">Most elements that are categorized as phrasing
+  content can only contain elements that are themselves categorized as
   phrasing content, not any flow content.</p>
 
   <p>Text nodes that are not <span>inter-element whitespace</span> are
@@ -5338,7 +5339,7 @@
 
   <p>User agents may use the element's language to determine proper
   processing or rendering (e.g. in the selection of appropriate
-  fonts or pronounciations, or for dictionary selection). <!--User
+  fonts or pronunciations, or for dictionary selection). <!--User
   agents must not use the element's language to determine text
   directionality. (commented out because text directionality is a
   rendering-level concern.)--></p>
@@ -5501,7 +5502,7 @@
   present. Mutating the <code>CSSStyleDeclaration</code> object must
   create a <code title="attr-font-style">style</code> attribute on the
   element (if there isn't one already) and then change its value to be
-  a value representing the serialised form of the
+  a value representing the serialized form of the
   <code>CSSStyleDeclaration</code> object. <a
   href="#refsCSSOM">[CSSOM]</a>
 
@@ -5846,26 +5847,27 @@
   key events.</p>
 
   <p>The <dfn><code>moveFocusForward</code></dfn> method uses the
-  <code>'nav-index'</code> property and the <code>tabindex</code>
-  attribute to find the next focusable element and focuses it.</p>
+  <code>'nav-index'</code> property and the <code
+  title="attr-tabindex">tabindex</code> attribute to find the next
+  focusable element and focuses it.</p>
 
   <p>The <dfn><code>moveFocusBackward</code></dfn> method uses the
-  <code>'nav-index'</code> property and the <code>tabindex</code>
-  attribute to find the previous focusable element and focuses
-  it.</p>
+  <code>'nav-index'</code> property and the <code
+  title="attr-tabindex>tabindex</code> attribute to find the previous
+  focusable element and focuses it.</p>
 
   <p>The <dfn><code>moveFocusUp</code></dfn> method uses the
-  <code>'nav-up'</code> property and the <code>tabindex</code>
-  attribute to find an appropriate focusable element and focuses
-  it.</p>
+  <code>'nav-up'</code> property and the <code
+  title="attr-tabindex>tabindex</code> attribute to find an
+  appropriate focusable element and focuses it.</p>
 
   <p>In a similar manner, the <dfn><code>moveFocusRight</code></dfn>,
   <dfn><code>moveFocusDown</code></dfn>, and
   <dfn><code>moveFocusLeft</code></dfn> methods use the
   <code>'nav-right'</code>, <code>'nav-down'</code>, and
-  <code>'nav-left'</code> properties (respectively), and the
-  <code>tabindex</code> attribute, to find an appropriate focusable
-  element and focus it.</p>
+  <code>'nav-left'</code> properties (respectively), and the <code
+  title="attr-tabindex>tabindex</code> attribute, to find an
+  appropriate focusable element and focus it.</p>
 
   <p>The <code>'nav-index'</code>, <code>'nav-up'</code>,
   <code>'nav-right'</code>, <code>'nav-down'</code>, and
@@ -6374,9 +6376,9 @@
    <dt>Categories</dt>
    <dd><span>Metadata content</span>.</dd>
    <dt>Contexts in which this element may be used:</dt>
-   <dd>If the <code title="attr-meta-charset">charset</code> attribute is present, or if the element is in the <span title="attr-meta-http-equiv-content-type">Encoding declaraton state</span>: as the first element in a <code>head</code> element.</dd>
-   <dd>If the <code title="attr-meta-http-equiv">http-equiv</code> attribute is present, and the element is not in the <span title="attr-meta-http-equiv-content-type">Encoding declaraton state</span>: in a <code>head</code> element.</dd>
-   <dd>If the <code title="attr-meta-http-equiv">http-equiv</code> attribute is present, and the element is not in the <span title="attr-meta-http-equiv-content-type">Encoding declaraton state</span>: in a <code>noscript</code> element that is a child of a <code>head</code> element.</dd>
+   <dd>If the <code title="attr-meta-charset">charset</code> attribute is present, or if the element is in the <span title="attr-meta-http-equiv-content-type">Encoding declaration state</span>: as the first element in a <code>head</code> element.</dd>
+   <dd>If the <code title="attr-meta-http-equiv">http-equiv</code> attribute is present, and the element is not in the <span title="attr-meta-http-equiv-content-type">Encoding declaration state</span>: in a <code>head</code> element.</dd>
+   <dd>If the <code title="attr-meta-http-equiv">http-equiv</code> attribute is present, and the element is not in the <span title="attr-meta-http-equiv-content-type">Encoding declaration state</span>: in a <code>noscript</code> element that is a child of a <code>head</code> element.</dd>
    <dd>If the <code title="attr-meta-name">name</code> attribute is present: where <span>metadata content</span> is expected.</dd>
    <dt>Content model:</dt>
    <dd>Empty.</dd>
@@ -6405,7 +6407,7 @@
   attribute, pragma directives with the <code
   title="attr-meta-http-equiv">http-equiv</code> attribute, and the
   file's <span>character encoding declaration</span> when an HTML
-  document is serialised to string form (e.g. for transmission over
+  document is serialized to string form (e.g. for transmission over
   the network or for disk storage) with the <code
   title="attr-meta-charset">charset</code> attribute.</p>
 
@@ -6710,7 +6712,7 @@
     <span>character encoding declaration</span>.</p>
 
     <p>For <code>meta</code> elements in the <span
-    title="attr-meta-http-equiv-content-type">Encoding declaraton
+    title="attr-meta-http-equiv-content-type">Encoding declaration
     state</span>, the <code title="attr-meta-content">content</code>
     attribute must have a value that is a case-insensitive<!-- ASCII
     XXX--> match of a string that consists of the literal string
@@ -6722,14 +6724,14 @@
 
     <p>If the document contains a <code>meta</code> element in the
     <span title="attr-meta-http-equiv-content-type">Encoding
-    declaraton state</span> then that element must be the first
+    declaration state</span> then that element must be the first
     element in the document's <code>head</code> element, and the
     document must not contain a <code>meta</code> element with the
     <code title="attr-meta-charset">charset</code> attribute
     present.</p>
 
     <p>The <span title="attr-meta-http-equiv-content-type">Encoding
-    declaraton state</span> may be used in <span title="HTML5">HTML
+    declaration state</span> may be used in <span title="HTML5">HTML
     documents</span> only, elements in that state must not be used in
     <span title="XHTML">XML documents</span>.</p>
 
@@ -6922,14 +6924,14 @@
   <ul>
 
    <li>The character encoding name given must be the name of the
-   character encoding used to serialise the file.</li>
+   character encoding used to serialize the file.</li>
 
    <li>The value must be a valid character encoding name, and must be
    the preferred name for that encoding. <a
    href="#refsIANACHARSET">[IANACHARSET]</a> <!-- XXX
    http://www.iana.org/assignments/character-sets --></li>
 
-   <li>The encoding name must be serialised without the use of <span
+   <li>The encoding name must be serialized without the use of <span
    title="syntax-charref">character references</span> or character
    escapes of any kind.</li>
 
@@ -6946,7 +6948,7 @@
   the encoding must be specified using a <code>meta</code> element
   with a <code title="attr-meta-charset">charset</code> attribute or a
   <code>meta</code> element in the <span
-  title="attr-meta-http-equiv-content-type">Encoding declaraton
+  title="attr-meta-http-equiv-content-type">Encoding declaration
   state</span>.</p>
 
   <p>Authors should not use JIS_X0212-1990, x-JIS0208, and encodings
@@ -7709,7 +7711,7 @@
   elements, or to use elements of the appropriate <span>rank</span>
   for the section's nesting level.</p>
 
-  <p>Authors are also encouraged to explictly wrap sections in
+  <p>Authors are also encouraged to explicitly wrap sections in
   elements of <span>sectioning content</span>, instead of relying on
   the implicit sections generated by having multiple heading in one
   element of <span>sectioning content</span>.</p>
@@ -7789,7 +7791,7 @@
    associated with a section.)</p></li>
 
    <li><p>Create a stack to hold elements, which is used to handle
-   nesting. Initialise this stack to empty.</p></li>
+   nesting. Initialize this stack to empty.</p></li>
 
    <li>
 
@@ -7834,7 +7836,7 @@
       element.</p>
 
       <p>Let there be a new outline for the new <var title="">current
-      outlinee</var>, initialised with just the new <var
+      outlinee</var>, initialized with just the new <var
       title="">current section</var> as the only section in the
       outline.</p>
 
@@ -8268,7 +8270,7 @@
   rather than by elements.</p>
 
   <p class="note"><strong>In the <span title="">HTML
-  serialisation</span><!-- XXX xref -->, a leading newline character
+  serialization</span><!-- XXX xref -->, a leading newline character
   immediately following the <code>pre</code> element start tag is
   stripped.</strong></p>
 
@@ -8449,7 +8451,7 @@
 
   <p>The <dfn title="dom-quote-cite"><code>cite</code></dfn> DOM
   attribute must <span>reflect</span> the element's <code
-  title="">cite</code> content attribte.
+  title="">cite</code> content attribute.
 
   <p class="note">The best way to represent a conversation is not with
   the <code>cite</code> and <code>blockquote</code> elements, but with
@@ -9343,7 +9345,7 @@
   <p>The <code>em</code> element represents stress emphasis of its
   contents.</p>
 
-  <p>The level of emphasis that a particlar piece of content has is
+  <p>The level of emphasis that a particular piece of content has is
   given by its number of ancestor <code>em</code> elements.</p>
 
   <p>The placement of emphasis changes the meaning of the sentence.
@@ -9358,7 +9360,7 @@
 
    <pre><p>Cats are cute animals.</p></pre>
 
-   <p>By emphasising the first word, the statement implies that the
+   <p>By emphasizing the first word, the statement implies that the
    kind of animal under discussion is in question (maybe someone is
    asserting that dogs are cute):</p>
 
@@ -9377,18 +9379,18 @@
    <pre><p>Cats are <em>cute</em> animals.</p></pre>
 
    <p>Similarly, if someone asserted that cats were vegetables,
-   someone correcting this might emphasise the last word:</p>
+   someone correcting this might emphasize the last word:</p>
 
    <pre><p>Cats are cute <em>animals</em>.</p></pre>
 
-   <p>By emphasising the entire sentence, it becomes clear that the
+   <p>By emphasizing the entire sentence, it becomes clear that the
    speaker is fighting hard to get the point across. This kind of
    emphasis also typically affects the punctuation, hence the
    exclamation mark here.</p>
 
    <pre><p><em>Cats are cute animals!</em></p></pre>
 
-   <p>Anger mixed with emphasising the cuteness could lead to markup
+   <p>Anger mixed with emphasizing the cuteness could lead to markup
    such as:</p>
 
    <pre><p><em>Cats are <em>cute</em> animals!</em></p></pre>
@@ -9461,7 +9463,7 @@
   other disadvantages), or other side comments.</p>
 
   <p class="note">The <code>small</code> element does not
-  "de-emphasise" or lower the importance of text emphasised by the
+  "de-emphasize" or lower the importance of text emphasised by the
   <code>em</code> element or marked as important with the
   <code>strong</code> element.</p>
 
@@ -9629,7 +9631,7 @@
 <p>When a wormhole is created, a vortex normally forms.
 <strong>Warning: The vortex caused by the wormhole opening will
 annihilate anything in its path.</strong> Vortexes can be avoided when
-using sufficently advanced dialing technology.</p>
+using sufficiently advanced dialing technology.</p>
 
 <p><mark>An obstruction in a gate will prevent it from accepting a
 wormhole connection.</mark></p></pre>
@@ -9783,7 +9785,7 @@
 backfill the <abbr>WHATWG</abbr> issue graph.</p></pre>
   </div>
 
-  <p>If an abbreviation is pluralised, the expansion's grammatical
+  <p>If an abbreviation is pluralized, the expansion's grammatical
   number (plural vs singular) must match the grammatical number of the
   contents of the element.</p>
 
@@ -9905,7 +9907,7 @@
 
    <p>In the following snippet:</p>
 
-   <pre><p>Our first date was <time datetime="2006-09-23">a saturday</time>.</p></pre>
+   <pre><p>Our first date was <time datetime="2006-09-23">a Saturday</time>.</p></pre>
 
    <p>...the <code>time</code> element's <code
    title="dom-time-date">date</code> attribute would have the value
@@ -10262,7 +10264,7 @@
 
   <p>There is no explicit way to specify units in the
   <code>meter</code> element, but the units may be specified in the
-  <code title="attr-title">title</code> attribute in freeform text.</p>
+  <code title="attr-title">title</code> attribute in free-form text.</p>
 
   <div class="example">
 
@@ -10542,7 +10544,7 @@
 
   <p>The <code>code</code> element represents a fragment of computer
   code. This could be an XML element name, a filename, a computer
-  program, or any other string that a computer would recognise.</p>
+  program, or any other string that a computer would recognize.</p>
 
   <p>Although there is no formal way to indicate the language of
   computer code being marked up, authors who wish to mark
@@ -10585,7 +10587,7 @@
 
   </div>
 
-  <p class="note">See the <code>pre</code> element for more detais.</p>
+  <p class="note">See the <code>pre</code> element for more details.</p>
 
 
   <h4>The <dfn><code>var</code></dfn> element</h4>
@@ -10636,7 +10638,7 @@
   program or computing system.</p>
 
   <p class="note">See the <code>pre</code> and <code>kbd</code>
-  elements for more detais.</p>
+  elements for more details.</p>
 
   <div class="example">
    <p>This example shows the <code>samp</code> element being used
@@ -10864,7 +10866,7 @@
   <p class="note">Style sheets can be used to format <code>i</code>
   elements, just like any other element can be restyled. Thus, it is
   not the case that content in <code>i</code> elements will
-  necessarily be italicised.</p>
+  necessarily be italicized.</p>
 
 
   <h4>The <dfn><code>b</code></dfn> element</h4>
@@ -10988,7 +10990,7 @@
 
   <h4>Usage summary</h4>
 
-  <p class="big-issue">We need to summarise the various elements, in
+  <p class="big-issue">We need to summarize the various elements, in
   particular to distinguish b/i/em/strong/var/q/mark/cite.</p>
 
   <!-- XXX when you do this, also reorder the elements in this section
@@ -11011,7 +11013,7 @@
  <dt>Customer
  <dd>Hello! I wish to register a complaint. Hello. Miss?
  <dt>Shopkeeper
- <dd><span title="Coloquial pronounciation of 'What do you'"
+ <dd><span title="Colloquial pronunciation of 'What do you'"
  >Watcha</span> mean, miss?
  <dt>Customer
  <dd>Uh, I'm sorry, I have a cold. I wish to make a complaint.
@@ -11451,7 +11453,7 @@
 <img src="promblem-packed-action.png" alt="ROUGH COPY! Promblem-Packed Action!">
 
 <p>...was aired. A lawyer, armed with a Bigger Notebook, launched a
-pre-emptive strike using snowballs. A complete copy of the trailer is
+preemptive strike using snowballs. A complete copy of the trailer is
 included with Exhibit B.</p>
 
 <figure>
@@ -11625,7 +11627,7 @@
 
     </div>
 
-    <p>It is important to realise that the alternative text is a
+    <p>It is important to realize that the alternative text is a
     <em>replacement</em> for the image, not a description of the
     image.</p>
 
@@ -11637,7 +11639,7 @@
    <dd>
 
     <p>A document can contain information in iconic form. The icon is
-    intended to help users of visual browsers to recognise features at
+    intended to help users of visual browsers to recognize features at
     a glance.</p>
 
     <p>In some cases, the icon is supplemental to a text label
@@ -11693,7 +11695,7 @@
     </div>
 
     <p>Many pages include logos, insignia, flags, or emblems, which
-    stand for a particular entity such as a company, organisation,
+    stand for a particular entity such as a company, organization,
     project, band, software package, country, or some such.</p>
 
     <p>If the logo is being used to represent the entity, the <code
@@ -11731,7 +11733,7 @@
  <h2>News</h2>
  <p>We have recently been looking at buying the <strong><img src="alpha.gif"
  alt=""> ΑΒΓ company</strong>, a small Greek company
- specialising in our type of product.</p></pre>
+ specializing in our type of product.</p></pre>
 
      <p>In this third snippet, we have a logo being used in an aside,
      as part of the larger article discussing the acquisition:</p>
@@ -11962,7 +11964,7 @@
     <p>When an image is included in a communication (such as an HTML
     e-mail) aimed at someone who is known to be able to view images,
     the <code title="attr-img-alt">alt</code> attribute may be
-    omitted. However, even in such cases it is stongly recommended
+    omitted. However, even in such cases it is strongly recommended
     that alternative text be included (as appropriate according to the
     kind of image involved, as described in the above entries), so
     that the e-mail is still usable should the user use a mail client
@@ -12682,7 +12684,7 @@
   element.</p>
 
   <p class="warning">Plugins are disabled in sandboxed browsing
-  contexts because they might not honour the restrictions imposed by
+  contexts because they might not honor the restrictions imposed by
   the sandbox (e.g. they might allow scripting even when scripting in
   the sandbox is disabled). User agents should convey the danger of
   overriding the sandbox to the user if an option to do so is
@@ -13059,7 +13061,7 @@
 
   </ol>
 
-  <p id="object-plugin">When the algorihm above instantiates a
+  <p id="object-plugin">When the algorithm above instantiates a
   <span>plugin</span>, the user agent should pass the names and values of all the
   <span title="concept-param-parameter">parameters</span> given by
   <code>param</code> elements that are children of the
@@ -13294,7 +13296,7 @@
   changes such that the last frame rendered is no longer the frame
   corresponding to the <span>current playback position</span> in the
   video, the new frame must be rendered. Similarly, any audio
-  associated with the video must, if played, be played synchronised
+  associated with the video must, if played, be played synchronized
   with the <span>current playback position</span>, at the specified
   <span title="dom-media-volume">volume</span> with the specified
   <span title="dom-media-muted">mute state</span>.</p>
@@ -13483,7 +13485,7 @@
   elements</span>.</p>
  
   <p>When an <code>audio</code> element is <span>actively
-  playing</span>, it must have its audio data played synchronised with
+  playing</span>, it must have its audio data played synchronized with
   the <span>current playback position</span>, at the specified <span
   title="dom-media-volume">volume</span> with the specified <span
   title="dom-media-muted">mute state</span>.</p>
@@ -13982,7 +13984,7 @@
 
    <dt><dfn title="dom-media-EMPTY"><code>EMPTY</code></dfn> (numeric value 0)</dt>
 
-   <dd>The element has not yet been initialised. All attributes are in
+   <dd>The element has not yet been initialized. All attributes are in
    their initial states.</dd>
 
    <dt><dfn title="dom-media-LOADING"><code>LOADING</code></dfn> (numeric value 1)</dt>
@@ -14439,7 +14441,7 @@
   otherwise.</p>
 
   <p>The <dfn title="dom-media-buffered"><code>buffered</code></dfn>
-  attribute must return a static <span>normalised
+  attribute must return a static <span>normalized
   <code>TimeRanges</code> object</span> that represents the ranges of
   the <span>media resource</span>, if any, that the user agent has
   downloaded, at the time the attribute is evaluated.</p>
@@ -14450,7 +14452,7 @@
 
   <p>The <dfn
   title="dom-media-bufferedBytes"><code>bufferedBytes</code></dfn>
-  attribute must return a static <span>normalised
+  attribute must return a static <span>normalized
   <code>ByteRanges</code> object</span> that represents the ranges of
   the <span>media resource</span>, if any, that the user agent has
   downloaded, at the time the attribute is evaluated.</p>
@@ -14683,7 +14685,7 @@
    without immediately reverting to the <code
    title="dom-media-DATA_UNAVAILABLE">DATA_UNAVAILABLE</code> state. In video,
    this corresponds to the user agent having data for the current
-   frame and the next frame. In audio, this corresponds ot the user
+   frame and the next frame. In audio, this corresponds to the user
    agent having data beyond the <span>current playback
    position</span>.</dd>
 
@@ -14774,7 +14776,7 @@
   thus without firing the <code
   title="event-canshowcurrentframe">canshowcurrentframe</code> and
   <code title="event-canplay">canplay</code> events. The only state
-  that is guarenteed to be reached is the <code
+  that is guaranteed to be reached is the <code
   title="dom-media-CAN_SHOW_CURRENT_FRAME">CAN_SHOW_CURRENT_FRAME</code>
   state, which is reached as part of the <code
   title="dom-media-load">load()</code> method's processing.</p>
@@ -15086,7 +15088,7 @@
   <span>ended playback</span>, and false otherwise.</p>
 
   <p>The <dfn title="dom-media-played"><code>played</code></dfn>
-  attribute must return a static <span>normalised
+  attribute must return a static <span>normalized
   <code>TimeRanges</code> object</span> that represents the ranges of
   the <span>media resource</span>, if any, that the user agent has so
   far rendered, at the time the attribute is evaluated.</p>
@@ -15181,7 +15183,7 @@
   </ol>
 
   <p>The <dfn title="dom-media-seekable"><code>seekable</code></dfn>
-  attribute must return a static <span>normalised
+  attribute must return a static <span>normalized
   <code>TimeRanges</code> object</span> that represents the ranges of
   the <span>media resource</span>, if any, that the user agent is able
   to seek to, at the time the attribute is evaluated, notwithstanding
@@ -15269,7 +15271,7 @@
   <ol>
 
    <li><p>Let <var title="">current ranges</var> be an ordered list of
-   <span title="cue range">cue ranges</span>, initialised to contain
+   <span title="cue range">cue ranges</span>, initialized to contain
    all the <span title="cue range">cue ranges</span> of the
    <span>media element</span> whose start times are less than or equal
    to the <span>current playback position</span> and whose end times
@@ -15277,7 +15279,7 @@
    order they were added to the element.</p></li>
 
    <li><p>Let <var title="">other ranges</var> be an ordered list of
-   <span title="cue range">cue ranges</span>, initialised to contain
+   <span title="cue range">cue ranges</span>, initialized to contain
    all the <span title="cue range">cue ranges</span> of the
    <span>media element</span> that are not present in <var
    title="">current ranges</var>, in the order they were added to the
@@ -15344,7 +15346,7 @@
   <p>The <dfn
   title="dom-voidCallback-handleEvent"><code>handleEvent</code></dfn>
   method of objects implementing the <code>VoidCallback</code>
-  interface is the entrypoint for the callback represented by the
+  interface is the entry point for the callback represented by the
   object.</p>
 
 
@@ -15446,7 +15448,7 @@
   equal to the number of ranges represented by the object.</p>
 
   <p>When a <code>TimeRanges</code> object is said to be a
-  <dfn>normalised <code>TimeRanges</code> object</dfn>, the ranges it
+  <dfn>normalized <code>TimeRanges</code> object</dfn>, the ranges it
   represents must obey the following criteria:</p>
 
   <ul>
@@ -15506,7 +15508,7 @@
   equal to the number of ranges represented by the object.</p>
 
   <p>When a <code>ByteRanges</code> object is said to be a
-  <dfn>normalised <code>ByteRanges</code> object</dfn>, the ranges it
+  <dfn>normalized <code>ByteRanges</code> object</dfn>, the ranges it
   represents must obey the following criteria:</p>
 
   <ul>
@@ -15764,7 +15766,7 @@
   <code title="attr-canvas-height">height</code> attributes are set
   (whether to a new value or to the previous value), the bitmap and
   any associated contexts must be cleared back to their initial state
-  and reinitialised with the newly specified coordinate space
+  and reinitialized with the newly specified coordinate space
   dimensions.</p>
 
   <p>The <dfn title="dom-canvas-width"><code>width</code></dfn> and
@@ -15785,7 +15787,7 @@
   </div>
 
 
-  <p>When the canvas is initialised it must be set to fully
+  <p>When the canvas is initialized it must be set to fully
   transparent black.</p>
 
 
@@ -15885,7 +15887,7 @@
   <code title="canvas-context-2d">2d</code> argument a second time
   must return the same object.</p>
 
-  <p>The 2D context represents a flat cartesian surface whose origin
+  <p>The 2D context represents a flat Cartesian surface whose origin
   (0,0) is at the top left corner, with the coordinate space having
   <var title="">x</var> values increasing when going right, and <var
   title="">y</var> values increasing when going down.</p>
@@ -16286,7 +16288,7 @@
   </dl>
 
   <p>These values are all case-sensitive — they must be used
-  exactly as shown. User agents must not recognise values that do not
+  exactly as shown. User agents must not recognize values that do not
   exactly match the values given above.</p>
 
   <p>The operators in the above list must be treated as described by
@@ -16298,7 +16300,7 @@
         <dd><cite>Compositing Digital Images</cite>, SIGGRAPH '84: Proceedings of the 11th annual conference on Computer graphics and interactive techniques, Volume 18, Number 3, T. Porter, T Duff. ACM Press, July 1984. ISBN 0-89791-138-5.</dd>
   -->
 
-  <p>On setting, if the user agent does not recognise the specified
+  <p>On setting, if the user agent does not recognize the specified
   value, it must be ignored, leaving the value of <code
   title="dom-context-2d-globalCompositeOperation">globalCompositeOperation</code>
   unaffected.</p>
@@ -16331,14 +16333,14 @@
   value.</p>
 
   <p>On getting, if the value is a color, then the <span
-  title="serialisation of a color">serialisation of the color</span>
+  title="serialization of a color">serialization of the color</span>
   must be returned. Otherwise, if it is not a color but a
   <code>CanvasGradient</code> or <code>CanvasPattern</code>, then the
   respective object must be returned. (Such objects are opaque and
   therefore only useful for assigning to other attributes or for
   comparison to other gradients or patterns.)</p>
 
-  <p>The <dfn>serialisation of a color</dfn> for a color value is a
+  <p>The <dfn>serialization of a color</dfn> for a color value is a
   string, computed as follows: if it has alpha equal to 1.0, then the
   string is a lowercase six-digit hex value, prefixed with a "#"
   character (U+0023 NUMBER SIGN), with the first two digits
@@ -16411,7 +16413,7 @@
   title="dom-context-2d-createLinearGradient">createLinearGradient()</code>
   are infinite or NaN, the method must raise an
   <code>INDEX_SIZE_ERR</code> exception. Otherwise, the method must
-  return a linear <code>CanvasGradient</code> initialised with the
+  return a linear <code>CanvasGradient</code> initialized with the
   specified line.</p>
 
   <p>Linear gradients must be rendered such that at and before the
@@ -16426,8 +16428,8 @@
   title="">x<sub>1</sub></var></span> and <span><var
   title="">y<sub>0</sub></var> = <var
   title="">y<sub>1</sub></var></span>, then the linear gradient must
-  paint nothing.</p> <!-- XXX could make this paint the start colour,
-  or the end colour, or raise an exception -->
+  paint nothing.</p> <!-- XXX could make this paint the start color,
+  or the end color, or raise an exception -->
 
   <p>The <dfn
   title="dom-context-2d-createRadialGradient"><code>createRadialGradient(<var
@@ -16442,7 +16444,7 @@
   units. If either of <var title="">r0</var> or <var title="">r1</var>
   are negative, or if any of the arguments are infinite or NaN, an
   <code>INDEX_SIZE_ERR</code> exception must be raised. Otherwise, the
-  method must return a radial <code>CanvasGradient</code> initialised
+  method must return a radial <code>CanvasGradient</code> initialized
   with the two specified circles, after transforming them according to
   the <span title="dom-context-2d-transformation">current
   transformation matrix</span>.</p>
@@ -16458,7 +16460,7 @@
    title="">r<sub>0</sub></var> = <var
    title="">r<sub>1</sub></var></span>, then the radial gradient must
    paint nothing. Abort these steps.</p> <!-- XXX could make this
-   paint the start colour, or the end colour, or a circle of one in
+   paint the start color, or the end color, or a circle of one in
    the other, or raise an exception --> </li>
 
    <li>
@@ -16543,11 +16545,11 @@
   <code title="">repeat-x</code>, <code title="">repeat-y</code>,
   <code title="">no-repeat</code>. If the empty string or null is
   specified, <code title="">repeat</code> must be assumed. If an
-  unrecognised value is given, then the user agent must raise a
-  <code>SYNTAX_ERR</code> exception. User agents must recognise the
+  unrecognized value is given, then the user agent must raise a
+  <code>SYNTAX_ERR</code> exception. User agents must recognize the
   four values described above exactly (e.g. they must not do case
   folding). The method must return a <code>CanvasPattern</code> object
-  suitably initialised.</p>
+  suitably initialized.</p>
 
   <p>The <var title="">image</var> argument must be an instance of an
   <code>HTMLImageElement</code> or <code>HTMLCanvasElement</code>. If
@@ -16564,7 +16566,7 @@
   <!-- drawImage() has an equivalent paragraph -->
 
   <p>If the <var title="">image</var> argument is an
-  <code>HTMLCanvasElement</code> object with either a horizonal
+  <code>HTMLCanvasElement</code> object with either a horizontal
   dimension or a vertical dimension equal to zero, then the
   implementation must raise an <code>INVALID_STATE_ERR</code>
   exception.</p>
@@ -16680,7 +16682,7 @@
   <p>The <code>miter</code> value means that a second filled triangle
   must (if it can given the miter length) be rendered at the join,
   with one line being the line between the two aforementioned corners,
-  abuting the first triangle, and the other two being continuations of
+  abutting the first triangle, and the other two being continuations of
   the outside edges of the two joining lines, as long as required to
   intersect without going over the miter length.</p>
 
@@ -16740,8 +16742,8 @@
   title="dom-context-2d-shadowColor">shadowColor</code> attribute
   initially must be fully-transparent black.</p>
 
-  <p>On getting, the <span title="serialisation of a
-  color">serialisation of the color</span> must be returned.</p>
+  <p>On getting, the <span title="serialization of a
+  color">serialization of the color</span> must be returned.</p>
 
   <p>On setting, the new value must be parsed as a CSS <color>
   value and the color assigned. If the value is not a valid color,
@@ -17155,14 +17157,14 @@
   clipping region, without affecting the actual subpaths. The new
   clipping region replaces the current clipping region.</p>
 
-  <p>When the context is initialised, the clipping region must be set
+  <p>When the context is initialized, the clipping region must be set
   to the rectangle with the top left corner at (0,0) and the width and
   height of the coordinate space.</p>
 
   <!-- XXXv4
    Jordan OSETE suggests:
     * support ways of extending the clipping region (union instead of intersection)
-       - also "add", "substract", "replace", "intersect" and "xor"
+       - also "add", "subtract", "replace", "intersect" and "xor"
     * support ways of resetting the clipping region without save/restore
   -->
 
@@ -17199,9 +17201,9 @@
   make the font look very ugly.</p>
 
   <p>On getting, the <code title="dom-context-2d-font">font</code>
-  attribute must return the serialised form of the current font of the
+  attribute must return the serialized form of the current font of the
   context. <a href="#refsCSSOM">[CSSOM]</a><!-- XXX ensure that this
-  defines serialisation of 'font' --></p>
+  defines serialization of 'font' --></p>
 
   <p>When the context is created, the font of the context must be set
   to 10px sans-serif. When the 'font-size' component is set to lengths
@@ -17324,7 +17326,7 @@
    line box is greater than <var title="">maxWidth</var> CSS pixels,
    then change <var title="">font</var> to have a more condensed font
    (if one is available or if a reasonably readable one can be
-   synthesised by applying a horizontal scale factor to the font) or a
+   synthesized by applying a horizontal scale factor to the font) or a
    smaller font, and return to the previous step.</p></li>
 
    <li>
@@ -17526,7 +17528,7 @@
    in the hypothetical line box is greater than <var
    title="">maxHeight</var> CSS pixels, then change <var
    title="">font</var> to have a more condensed font (if one is
-   available or if a reasonably readable one can be synthesised by
+   available or if a reasonably readable one can be synthesized by
    applying an appropriate scale factor to the font) or a smaller
    font, and return to the previous step.</p></li>
 
@@ -17721,7 +17723,7 @@
 
   <!-- handled by the next paragraph
   <p>If the <var title="">image</var> argument is an
-  <code>HTMLCanvasElement</code> object with either a horizonal
+  <code>HTMLCanvasElement</code> object with either a horizontal
   dimension or a vertical dimension equal to zero, then the
   implementation must raise an <code>INVALID_STATE_ERR</code>
   exception.</p>
@@ -17808,7 +17810,7 @@
   title="">sx</var>, <var title="">sy</var>, <var title="">sw</var>,
   <var title="">sh</var>)</code></dfn> method must return an
   <code>ImageData</code> object representing the underlying pixel data
-  for the area of the canvas denoted by the rectanglewhose corners are
+  for the area of the canvas denoted by the rectangle whose corners are
   the four points (<var title="">sx</var>, <var title="">sy</var>),
   (<span><var title="">sx</var>+<var title="">sw</var></span>, <var
   title="">sy</var>), (<span><var title="">sx</var>+<var
@@ -17826,14 +17828,14 @@
   title="">sh</var> arguments are zero, the method must instead raise
   an <code>INDEX_SIZE_ERR</code> exception.</p>
 
-  <p><code>ImageData</code> objects must be initialised so that their
+  <p><code>ImageData</code> objects must be initialized so that their
   <dfn title="dom-imagedata-width"><code>width</code></dfn> attribute
   is set to <var title="">w</var>, the number of physical device
   pixels per row in the image data, their <dfn
   title="dom-imagedata-height"><code>height</code></dfn> attribute is
   set to <var title="">h</var>, the number of rows in the image data,
   and the <dfn title="dom-imagedata-data"><code>data</code></dfn>
-  attribute is initialised to an array of <var
+  attribute is initialized to an array of <var
   title="">h</var>×<var title="">w</var>×4 integers. The
   pixels must be represented in this array in left-to-right order, row
   by row, starting at the top left, with each pixel's red, green,
@@ -17871,7 +17873,7 @@
   title="">dirtyHeight</var>)</code></dfn> method writes data from
   <code>ImageData</code> structures back to the canvas.</p>
 
-  <p>If the first argment to the method is null or not an
+  <p>If the first argument to the method is null or not an
   <code>ImageData</code> object that was returned by <code
   title="dom-context-2d-createImageData">createImageData()</code> or
   <code title="dom-context-2d-getImageData">getImageData()</code> then
@@ -17976,7 +17978,7 @@
    title="">y</var> < <span><var
    title="">dirtyY</var>+<var
    title="">dirtyHeight</var></span></span>, copy the four channels of
-   thr pixel with coordinate (<var title="">x</var>, <var
+   the pixel with coordinate (<var title="">x</var>, <var
    title="">y</var>) in the <var title="">imagedata</var> data
    structure to the pixel with coordinate (<span><var
    title="">x<sub>device</sub></var>+<var title="">x</var></span>,
@@ -18124,7 +18126,7 @@
 
    <li><p>Render the shape or image, creating image <var
    title="">A</var>, as described in the previous sections. For
-   shapes, the current fill, stroke, and line styles must be honoured,
+   shapes, the current fill, stroke, and line styles must be honored,
    and the stroke must itself also be subjected to the current
    transformation matrix.</p></li>
 
@@ -18173,7 +18175,7 @@
 
   <h5>Color spaces and color correction</h5>
 
-  <p>The <code>canvas</code> APIs must perform colour correction at
+  <p>The <code>canvas</code> APIs must perform color correction at
   only two points: when rendering images with their own gamma
   correction and color space information onto the canvas, to convert
   the image to the color space used by the canvas (e.g. using the
@@ -18305,7 +18307,7 @@
    </dd>
   </dl>
 
-  <p>The <code>map</code> element, in conjuction with any
+  <p>The <code>map</code> element, in conjunction with any
   <code>area</code> element descendants, defines an <span>image
   map</span>.</p>
 
@@ -18424,7 +18426,7 @@
      <td>Non-conforming
   </table>
 
-  <p>The attribute may be ommited. The <i>missing value default</i> is
+  <p>The attribute may be omitted. The <i>missing value default</i> is
   the <span title="attr-area-shape-rect">rectangle</span> state.</p>
 
   <p>The <dfn title="attr-area-coords"><code>coords</code></dfn>
@@ -18845,7 +18847,7 @@
   not match the element's content model was replaced, for the purposes
   of MathML layout and rendering, by an <code title="">merror</code>
   element in the <span>MathML namespace</span> containing some
-  appropiate error message.</p>
+  appropriate error message.</p>
 
   <p>To enable authors to use MathML tools that only accept MathML in
   its XML form, interactive HTML user agents are encouraged to
@@ -18981,7 +18983,7 @@
 
      <li>One or more <code>tr</code> elements. <strong
      class="note">(Only expressible in the <span title="">XML
-     serialisation</span><!-- XXX xref -->.)</strong></li>
+     serialization</span><!-- XXX xref -->.)</strong></li>
 
     </ul>
 
@@ -19753,7 +19755,7 @@
   title="">y</var>=<var title="">y<sub
   title="">height</sub></var>-1</span>, for a particular value of <var
   title="">x</var>. Columns can correspond to <code>col</code>
-  elements, but in the absense of <code>col</code> elements are
+  elements, but in the absence of <code>col</code> elements are
   implied.</p>
 
   <p>A <dfn title="concept-row-group">row group</dfn> is a set of
@@ -19852,7 +19854,7 @@
     <!-- this step is here just so that we can be sure to have a first
     element in the next step, so that we can set up the "advance"
     exception-handling thingy below; otherwise it'd be more
-    complicated. it's not a perf optimisation per se. -->
+    complicated. it's not a perf optimization per se. -->
 
     <p>If the <code>table</code> element has no children elements,
     then return <var title="">the table</var> (which will be empty),
@@ -20912,8 +20914,8 @@
   href="#refsUNICODE">[UNICODE]</a></p>
 
   <p>User agents may remove <span title="empty data cell">empty data
-  cells</span> when analysing data in a <span title="concept
-  table">table</span>.</p>
+  cells</span> when analyzing data in a <span
+  title="concept-table">table</span>.</p>
 
 
   <h3 id="forms">Forms</h3>
@@ -21607,9 +21609,9 @@
   documents</span>.</p>
 
   <p class="note"><strong>The <code>noscript</code> element is only
-  effective in the <span title="">HTML serialisation</span><!-- XXX
+  effective in the <span title="">HTML serialization</span><!-- XXX
   xref -->, it has no effect in the <span title="">XML
-  serialisation</span><!-- XXX xref -->.</strong></p>
+  serialization</span><!-- XXX xref -->.</strong></p>
 
   <p>When used in <span>HTML documents</span>, the allowed content
   model is as follows:</p>
@@ -22719,7 +22721,7 @@
     title="">classes</var>)</code> method must add no classes.</p>
 
     <p class="big-issue"><!-- select-provider-selection
-    XXX-->autoselect some rows when initialised, reflect the selection
+    XXX-->autoselect some rows when initialized, reflect the selection
     in the select, reflect the multiple attribute somehow.</p>
 
     <p>The data provider must call the <code>datagrid</code>'s update
@@ -22816,7 +22818,7 @@
     title="">i</var>)</code> must return the first <code>menu</code>
     element descendant (in the real DOM) of the row's element, that is
     not also a descendant of another element in the filtered view that
-    is a decsendant of the row's element. (This is analogous to the
+    is a descendant of the row's element. (This is analogous to the
     image case above.)</p>
 
     <p><code title="dom-provider-getRowClasses">getRowClasses(<var
@@ -23422,14 +23424,14 @@
    class applies to the cell. If it does, the cell is unchecked.
    Otherwise, the <code
    title="datagrid-cell-class-indeterminate">indeterminate</code>
-   class appplies to the cell and the cell's checkbox is in an
+   class applies to the cell and the cell's checkbox is in an
    indeterminate state. When the <code
    title="datagrid-cell-class-indeterminate">indeterminate</code>
-   class appplies to the cell, the checkbox is a tristate checkbox,
+   class applies to the cell, the checkbox is a tristate checkbox,
    and the user can set it to the indeterminate state. Otherwise, only
    the <code title="datagrid-cell-class-checked">checked</code> and/or
    <code title="datagrid-cell-class-unchecked">unchecked</code>
-   classes apply to the cell, and the cell can only be toggled betwen
+   classes apply to the cell, and the cell can only be toggled between
    those two states.</dd>
 
   </dl>
@@ -23468,7 +23470,7 @@
   title="dom-provider-getRowCount">getRowCount()</code> varies in ways
   that do not match the calls made to the update methods, the user
   agent may disable the <code>datagrid</code>. User agents that do not
-  disable the <code>datagrid</code> in inconsistent cases must honour
+  disable the <code>datagrid</code> in inconsistent cases must honor
   the most recently returned values.</p>
 
   <p>User agents may cache returned values so that the data provider
@@ -23519,7 +23521,7 @@
   title="">row</var>, <var title="">count</var>)</code></dfn> method
   is called, the user agent must assume that <var title="">count</var>
   new rows have been inserted, such that the first new row is
-  indentified by <var title="">row</var>. The user agent must update
+  identified by <var title="">row</var>. The user agent must update
   its rendering and the selection accordingly. The new rows should not
   be selected.</p>
 
@@ -23657,7 +23659,7 @@
   are currently selected. Initially no rows are selected, but this can
   be changed via the methods described in this section. <!--XXX
   select-provider-selection The default data provider, for instance,
-  changes which rows are selected when it is first initialised.--></p>
+  changes which rows are selected when it is first initialized.--></p>
 
   <p>The selection of a <code>datagrid</code> is represented by its
   <dfn title="dom-datagrid-selection"><code>selection</code></dfn> DOM
@@ -23987,7 +23989,7 @@
   any of the actions described above to happen.</p>
 
   <p class="big-issue"> should change all the above so it actually is
-  just trigged by a click event, then we could remove the shadowing
+  just triggered by a click event, then we could remove the shadowing
   click() method and rely on actual events. </p>
 
   <p class="big-issue">Need to define the command="" attribute</p>
@@ -24120,7 +24122,7 @@
    <li><a href="about.html">About</a></li>
   </menu>
  </li>
-</menubar>
+</menu>
 
 ...
 
@@ -24149,7 +24151,7 @@
    </select>
    <span><input type="submit" value="Go"></span>
   </menu>
- </menubar>
+ </menu>
 </form></pre>
 
 <form ...>
@@ -25430,7 +25432,7 @@
    string as the mode, and the <var title="">existing nodes</var> lists
    as the lists of existing nodes.</p></li>
 
-<!--(for now, since we can't guarentee that we'll reset the dataNode
+<!--(for now, since we can't guarantee that we'll reset the dataNode
 attribute of nodes that are dynamically moved around between regens,
 we'll just act as if the dataNode attribute is set on creation and
 never reset. This is nice and consistent.)
@@ -25448,7 +25450,7 @@
   each other recursively, the <span>Levenberg data node
   algorithm</span> and the <span>Levenberg template node
   algorithm</span>. These algorithms use the data structures
-  initialised by the set of steps described above.</p>
+  initialized by the set of steps described above.</p>
 
   <p>The <dfn>Levenberg data node algorithm</dfn> is as follows. It is
   always invoked with three DOM nodes, one string, and a set of lists
@@ -26044,7 +26046,7 @@
   contexts</span> must execute on a single conceptual thread. The
   dispatch of events fired by the user agent (e.g. in response to user
   actions or network activity) and the execution of any scripts
-  associated with timers must be serialised so that for each
+  associated with timers must be serialized so that for each
   <span>unit of related browsing contexts</span> there is only one
   script being executed at a time.</p>
 <!-- XXX queue concept should be made generic across the spec.
@@ -26071,7 +26073,7 @@
   title="">_blank</code>, <code title="">_self</code>, <code
   title="">_parent</code>, or <code title="">_top</code>.</p>
 
-  <p><dfn>The rules for chosing a browsing context given a browsing
+  <p><dfn>The rules for choosing a browsing context given a browsing
   context name</dfn> are as follows. The rules assume that they are
   being applied in the context of a <span>browsing context</span>.</p>
 
@@ -26326,7 +26328,7 @@
    <dt><dfn title="dom-image-w"><code>Image(in unsigned long <var title="">w</var>)</code></dfn></dt>
    <dt><dfn title="dom-image-wh"><code>Image(in unsigned long <var title="">w</var>, in unsigned long <var title="">h</var>)</code></dfn></dt>
 
-   <dd><p>When invoked as corstructors, these must return a new
+   <dd><p>When invoked as constructors, these must return a new
    <code>HTMLImageElement</code> object (a new <code>img</code>
    element). If the <var title="">h</var> argument is present, the new
    object's <code title="attr-img-height">height</code> content
@@ -26390,7 +26392,7 @@
 
   <p>When the method is invoked, the user agent must first select a
   <span>browsing context</span> to navigate by applying <span>the
-  rules for chosing a browsing context given a browsing context
+  rules for choosing a browsing context given a browsing context
   name</span> using the <var title="">target</var> argument as the
   name and the <span>browsing context</span> of the script as the
   context in which the algorithm is executed, unless the user has
@@ -26412,7 +26414,7 @@
   <span title="replacement enabled">replacement must be
   enabled</span>; otherwise, it must not be enabled unless the
   <span>browsing context</span> was just created as part of the
-  <span>the rules for chosing a browsing context given a browsing
+  <span>the rules for choosing a browsing context given a browsing
   context name</span>. The navigation must be done with the
   <span>browsing context</span> corresponding to the
   <code>Window</code> object that is the <span>script execution
@@ -26696,7 +26698,7 @@
 
     <p>When a <code>Document</code> is created, unless stated
     otherwise above, its <span>effective script origin</span> is
-    initialised to the <span>origin</span> of the
+    initialized to the <span>origin</span> of the
     <code>Document</code>. However, the <code
     title="dom-document-domain">document.domain</code> attribute can
     be used to change it.</p>
@@ -26705,7 +26707,7 @@
 
   </dl>
 
-  <p>The <dfn>serialisation of an origin</dfn> is the string obtained
+  <p>The <dfn>serialization of an origin</dfn> is the string obtained
   by applying the following algorithm to the given
   <span>origin</span>:</p>
 
@@ -26769,7 +26771,7 @@
   <h4>Relaxing the same-origin restriction</h4>
 
   <p>The <dfn title="dom-document-domain"><code>domain</code></dfn>
-  attribute on <code>Document</code> objects must be initialised to
+  attribute on <code>Document</code> objects must be initialized to
   <span>the document's domain</span>, if it has one, and the empty
   string otherwise. On getting, the attribute must return its current
   value, unless the document was created by
@@ -27552,8 +27554,8 @@
     <p>The three arguments passed to the function are all
     <code>DOMString</code>s; the first must give the message that the
     UA is considering reporting, the second must give the URI to the
-    resource in which the error occured, and the third must give the
-    line number in that resource on which the error occured.</p>
+    resource in which the error occurred, and the third must give the
+    line number in that resource on which the error occurred.</p>
 
     <p>If the function returns false, then the error should not be
     reported to the user. Otherwise, if the function returns another
@@ -27793,7 +27795,7 @@
 
   <p>These browsing contexts also have an associated <dfn>return
   value</dfn>. The <span>return value</span> of a browsing context
-  must be initialised to the empty string when the browsing context is
+  must be initialized to the empty string when the browsing context is
   created.</p>
 
   <p>The <dfn
@@ -27934,7 +27936,7 @@
      <pre>http://example.com/soup?url=http%3A%2F%2Fwww.example.net%2Fchickenk%C3%AFwi.soup</pre>
 
      <p>This site could then fetch the <code>chickenk&#xEF;wi.soup</code>
-     file and do whatever it is that it does with soup (synthesise it
+     file and do whatever it is that it does with soup (synthesize it
      and ship it to the user, or whatever).</p>
 
     </div>
@@ -28011,7 +28013,7 @@
   gracefully handle such hostile attempts, protecting the user.</p>
 
   <p><strong>Misleading titles.</strong> User agents should not rely
-  wholy on the <var title="">title</var> argument to the methods when
+  wholly on the <var title="">title</var> argument to the methods when
   presenting the registered handlers to the user, since sites could
   easily lie. For example, a site <code>hostile.example.net</code>
   could claim that it was registering the "Cuddly Bear Happy Content
@@ -28261,7 +28263,7 @@
     </dl>
 
     <p class="note">A URI in the list can be flagged with multiple
-    different types, and thus an entry can end up being categorised as
+    different types, and thus an entry can end up being categorized as
     multiple entries. For example, an entry can be an explicit entry
     and a dynamic entry at the same time.</p>
 
@@ -28450,7 +28452,7 @@
 
   <ol>
    
-   <li><p>The user agent must decode the bytestream corresponding with
+   <li><p>The user agent must decode the byte stream corresponding with
    the manifest to be parsed, treating it as UTF-8. Bytes or sequences
    of bytes that are not valid UTF-8 sequences must be interpreted as
    a U+FFFD REPLACEMENT CHARACTER. <!--All U+0000 NULL characters must
@@ -28473,7 +28475,7 @@
    whitelist</span>.</p></li>
 
    <li><p>Let <var title="">input</var> be the decoded text of the
-   manifest's bytestream.</p></li>
+   manifest's byte stream.</p></li>
 
    <li><p>Let <var title="">position</var> be a pointer into <var
    title="">input</var>, initially pointing at the first
@@ -28714,7 +28716,7 @@
 
     <p>If there is already a resource with the URI of <var
     title="">manifest URI</var> in <var title="">cache</var>, and
-    that resource is categorised as a <span
+    that resource is categorized as a <span
     title="concept-appcache-manifest">manifest</span>, then this is an
     <dfn title="concept-appcache-upgrade">upgrade
     attempt</dfn>. Otherwise, this is a <dfn
@@ -28892,7 +28894,7 @@
 
       <p>Fetch the resource. If this is an <span
       title="concept-appcache-upgrade">upgrade attempt</span>, then
-      use <var title="">cache</var> as an HTTP cache, and honour HTTP
+      use <var title="">cache</var> as an HTTP cache, and honor HTTP
       caching semantics (such as expiration, ETags, and so forth) with
       respect to that cache. User agents may also have other caches in
       place that are also honored. If the resource in question is
@@ -28918,28 +28920,28 @@
      the <var title="">new cache</var>.</p></li>
 
      <li><p>If the URI being processed was flagged as an "explicit
-     entry" in <var title="">file list</var>, then categorise the
+     entry" in <var title="">file list</var>, then categorize the
      entry as an <span title="concept-appcache-explicit">explicit
      entry</span>.</p></li>
 
      <li><p>If the URI being processed was flagged as a "fallback
-     entry" in <var title="">file list</var>, then categorise the
+     entry" in <var title="">file list</var>, then categorize the
      entry as a <span title="concept-appcache-fallback">fallback
      entry</span>.</p></li>
 
      <li><p>If the URI being processed was flagged as a "opportunistic
-     entry" in <var title="">file list</var>, then categorise the
+     entry" in <var title="">file list</var>, then categorize the
      entry as an <span
      title="concept-appcache-oppcache">opportunistically cached
      entry</span>.</p></li>
 
      <li><p>If the URI being processed was flagged as an "implicit
-     entry" in <var title="">file list</var>, then categorise the
+     entry" in <var title="">file list</var>, then categorize the
      entry as a <span title="concept-appcache-implicit">implicit
      entry</span>.</p></li>
 
      <li><p>If the URI being processed was flagged as an "dynamic
-     entry" in <var title="">file list</var>, then categorise the
+     entry" in <var title="">file list</var>, then categorize the
      entry as a <span title="concept-appcache-dynamic">dynamic
      entry</span>.</p></li>
 
@@ -28948,7 +28950,7 @@
    </li>
 
    <li><p>Store <var title="">manifest</var> in <var title="">new
-   cache</var>, if it's not there already, and categorise this entry
+   cache</var>, if it's not there already, and categorize this entry
    (whether newly added or not) as <span
    title="concept-appcache-manifest">the manifest</span>.</p></li>
 
@@ -29101,7 +29103,7 @@
 
    <dd>
 
-    <p>As an optimisation, if the resource was loaded from an
+    <p>As an optimization, if the resource was loaded from an
     <span>application cache</span>, and the manifest URI of that cache
     doesn't match the manifest URI with which the algorithm was
     invoked, then the user agent should mark the entry in that
@@ -29171,9 +29173,9 @@
      <li><p>If there is already an <span>application cache</span>
      identified by this manifest URI, and the most up to date version
      of that <span>application cache</span> contains a resource with
-     the URI of the manifest, and that resource is categorised as a
+     the URI of the manifest, and that resource is categorized as a
      <span title="concept-appcache-manifest">manifest</span>, then:
-     store the resource in the matching cache, categorised as an <span
+     store the resource in the matching cache, categorized as an <span
      title="concept-appcache-implicit">implicit entry</span>,
      associate the <code>Document</code> with that cache, invoke the
      <span>application cache update process</span>, and abort these
@@ -29190,9 +29192,9 @@
      identified by this manifest URI, then the most up to date version
      of that <span>application cache</span> does not yet contain a
      resource with the URI of the manifest, or it does but that
-     resource is not yet categorised as a <span
+     resource is not yet categorized as a <span
      title="concept-appcache-manifest">manifest</span>: store the
-     resource in that cache, categorised as an <span
+     resource in that cache, categorized as an <span
      title="concept-appcache-implicit">implicit entry</span>
      (replacing the file's previous contents if it was already in the
      cache, but not removing any other categories it might have), and
@@ -29201,7 +29203,7 @@
 
      <li><p>Otherwise, there is no matching <span>application
      cache</span>: create a new application cache identified by this
-     manifest URI, store the resource in that cache, categorised as an
+     manifest URI, store the resource in that cache, categorized as an
      <span title="concept-appcache-implicit">implicit entry</span>,
      and then invoke the <span>application cache update
      process</span>.</p></li>
@@ -29363,7 +29365,7 @@
    an <span>application cache</span> whose group is in the <i>idle</i>
    <span title="concept-appcache-states">update status</span>, and
    that application cache is the newest cache in its group that
-   contains a resource categorised as a <span
+   contains a resource categorized as a <span
    title="concept-appcache-manifest">manifest</span>.</p></dd>
 
    <dt><dfn title="dom-appcache-CHECKING"><code>CHECKING</code></dfn>
@@ -29389,7 +29391,7 @@
    an <span>application cache</span> whose group is in the <i>idle</i>
    <span title="concept-appcache-states">update status</span>, but
    that application cache is <em>not</em> the newest cache in its
-   group that contains a resource categorised as a <span
+   group that contains a resource categorized as a <span
    title="concept-appcache-manifest">manifest</span>.</p></dd>
 
   </dl>
@@ -29443,7 +29445,7 @@
    <li><p>If there is already a resource in in the <span>application
    cache</span> with which the <code>ApplicationCache</code> object is
    associated that has the address <var title="">uri</var>, then
-   ensure that entry is categorised as a <span
+   ensure that entry is categorized as a <span
    title="concept-appcache-dynamic">dynamic entry</span> and return
    and abort these steps.</p></li>
 
@@ -29468,7 +29470,7 @@
     <code>ApplicationCache</code> object is associated.</p>
 
     <p>Add the fetched resource to the <span>application cache</span>
-    and categorise it as a <span
+    and categorize it as a <span
     title="concept-appcache-dynamic">dynamic entry</span> before
     letting any such scripts resume.</p>
   
@@ -29487,12 +29489,12 @@
 
   <p>The <dfn title="dom-appcache-remove"><code>remove(<var
   title="">uri</var>)</code></dfn> method must remove the <span
-  title="concept-appcache-dynamic">dynamic entry</span> categorisation
+  title="concept-appcache-dynamic">dynamic entry</span> categorization
   of any entry with the address <var title="">uri</var> in the
   <span>application cache</span> with which the
   <code>ApplicationCache</code> object is associated. <span
   class="big-issue">Resolve relative URIs... (ignore syntax
-  errors)</span> If this removes the last categorisation of an entry
+  errors)</span> If this removes the last categorization of an entry
   in that cache, then the entry must be removed entirely (such that if
   it is re-added, it will be loaded from the network again). If the
   <code>ApplicationCache</code> object is not associated with any
@@ -29540,7 +29542,7 @@
    found in the previous step.)</p></li>
 
    <li><p>Check that there is an application cache in the same group
-   as <var title="">cache</var> which has an entry categorised as a
+   as <var title="">cache</var> which has an entry categorized as a
    <span title="concept-appcache-manifest">manifest</span> that has is
    newer than <var title="">cache</var>. If there is not, then raise
    an <code>INVALID_STATE_ERR</code> exception and abort these
@@ -29548,7 +29550,7 @@
 
    <li><p>Let <var title="">new cache</var> be the newest
    <span>application cache</span> in the same group as <var
-   title="">cache</var> which has an entry categorised as a <span
+   title="">cache</var> which has an entry categorized as a <span
    title="concept-appcache-manifest">manifest</span>.</p></li>
 
    <li><p>Unassociate <var title="">document</var> from <var
@@ -30205,7 +30207,7 @@
     with the <span>same origin</span> as the URI in question, and that
     have this URI as one of their entries (excluding entries marked as
     <span title="concept-appcache-foreign">foreign</span>), and that
-    already contain their manifest, categorised as a <span
+    already contain their manifest, categorized as a <span
     title="concept-appcache-manifest">manifest</span>. If so, then the
     user agent must then fetch the resource from the <span
     title="concept-appcache-selection">most appropriate application
@@ -30289,7 +30291,7 @@
       the user didn't cancel the request, the user agent must cache
       the resource in all the application caches that have a <span
       title="concept-appcache-matches-oppcache">matching opportunistic
-      caching namespace</span>, categorised as <span
+      caching namespace</span>, categorized as <span
       title="concept-appcache-oppcache">opportunistically cached
       entries</span>. Meanwhile, the user must continue along these
       steps.</p>
@@ -31160,7 +31162,7 @@
 
          </dd>
 
-         <dt>Otherwies, if the <var
+         <dt>Otherwise, if the <var
          title="">index<sub>stream</sub></var>th byte of the pattern
          is a "<em>WS</em>" byte:</dt>
 
@@ -31510,7 +31512,7 @@
 
   </ol>
 
-  <p class="note">For efficiency reaons, implementations may wish to
+  <p class="note">For efficiency reasons, implementations may wish to
   implement this algorithm and the algorithm for detecting the
   character encoding of HTML documents in parallel.</p>
 
@@ -31534,7 +31536,7 @@
   HTTP headers and one of the other ones is syntactically correct). <a
   href="#refsHTTP">[HTTP]</a></p>
 
-  <p>For resources fetched from the filesystem, user agents should use
+  <p>For resources fetched from the file system, user agents should use
   platform-specific conventions, e.g. operating system extension/type
   mappings.</p>
 
@@ -31584,7 +31586,7 @@
      U+0027 APOSTROPHE ("'") in  <var title="">s</var></dt>
 
      <dd><p>Return the string between this character and the next
-     earliest occurance of this character.</dd>
+     earliest occurrence of this character.</dd>
 
      <dt>If it is an unmatched U+0022 QUOTATION MARK ('"')</dt>
      <dt>If it is an unmatched U+0027 APOSTROPHE ("'")</dt>
@@ -31674,7 +31676,7 @@
   multiple windows, and lasts beyond the current session. In
   particular, Web applications may wish to store megabytes of user
   data, such as entire user-authored documents or a user's mailbox, on
-  the clientside for performance reasons.</p>
+  the client side for performance reasons.</p>
 
   <p>Again, cookies do not handle this case well, because they are
   transmitted with every request.</p>
@@ -32018,7 +32020,7 @@
   storage areas simultaneously in a predictable manner. Scripts must
   not be able to detect any concurrent script execution.</p>
 
-  <p>This is required to guarentee that the <code
+  <p>This is required to guarantee that the <code
   title="dom-Storage-length">length</code> attribute of a
   <code>Storage</code> object never changes while a script is
   executing, other than in a way that is predictable by the script
@@ -32058,7 +32060,7 @@
 
 <!-- include an example that does something like the following to show
 you should never embed strings straight into the statement, even when you
-have a variable and unknownable number of literals coming:
+have a variable and unknowable number of literals coming:
    var q = "";
    for each (var i in array)
      q += (q == "" ? "" : ", ") + "?";
@@ -32117,7 +32119,7 @@
   the supported set of names.</p>
 
   <p>User agents are expected to use the display name and the
-  estimated database size to optimise the user experience. For
+  estimated database size to optimize the user experience. For
   example, a user agent could use the estimated size to suggest an
   initial quota to the user. This allows a site that is aware that it
   will try to use hundreds of megabytes to declare this upfront,
@@ -32263,7 +32265,7 @@
     replaced by the <var title="">n</var>th value in the <var
     title="">arguments</var> array.)</p>
 
-    <p>If the second argument is ommitted or null, then treat the <var
+    <p>If the second argument is omitted or null, then treat the <var
     title="">arguments</var> array as empty.</p>
 
     <p>The result is <i>the statement</i>.</p>
@@ -32300,7 +32302,7 @@
 
   <p>The user agent must act as if the database was hosted in an
   otherwise completely empty environment with no resources. For
-  example, attempts to read from or write to the filesystem will
+  example, attempts to read from or write to the file system will
   fail.</p>
 
 
@@ -32457,7 +32459,7 @@
 
   <p>The <dfn title="dom-SQLError-message"><code>message</code></dfn>
   DOM attribute must return an error message describing the error
-  encountered. The message should be localised to the user's
+  encountered. The message should be localized to the user's
   language.</p>
 
 
@@ -32476,7 +32478,7 @@
    <code>SQLTransaction</code> object that represents that
    transaction.</p></li>
 
-   <li><p>If an error occured in the opening of the transaction, jump
+   <li><p>If an error occurred in the opening of the transaction, jump
    to the last step.</p></li>
 
    <li><p>If a <i>preflight operation</i> was defined for this
@@ -32563,7 +32565,7 @@
 
    <li><p>Commit the transaction.</p></li>
 
-   <li><p>If an error occured in the committing of the transaction,
+   <li><p>If an error occurred in the committing of the transaction,
    jump to the last step.</p></li>
 
    <li><p>Invoke the <i>success callback</i>.</p></li>
@@ -32573,7 +32575,7 @@
 
    <li><p>Call the <i>error callback</i> with a newly constructed
    <code>SQLError</code> object that represents the last error to have
-   occured in this transaction. Rollback the transaction. Any
+   occurred in this transaction. Rollback the transaction. Any
    still-pending statements in the transaction are discarded.</p></li>
 
   </ol>
@@ -32678,7 +32680,7 @@
     <p>Site-specific white-listing of access to local storage areas
     and databases: user agents may allow sites to access session
     storage areas in an unrestricted manner, but require the user to
-    authorise access to local storage areas and databases.</p>
+    authorize access to local storage areas and databases.</p>
 
    </li>
 
@@ -32743,7 +32745,7 @@
   <h5>DNS spoofing attacks</h5>
 
   <p>Because of the potential for DNS spoofing attacks, one cannot
-  guarentee that a host claiming to be in a certain domain really is
+  guarantee that a host claiming to be in a certain domain really is
   from that domain. To mitigate this, pages can use SSL. Pages using
   SSL can be sure that only pages using SSL that have certificates
   identifying them as being from the same domain can access their
@@ -32867,7 +32869,7 @@
   href="#linkTypes">allowed values and their meanings</a> are defined
   below. The <code title="attr-hyperlink-rel">rel</code> attribute has
   no default value. If the attribute is omitted or if none of the
-  values in the attribute are recognised by the UA, then the document
+  values in the attribute are recognized by the UA, then the document
   has no particular relationship with the destination resource other
   than there being a hyperlink between the two.</p>
 
@@ -32921,7 +32923,7 @@
   <code>area</code> element that has a <code
   title="attr-hyperlink-target">target</code> attribute, then the
   browsing context that is navigated must be chosen by applying
-  <span>the rules for chosing a browsing context given a browsing
+  <span>the rules for choosing a browsing context given a browsing
   context name</span>, using the value of the <code
   title="attr-hyperlink-target">target</code> attribute as the
   browsing context name. If these rules result in the creation of a
@@ -32941,7 +32943,7 @@
   <code>base</code> element with a <code
   title="attr-base-target">target</code> attribute, then the browsing
   context that is navigated must be chosen by applying <span>the rules
-  for chosing a browsing context given a browsing context name</span>,
+  for choosing a browsing context given a browsing context name</span>,
   using the value of the <code title="attr-base-target">target</code>
   attribute of the first such <code>base</code> element as the
   browsing context name. If these rules result in the creation of a
@@ -33057,7 +33059,7 @@
     <li>It allows the paranoid user to disable the notifications
     without losing the underlying link functionality.</li>
 
-    <li>It allows the UA to optimise the use of available network
+    <li>It allows the UA to optimize the use of available network
     bandwidth so that the target page loads faster.</li>
 
    </ul>
@@ -33065,7 +33067,7 @@
    <p>Thus, while it is possible to track users without this feature,
    authors are encouraged to use the <code
    title="attr-hyperlink-ping">ping</code> attribute so that the user agent
-   can improve <!-- XXX optimise? --> the user experience.</p> <!--
+   can improve <!-- XXX optimize? --> the user experience.</p> <!--
    XXX need a better way to end that sentence. It's what I mean, but
    it sounds kooky. -->
 
@@ -33075,7 +33077,7 @@
 
   <h4 id="linkTypes">Link types</h4>
 
-  <p>The following table summarises the link types that are defined by
+  <p>The following table summarizes the link types that are defined by
   this specification. This table is non-normative; the actual
   definitions for the link types are given in the next few
   sections.</p>
@@ -33232,7 +33234,7 @@
      <td><code title="rel-prefetch">prefetch</code></td>
      <td><span title="external resource link">External Resource</span></td>
      <td><em>not allowed</em></td>
-     <td>Specifies that the target resource should be pre-emptively cached.</td>
+     <td>Specifies that the target resource should be preemptively cached.</td>
     </tr>
 
     <tr>
@@ -33874,7 +33876,7 @@
   <p>The <code title="rel-up">up</code> keyword may be repeated within
   a <code title="attr-hyperlink-rel">rel</code> attribute to indicate
   the hierarchical distance from the current document to the
-  referenced document. Each occurance of the keyword represents one
+  referenced document. Each occurrence of the keyword represents one
   further level. If the <code title="rel-index">index</code> keyword
   is also present, then the number of <code title="rel-up">up</code>
   keywords is the depth of the current page relative to the top of the
@@ -33900,7 +33902,7 @@
   <div class="example">
 
    <p>This can be used to mark up a navigation style sometimes known
-   as breadcrumbs. In the following example, the current page can be
+   as bread crumbs. In the following example, the current page can be
    reached via two paths.</p>
 
    <pre><nav>
@@ -34393,8 +34395,8 @@
   not, or if an element is <span>editable</span> and it has no parent
   element, then the element is an <dfn>editing host</dfn>. Editable
   elements can be nested. User agents must make editing hosts
-  focusable (which typicially means they enter the <span
-  title="tabindex">tab order</span>). An editing host can contain
+  focusable (which typically means they enter the <span
+  title="attr-tabindex">tab order</span>). An editing host can contain
   non-editable sections, these are handled as described below. An
   editing host can contain non-editable sections that contain further
   editing hosts.</p>
@@ -34752,7 +34754,7 @@
   various kinds of data.</p>
 
   <p>When a <code>DataTransfer</code> object is created, it must be
-  initialised as follows:</p>
+  initialized as follows:</p>
 
   <ul>
 
@@ -34906,7 +34908,7 @@
      <td>&#x2713; Bubbles</td>
      <td>&#x2713; Cancelable</td>
      <td>Empty</td>
-     <td><a href="#effectAllowed-initialisation">Same as last event</a></td>
+     <td><a href="#effectAllowed-initialization">Same as last event</a></td>
      <td><code title="">none</code></td>
      <td>Continue the drag-and-drop operation</td>
     </tr>
@@ -34917,8 +34919,8 @@
      <td>&#x2713; Bubbles</td>
      <td>&#x2713; Cancelable</td>
      <td>Empty</td>
-     <td><a href="#effectAllowed-initialisation">Same as last event</a></td>
-     <td><a href="#dropEffect-initialisation">Based on <code>effectAllowed</code> value</a></td>
+     <td><a href="#effectAllowed-initialization">Same as last event</a></td>
+     <td><a href="#dropEffect-initialization">Based on <code>effectAllowed</code> value</a></td>
      <td>Reject <span>immediate user selection</span> as potential <span title="current target element">target element</span></td>
     </tr>
 
@@ -34928,7 +34930,7 @@
      <td>&#x2713; Bubbles</td>
      <td>—</td>
      <td>Empty</td>
-     <td><a href="#effectAllowed-initialisation">Same as last event</a></td>
+     <td><a href="#effectAllowed-initialization">Same as last event</a></td>
      <td><code title="">none</code></td>
      <td>None</td>
     </tr>
@@ -34939,8 +34941,8 @@
      <td>&#x2713; Bubbles</td>
      <td>&#x2713; Cancelable</td>
      <td>Empty</td>
-     <td><a href="#effectAllowed-initialisation">Same as last event</a></td>
-     <td><a href="#dropEffect-initialisation">Based on <code>effectAllowed</code> value</a></td>
+     <td><a href="#effectAllowed-initialization">Same as last event</a></td>
+     <td><a href="#dropEffect-initialization">Based on <code>effectAllowed</code> value</a></td>
      <td>Reset the <span>current drag operation</span> to "none"</td>
     </tr>
 
@@ -34950,7 +34952,7 @@
      <td>&#x2713; Bubbles</td>
      <td>&#x2713; Cancelable</td>
      <td><code>getData()</code> returns data set in <code title="dom-dragstart">dragstart</code> event</td>
-     <td><a href="#effectAllowed-initialisation">Same as last event</a></td>
+     <td><a href="#effectAllowed-initialization">Same as last event</a></td>
      <td><span>Current drag operation</span></td>
      <td>Varies</td>
     </tr>
@@ -34961,7 +34963,7 @@
      <td>&#x2713; Bubbles</td>
      <td>—</td>
      <td>Empty</td>
-     <td><a href="#effectAllowed-initialisation">Same as last event</a></td>
+     <td><a href="#effectAllowed-initialization">Same as last event</a></td>
      <td><span>Current drag operation</span></td>
      <td>Varies</td>
     </tr>
@@ -34976,7 +34978,7 @@
   title="event-drop">drop</code> events, for which the contents are
   set as described in the processing model, below.</p>
 
-  <p id="effectAllowed-initialisation">The <code
+  <p id="effectAllowed-initialization">The <code
   title="dom-DataTransfer-effectAllowed">effectAllowed</code>
   attribute must be set to "<code title="">uninitialized</code>" for
   <code title="event-dragstart">dragstart</code> events, and to
@@ -34985,7 +34987,7 @@
   agent for the purposes of the drag-and-drop model described
   below).</p>
 
-  <p id="dropEffect-initialisation">The <code
+  <p id="dropEffect-initialization">The <code
   title="dom-DataTransfer-dropEffect">dropEffect</code> attribute must
   be set to "<code title="">none</code>" for <code
   title="event-dragstart">dragstart</code>, <code
@@ -35617,7 +35619,7 @@
   drag-and-drop operation initiates, then the user agent must act as
   if the user had indicated (as the <span>immediate user
   selection</span>) a hypothetical application representing the
-  clipbroad. Then, the user agent must act as if the user had ended
+  clipboard. Then, the user agent must act as if the user had ended
   the drag-and-drop operation without canceling it. If the
   drag-and-drop operation didn't get canceled, the user agent should
   then follow the relevant platform-specific conventions for copy
@@ -35989,7 +35991,7 @@
   appears to have separate <span title="undo transaction history">undo
   transaction histories</span> for each form control; similarly, it is
   possible to design systems where the user has access to more undo
-  information than is present in the offical (as described above)
+  information than is present in the official (as described above)
   <span>undo transaction history</span> (such as providing a
   tree-based approach to document state). Such UI models should be
   based upon the single <span>undo transaction history</span>
@@ -36239,7 +36241,7 @@
   either through this interface or via user interaction).</p>
 
   <p>Objects implementing this interface must <dfn
-  title="dom-selection-toString">stringinfy</dfn> to a concatenation
+  title="dom-selection-toString">stringify</dfn> to a concatenation
   of the results of invoking the <code title="">toString()</code>
   method of the <code>Range</code> object on each of the ranges of the
   selection, in the order they appear in the list (first to last).</p>
@@ -37600,7 +37602,7 @@
 
   <p>The user agent must then begin trying to establish a connection
   with the target host and specified port. (This typically would begin
-  in the backgound, while the script continues to execute.)</p>
+  in the background, while the script continues to execute.)</p>
 
   <p>If the <var title="">secure</var> boolean argument is set to
   true, then the user agent must establish a secure connection with
@@ -38247,8 +38249,8 @@
     the value passed as the <var title="">message</var> argument to
     the <code title="dom-window-postMessage">postMessage()</code>
     method, the <code title="dom-MessageEvent-origin">origin</code>
-    attribute must be set to the <span title="serialisation of an
-    origin">serialisation</span> of the <span>origin</span> of the
+    attribute must be set to the <span title="serialization of an
+    origin">serialization</span> of the <span>origin</span> of the
     script that invoked the method, the <code
     title="dom-MessageEvent-lastEventId">lastEventId</code> attribute
     must be set to the empty string, and the <code
@@ -38378,7 +38380,7 @@
   next few sections.</p>
 
   <p>In addition, there are some restrictions on how <span>character
-  encoding declarations</span> are to be serialised, as discussed in
+  encoding declarations</span> are to be serialized, as discussed in
   the section on that topic.</p>
 
   <div class="note">
@@ -38963,7 +38965,7 @@
   <h5 id="cdata-rcdata-restrictions">Restrictions on the contents of CDATA and RCDATA elements</h5>
 
   <p>The text in CDATA and RCDATA elements must not contain any
-  occurences of the string "<code title=""></</code>" (U+003C
+  occurrences of the string "<code title=""></</code>" (U+003C
   LESS-THAN SIGN, U+002F SOLIDUS) followed by characters that
   case-insensitively<!--ASCII--> match the tag name of the element
   followed by one of U+0009 CHARACTER TABULATION, U+000A LINE FEED
@@ -39152,7 +39154,7 @@
    basis.</p>
 
    <p>Authors interested in using SGML tools in their authoring
-   pipeline are encouraged to use XML tools and the XML serialisation
+   pipeline are encouraged to use XML tools and the XML serialization
    of HTML5.</p>
 
   </div>
@@ -39819,7 +39821,7 @@
   inserted. The insertion point is relative to the position of the
   character immediately after it, it is not an absolute offset into
   the input stream. Initially, the insertion point is
-  uninitialised.</p>
+  uninitialized.</p>
 
   <p>The "EOF" character in the tables below is a conceptual character
   representing the end of the <span>input stream</span>. If the parser
@@ -40068,7 +40070,7 @@
   stack.</p>
 
   <p>In the <span>fragment case</span>, the <span>stack of open
-  elements</span> is initialised to contain an <code>html</code>
+  elements</span> is initialized to contain an <code>html</code>
   element that is created as part of <span title="html fragment
   parsing algorithm">that algorithm</span>. (The <span>fragment
   case</span> skips the "<span title="insertion mode: before
@@ -41964,8 +41966,8 @@
   <p class="note">The algorithm described below places no limit on the
   depth of the DOM tree generated, or on the length of tag names,
   attribute names, attribute values, text nodes, etc. While
-  implementators are encouraged to avoid arbitrary limits, it is
-  recognised that <a href="#hardwareLimitations">practical
+  implementors are encouraged to avoid arbitrary limits, it is
+  recognized that <a href="#hardwareLimitations">practical
   concerns</a> will likely force user agents to impose nesting
   depths.</p>
 
@@ -42000,7 +42002,7 @@
   <p>The steps below may also require that the UA insert an HTML
   element in a particular place, in which case the UA must follow the
   same steps except that it must insert or append the new node in the
-  location specified insead of appending it to the <span>current
+  location specified instead of appending it to the <span>current
   node</span>. (This happens in particular during the parsing of
   tables with invalid content.)</p>
 
@@ -42210,7 +42212,7 @@
     <span>parse error</span>. Conformance checkers may, instead of
     reporting this error, switch to a conformance checking mode for
     another language (e.g. based on the DOCTYPE token a conformance
-    checker could recognise that the document is an HTML4-era
+    checker could recognize that the document is an HTML4-era
     document, and defer to an HTML4 conformance checker.)</p>
 
     <p>Append a <code>DocumentType</code> node to the
@@ -42688,7 +42690,7 @@
      a call to <code
      title="dom-document-write-HTML">document.write()</code>:</dt>
 
-     <dd><p>Abort the processing of any nested invokations of the
+     <dd><p>Abort the processing of any nested invocations of the
      tokeniser, yielding control back to the caller. (Tokenisation
      will resume when the caller returns to the "outer" tree
      construction stage.)</p></dd>
@@ -45532,16 +45534,16 @@
 
 
 
-  <h3>Serialising HTML fragments</h3>
+  <h3>Serializing HTML fragments</h3>
 
-  <p>The following steps form the <dfn>HTML fragment serialisation
+  <p>The following steps form the <dfn>HTML fragment serialization
   algorithm</dfn>. The algorithm takes as input a DOM
   <code>Element</code> or <code>Document</code>, referred to as <var
   title="">the node</var>, and either returns a string or raises an
   exception.</p>
 
-  <p class="note">This algorithm serialises the <em>children</em> of
-  the node being serialised, not the node itself.</p>
+  <p class="note">This algorithm serializes the <em>children</em> of
+  the node being serialized, not the node itself.</p>
 
   <ol>
 
@@ -45591,7 +45593,7 @@
         <p>While the exact order of attributes is UA-defined, and may
         depend on factors such as the order that the attributes were
         given in the original markup, the sort order must be stable,
-        such that consecutive invocations of this algorithm serialise an
+        such that consecutive invocations of this algorithm serialize an
         element's attributes in the same order.</p>
 
         <p>Append a U+003E GREATER-THAN SIGN (<code title="">></code>)
@@ -45607,7 +45609,7 @@
         node at this point.</p> <!-- also, i guess: image, isindex,
         and keygen, but we don't list those because we don't consider
         those "elements", more "macros", and thus we should never
-        serialise them --> <!-- XXX when we get around to it, add
+        serialize them --> <!-- XXX when we get around to it, add
         event-source -->
 
         <p>If <var title="">current node</var> is a <code>pre</code>
@@ -45615,7 +45617,7 @@
         (LF) character.</p>
 
         <p>Append the value of running the <span>HTML fragment
-        serialisation algorithm</span> on the <var title="">current
+        serialization algorithm</span> on the <var title="">current
         node</var> element (thus recursing into this algorithm for
         that element), followed by a U+003C LESS-THAN SIGN (<code
         title=""><</code>) character, a U+002F SOLIDUS (<code
@@ -45741,11 +45743,11 @@
   parsed with an <span>HTML parser</span>, will not return the
   original tree structure. For instance, if a <code>textarea</code>
   element to which a <code title="">Comment</code> node has been
-  appended is serialised and the output is then reparsed, the comment
+  appended is serialized and the output is then reparsed, the comment
   will end up being displayed in the text field. Similarly, if, as a
   result of DOM manipulation, an element contains a comment that
   contains the literal string "<code title="">--></code>", then
-  when the result of serialising the element is parsed, the comment
+  when the result of serializing the element is parsed, the comment
   will be truncated at that point and the rest of the comment will be
   interpreted as markup. More examples would be making a
   <code>script</code> element contain a text node with the text string
@@ -46051,7 +46053,7 @@
   <code>AbstractView</code> interface. Only the default view
   implements the <code>Window</code> interface. The other views can be
   reached using the <code>view</code> attribute of the
-  <code>UIEvent</code> inteface, during event propagation. There is no
+  <code>UIEvent</code> interface, during event propagation. There is no
   way currently to enumerate all the views.</p>
 
   <!-- XXX examples! -->
@@ -46191,11 +46193,11 @@
   that can be integrated into this one. This section covers some of
   the more common requests.</p>
 
-  <h3>Localisation</h3>
+  <h3>Localization</h3>
 
-  <p>If you wish to create localised versions of an HTML application,
+  <p>If you wish to create localized versions of an HTML application,
   the best solution is to preprocess the files on the server, and then
-  use HTTP content negotation to serve the appropriate language.</p>
+  use HTTP content negotiation to serve the appropriate language.</p>
 
   <!-- <p>XXX example here</p> -->
 




More information about the Commit-Watchers mailing list