[e] (0) more typos and clarifications

git-svn-id: http://svn.whatwg.org/webapps@5269 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Aug 10, 2010 · f2e7c6a · f2e7c6a
1 parent 4303989
commit f2e7c6a
Show file tree

Hide file tree

Showing 3 changed files with 28 additions and 27 deletions.
diff --git a/complete.html b/complete.html
@@ -44628,7 +44628,7 @@ <h4 id=association-of-controls-and-forms><span class=secno>4.10.18 </span>Associ
    outer form "a".</p>
 
    <p>This happens as follows: First, the "e" node gets associated
-   with "c" in the <a href=#html-parser>HTML parser</a>. Theh, the <code title=dom-innerHTML><a href=#dom-innerhtml>innerHTML</a></code> algorithm moves the nodes
+   with "c" in the <a href=#html-parser>HTML parser</a>. Then, the <code title=dom-innerHTML><a href=#dom-innerhtml>innerHTML</a></code> algorithm moves the nodes
    from the temporary document to the "b" element. At this point, the
    nodes see their ancestor chain change, and thus all the "magic"
    associations done by the parser are reset to normal ancestor
@@ -77903,13 +77903,12 @@ <h5 id=cdata-rcdata-restrictions><span class=secno>12.1.2.6 </span>Restrictions
   <h4 id=text-1><span class=secno>12.1.3 </span>Text</h4>
 
   <p><dfn id=syntax-text title=syntax-text>Text</dfn> is allowed inside elements,
-  attributes, and comments. Text must consist of Unicode characters.
-  Text must not contain U+0000 characters. Text must not contain
-  permanently undefined Unicode characters (noncharacters). Text must
-  not contain control characters other than <a href=#space-character title="space
-  character">space characters</a>. Extra constraints are placed on
-  what is and what is not allowed in text based on where the text is
-  to be put, as described in the other sections.</p>
+  attribute values, and comments. Text must consist of Unicode
+  characters. Text must not contain U+0000 characters. Text must not
+  contain permanently undefined Unicode characters (noncharacters).
+  Text must not contain control characters other than <a href=#space-character title="space character">space characters</a>. Extra constraints
+  are placed on what is and what is not allowed in text based on where
+  the text is to be put, as described in the other sections.</p>
 
 
   <h5 id=newlines><span class=secno>12.1.3.1 </span>Newlines</h5>
@@ -78119,7 +78118,8 @@ <h4 id=overview-of-the-parsing-model><span class=secno>12.2.1 </span>Overview of
 
   <p>In the common case, the data handled by the tokenization stage
   comes from the network, but <a href=#dynamic-markup-insertion title="dynamic markup
-  insertion">it can also come from script</a>, e.g. using the <code title=dom-document-write><a href=#dom-document-write>document.write()</a></code> API.</p>
+  insertion">it can also come from script</a> running in the user
+  agent, e.g. using the <code title=dom-document-write><a href=#dom-document-write>document.write()</a></code> API.</p>
 
   <p><img alt="" src=images/parsing-model-overview.png></p>
 

diff --git a/index b/index
@@ -44555,7 +44555,7 @@ out of 233&thinsp;257&thinsp;824 bytes available&lt;/meter&gt;&lt;/p&gt;</pre>
    outer form "a".</p>
 
    <p>This happens as follows: First, the "e" node gets associated
-   with "c" in the <a href=#html-parser>HTML parser</a>. Theh, the <code title=dom-innerHTML><a href=#dom-innerhtml>innerHTML</a></code> algorithm moves the nodes
+   with "c" in the <a href=#html-parser>HTML parser</a>. Then, the <code title=dom-innerHTML><a href=#dom-innerhtml>innerHTML</a></code> algorithm moves the nodes
    from the temporary document to the "b" element. At this point, the
    nodes see their ancestor chain change, and thus all the "magic"
    associations done by the parser are reset to normal ancestor
