[html5] r4354 - [e] (0) Trivial typo fixes (batch edition)
whatwg at whatwg.org
whatwg at whatwg.org
Tue Oct 27 12:04:59 PDT 2009
Author: ianh
Date: 2009-10-27 12:04:55 -0700 (Tue, 27 Oct 2009)
New Revision: 4354
Modified:
complete.html
index
source
Log:
[e] (0) Trivial typo fixes (batch edition)
Modified: complete.html
===================================================================
--- complete.html 2009-10-27 18:58:06 UTC (rev 4353)
+++ complete.html 2009-10-27 19:04:55 UTC (rev 4354)
@@ -7566,7 +7566,7 @@
<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 @@
<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=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 @@
<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,7 +11758,7 @@
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>
@@ -11763,7 +11766,7 @@
<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 @@
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.
Modified: index
===================================================================
--- index 2009-10-27 18:58:06 UTC (rev 4353)
+++ index 2009-10-27 19:04:55 UTC (rev 4354)
@@ -7384,7 +7384,7 @@
<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 @@
<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 @@
<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 @@
<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,7 +11576,7 @@
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>
@@ -11581,7 +11584,7 @@
<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 @@
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.
Modified: source
===================================================================
--- source 2009-10-27 18:58:06 UTC (rev 4353)
+++ source 2009-10-27 19:04:55 UTC (rev 4354)
@@ -7451,7 +7451,7 @@
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 @@
<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 @@
<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 @@
<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 @@
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 @@
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 @@
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.
More information about the Commit-Watchers
mailing list