[e] (0) Trivial typo fixes (batch edition)

git-svn-id: http://svn.whatwg.org/webapps@4354 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

@@ -7566,7 +7566,7 @@ <h4 id=creating-documents><span class=secno>3.1.5 </span>Creating documents</h4>
   <p><a href=#html-documents>HTML documents</a> can be created using the <code title=dom-DOMHTMLImplementation-createHTMLDocument><a href=#dom-domhtmlimplementation-createhtmldocument>createHTMLDocument()</a></code>
   method:</p>
 
-  <pre>[Supplemental, NoInterfaceObject]
+  <pre class=idl>[Supplemental, NoInterfaceObject]
 interface <dfn id=domhtmlimplementation>DOMHTMLImplementation</dfn> {
   <span>Document</span> <a href=#dom-domhtmlimplementation-createhtmldocument title=dom-DOMHTMLImplementation-createHTMLDocument>createHTMLDocument</a>(in DOMString title);
 };
@@ -9660,11 +9660,14 @@ <h3 id=interactions-with-xpath-and-xslt><span class=secno>3.4 </span>Interaction
 
    <p>A QName in the node test is expanded into an expanded-name using
    the namespace declarations from the expression context. If the
-   QName has a prefix, then there must be namespace declaration for
-   this prefix in the expression context, and the correponding
-   namespace URI is the one that is associated with this prefix.  It
-   is an error if the QName has a prefix for which there is no
-   namespace declaration in the expression context. </p>
+   QName has a prefix, then there must be a<!-- added 2009-10-27 -
+   http://www.w3.org/Bugs/Public/show_bug.cgi?id=8062 --> namespace
+   declaration for this prefix in the expression context, and the
+   corresponding<!-- typo fixed 2009-10-27 -
+   http://www.w3.org/Bugs/Public/show_bug.cgi?id=8063 --> namespace
+   URI is the one that is associated with this prefix.  It is an error
+   if the QName has a prefix for which there is no namespace
+   declaration in the expression context. </p>
 
    <p>If the QName has no prefix and the principal node type of the
    axis is element, then the default element namespace is
@@ -9724,7 +9727,7 @@ <h3 id=interactions-with-xpath-and-xslt><span class=secno>3.4 </span>Interaction
   <h3 id=dynamic-markup-insertion><span class=secno>3.5 </span><dfn>Dynamic markup insertion</dfn></h3>
 
   <p class=note>APIs for dynamically inserting markup into the