@@ -71013,13 +71013,12 @@ interface <dfn id=messageport>MessagePort</dfn> {
   <h4 id=text-1><span class=secno>10.1.3 </span>Text</h4>
 
   <p><dfn id=syntax-text title=syntax-text>Text</dfn> is allowed inside elements,
-  attributes, and comments. Text must consist of Unicode characters.
-  Text must not contain U+0000 characters. Text must not contain
-  permanently undefined Unicode characters (noncharacters). Text must
-  not contain control characters other than <a href=#space-character title="space
-  character">space characters</a>. Extra constraints are placed on
-  what is and what is not allowed in text based on where the text is
-  to be put, as described in the other sections.</p>
+  attribute values, and comments. Text must consist of Unicode
+  characters. Text must not contain U+0000 characters. Text must not
+  contain permanently undefined Unicode characters (noncharacters).
+  Text must not contain control characters other than <a href=#space-character title="space character">space characters</a>. Extra constraints
+  are placed on what is and what is not allowed in text based on where
+  the text is to be put, as described in the other sections.</p>
 
 
   <h5 id=newlines><span class=secno>10.1.3.1 </span>Newlines</h5>
@@ -71229,7 +71228,8 @@ interface <dfn id=messageport>MessagePort</dfn> {
 
   <p>In the common case, the data handled by the tokenization stage
   comes from the network, but <a href=#dynamic-markup-insertion title="dynamic markup
-  insertion">it can also come from script</a>, e.g. using the <code title=dom-document-write><a href=#dom-document-write>document.write()</a></code> API.</p>
+  insertion">it can also come from script</a> running in the user
+  agent, e.g. using the <code title=dom-document-write><a href=#dom-document-write>document.write()</a></code> API.</p>
 
   <p><img alt="" src=images/parsing-model-overview.png></p>
 

diff --git a/source b/source
@@ -49960,7 +49960,7 @@ out of 233&#x2009;257&#x2009;824 bytes available&lt;/meter>&lt;/p></pre>
    outer form "a".</p>
 
    <p>This happens as follows: First, the "e" node gets associated
-   with "c" in the <span>HTML parser</span>. Theh, the <code
+   with "c" in the <span>HTML parser</span>. Then, the <code
    title="dom-innerHTML">innerHTML</code> algorithm moves the nodes
    from the temporary document to the "b" element. At this point, the
    nodes see their ancestor chain change, and thus all the "magic"
@@ -88897,13 +88897,13 @@ interface <dfn>SQLTransactionSync</dfn> {
   <h4>Text</h4>
 
   <p><dfn title="syntax-text">Text</dfn> is allowed inside elements,
-  attributes, and comments. Text must consist of Unicode characters.
-  Text must not contain U+0000 characters. Text must not contain
-  permanently undefined Unicode characters (noncharacters). Text must
-  not contain control characters other than <span title="space
-  character">space characters</span>. Extra constraints are placed on
-  what is and what is not allowed in text based on where the text is
-  to be put, as described in the other sections.</p>
+  attribute values, and comments. Text must consist of Unicode
+  characters. Text must not contain U+0000 characters. Text must not
+  contain permanently undefined Unicode characters (noncharacters).
+  Text must not contain control characters other than <span
+  title="space character">space characters</span>. Extra constraints
+  are placed on what is and what is not allowed in text based on where
+  the text is to be put, as described in the other sections.</p>
 
 
   <h5>Newlines</h5>
@@ -89122,7 +89122,8 @@ interface <dfn>SQLTransactionSync</dfn> {
 
   <p>In the common case, the data handled by the tokenization stage
   comes from the network, but <span title="dynamic markup
-  insertion">it can also come from script</span>, e.g. using the <code
+  insertion">it can also come from script</span> running in the user
+  agent, e.g. using the <code
   title="dom-document-write">document.write()</code> API.</p>
 
   <p><img src="images/parsing-model-overview.png" alt=""></p>