-  document interact with the parser, and thus their behavior, varies
+  document interact with the parser, and thus their behavior varies
   depending on whether they are used with <a href=#html-documents>HTML documents</a>
   (and the <a href=#html-parser>HTML parser</a>) or XHTML in <a href=#xml-documents>XML
   documents</a> (and the <a href=#xml-parser>XML parser</a>).</p>
@@ -10326,7 +10329,7 @@ <h4 id=insertadjacenthtml()><span class=secno>3.5.7 </span><code title=dom-inser
 
    <dd>
 
-    <p>Parsed the given string <var title="">text</var> as HTML or XML
+    <p>Parses the given string <var title="">text</var> as HTML or XML
     and inserts the resulting nodes into the tree in the position
     given by the <var title="">position</var> argument, as
     follows:</p>
@@ -11755,15 +11758,15 @@ <h5 id=other-pragma-directives><span class=secno>4.2.5.4 </span>Other pragma dir
   conditions, be registered in the <a href=http://wiki.whatwg.org/wiki/PragmaExtensions>WHATWG Wiki
   PragmaExtensions page</a>. <a href=#refsWHATWGWIKI>[WHATWGWIKI]</a></p>
 
-  <p>Such extensions must use a name that is identical to a HTTP
+  <p>Such extensions must use a name that is identical to an HTTP
   header registered in the Permanent Message Header Field Registry,
   and must have behavior identical to that described for the HTTP
   header. <a href=#refsIANAPERMHEADERS>[IANAPERMHEADERS]</a></p>
 
   <p>Pragma directives corresponding to headers describing metadata,
   or not requiring specific user agent processing, must not be
   registered; instead, use <a href=#concept-meta-extensions title=concept-meta-extensions>metadata names</a>. Pragma
-  directions corresponding to headers that affect the HTTP processing
+  directives corresponding to headers that affect the HTTP processing
   model (e.g. caching) must not be registered, as they would result in
   HTTP-level behavior being different for user agents that implement
   HTML than for user agents that do not.</p>
@@ -11885,7 +11888,7 @@ <h5 id=charset><span class=secno>4.2.5.5 </span>Specifying the document's charac
   handling of ASCII "~" -->, encodings based on ISO-2022<!--
   http://krijnhoetmer.nl/irc-logs/whatwg/20090628#l-422 and
   http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-October/023797.html
-  -->, and encodings based on EBCDIC. Furtermore, authors must not use
+  -->, and encodings based on EBCDIC. Furthermore, authors must not use
   the CESU-8, UTF-7, BOCU-1 and SCSU encodings, which also fall into
   this category, because these encodings were never intended for use
   for Web content.

index

@@ -7384,7 +7384,7 @@ interface <dfn id=htmldocument>HTMLDocument</dfn> {
   <p><a href=#html-documents>HTML documents</a> can be created using the <code title=dom-DOMHTMLImplementation-createHTMLDocument><a href=#dom-domhtmlimplementation-createhtmldocument>createHTMLDocument()</a></code>
   method:</p>
 
-  <pre>[Supplemental, NoInterfaceObject]
+  <pre class=idl>[Supplemental, NoInterfaceObject]
 interface <dfn id=domhtmlimplementation>DOMHTMLImplementation</dfn> {
   <span>Document</span> <a href=#dom-domhtmlimplementation-createhtmldocument title=dom-DOMHTMLImplementation-createHTMLDocument>createHTMLDocument</a>(in DOMString title);
 };
@@ -9478,11 +9478,14 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
 
    <p>A QName in the node test is expanded into an expanded-name using
    the namespace declarations from the expression context. If the
-   QName has a prefix, then there must be namespace declaration for
-   this prefix in the expression context, and the correponding
-   namespace URI is the one that is associated with this prefix.  It
-   is an error if the QName has a prefix for which there is no
-   namespace declaration in the expression context. </p>
+   QName has a prefix, then there must be a<!-- added 2009-10-27 -
+   http://www.w3.org/Bugs/Public/show_bug.cgi?id=8062 --> namespace
+   declaration for this prefix in the expression context, and the
+   corresponding<!-- typo fixed 2009-10-27 -
+   http://www.w3.org/Bugs/Public/show_bug.cgi?id=8063 --> namespace
+   URI is the one that is associated with this prefix.  It is an error
+   if the QName has a prefix for which there is no namespace
+   declaration in the expression context. </p>
 
    <p>If the QName has no prefix and the principal node type of the
    axis is element, then the default element namespace is
@@ -9542,7 +9545,7 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
   <h3 id=dynamic-markup-insertion><span class=secno>3.5 </span><dfn>Dynamic markup insertion</dfn></h3>
 
   <p class=note>APIs for dynamically inserting markup into the
-  document interact with the parser, and thus their behavior, varies
+  document interact with the parser, and thus their behavior varies
   depending on whether they are used with <a href=#html-documents>HTML documents</a>
   (and the <a href=#html-parser>HTML parser</a>) or XHTML in <a href=#xml-documents>XML
   documents</a> (and the <a href=#xml-parser>XML parser</a>).</p>
@@ -10144,7 +10147,7 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
 
    <dd>
 
-    <p>Parsed the given string <var title="">text</var> as HTML or XML
+    <p>Parses the given string <var title="">text</var> as HTML or XML
     and inserts the resulting nodes into the tree in the position
     given by the <var title="">position</var> argument, as
     follows:</p>
@@ -11573,15 +11576,15 @@ people expect to have work and what is necessary.
   conditions, be registered in the <a href=http://wiki.whatwg.org/wiki/PragmaExtensions>WHATWG Wiki
   PragmaExtensions page</a>. <a href=#refsWHATWGWIKI>[WHATWGWIKI]</a></p>
 
-  <p>Such extensions must use a name that is identical to a HTTP
+  <p>Such extensions must use a name that is identical to an HTTP
   header registered in the Permanent Message Header Field Registry,
   and must have behavior identical to that described for the HTTP
   header. <a href=#refsIANAPERMHEADERS>[IANAPERMHEADERS]</a></p>
 
   <p>Pragma directives corresponding to headers describing metadata,
   or not requiring specific user agent processing, must not be
   registered; instead, use <a href=#concept-meta-extensions title=concept-meta-extensions>metadata names</a>. Pragma
-  directions corresponding to headers that affect the HTTP processing
+  directives corresponding to headers that affect the HTTP processing
   model (e.g. caching) must not be registered, as they would result in
   HTTP-level behavior being different for user agents that implement
   HTML than for user agents that do not.</p>
@@ -11703,7 +11706,7 @@ people expect to have work and what is necessary.
   handling of ASCII "~" -->, encodings based on ISO-2022<!--
   http://krijnhoetmer.nl/irc-logs/whatwg/20090628#l-422 and
   http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-October/023797.html
-  -->, and encodings based on EBCDIC. Furtermore, authors must not use
+  -->, and encodings based on EBCDIC. Furthermore, authors must not use
   the CESU-8, UTF-7, BOCU-1 and SCSU encodings, which also fall into
   this category, because these encodings were never intended for use
   for Web content.

source

@@ -7451,7 +7451,7 @@ interface <dfn>HTMLDocument</dfn> {
   title="dom-DOMHTMLImplementation-createHTMLDocument">createHTMLDocument()</code>
   method:</p>
 
-  <pre>[Supplemental, NoInterfaceObject]
+  <pre class="idl">[Supplemental, NoInterfaceObject]
 interface <dfn>DOMHTMLImplementation</dfn> {
   <span>Document</span> <span title="dom-DOMHTMLImplementation-createHTMLDocument">createHTMLDocument</span>(in DOMString title);
 };
@@ -9828,11 +9828,14 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
 
    <p>A QName in the node test is expanded into an expanded-name using
    the namespace declarations from the expression context. If the
-   QName has a prefix, then there must be namespace declaration for
-   this prefix in the expression context, and the correponding
-   namespace URI is the one that is associated with this prefix.  It
-   is an error if the QName has a prefix for which there is no
-   namespace declaration in the expression context. </p>
+   QName has a prefix, then there must be a<!-- added 2009-10-27 -
+   http://www.w3.org/Bugs/Public/show_bug.cgi?id=8062 --> namespace
+   declaration for this prefix in the expression context, and the
+   corresponding<!-- typo fixed 2009-10-27 -
+   http://www.w3.org/Bugs/Public/show_bug.cgi?id=8063 --> namespace
+   URI is the one that is associated with this prefix.  It is an error
+   if the QName has a prefix for which there is no namespace
+   declaration in the expression context. </p>
 
    <p>If the QName has no prefix and the principal node type of the
    axis is element, then the default element namespace is
@@ -9899,7 +9902,7 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
   <h3><dfn>Dynamic markup insertion</dfn></h3>
 
   <p class="note">APIs for dynamically inserting markup into the
-  document interact with the parser, and thus their behavior, varies
+  document interact with the parser, and thus their behavior varies
   depending on whether they are used with <span>HTML documents</span>
   (and the <span>HTML parser</span>) or XHTML in <span>XML
   documents</span> (and the <span>XML parser</span>).</p>
@@ -10582,7 +10585,7 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
 
    <dd>
 
-    <p>Parsed the given string <var title="">text</var> as HTML or XML
+    <p>Parses the given string <var title="">text</var> as HTML or XML
     and inserts the resulting nodes into the tree in the position
     given by the <var title="">position</var> argument, as
     follows:</p>
@@ -12229,7 +12232,7 @@ people expect to have work and what is necessary.
   PragmaExtensions page</a>. <a
   href="#refsWHATWGWIKI">[WHATWGWIKI]</a></p>
 
-  <p>Such extensions must use a name that is identical to a HTTP
+  <p>Such extensions must use a name that is identical to an HTTP
   header registered in the Permanent Message Header Field Registry,
   and must have behavior identical to that described for the HTTP
   header. <a href="#refsIANAPERMHEADERS">[IANAPERMHEADERS]</a></p>
@@ -12238,7 +12241,7 @@ people expect to have work and what is necessary.
   or not requiring specific user agent processing, must not be
   registered; instead, use <span
   title="concept-meta-extensions">metadata names</span>. Pragma
-  directions corresponding to headers that affect the HTTP processing
+  directives corresponding to headers that affect the HTTP processing
   model (e.g. caching) must not be registered, as they would result in
   HTTP-level behavior being different for user agents that implement
   HTML than for user agents that do not.</p>
@@ -12374,7 +12377,7 @@ people expect to have work and what is necessary.
   handling of ASCII "~" -->, encodings based on ISO-2022<!--
   http://krijnhoetmer.nl/irc-logs/whatwg/20090628#l-422 and
   http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-October/023797.html
-  -->, and encodings based on EBCDIC. Furtermore, authors must not use
+  -->, and encodings based on EBCDIC. Furthermore, authors must not use
   the CESU-8, UTF-7, BOCU-1 and SCSU encodings, which also fall into
   this category, because these encodings were never intended for use
   for Web content.