[html5] r4385 - [e] (0) Minor clarifications

[whatwg at whatwg.org]

Author: ianh
Date: 2009-11-30 22:47:52 -0800 (Mon, 30 Nov 2009)
New Revision: 4385

Modified:
   complete.html
   source
Log:
[e] (0) Minor clarifications

Modified: complete.html
===================================================================
--- complete.html	2009-12-01 02:13:42 UTC (rev 4384)
+++ complete.html	2009-12-01 06:47:52 UTC (rev 4385)
@@ -110,7 +110,7 @@
 
   <header class=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
    <hgroup><h1>Web Applications 1.0</h1>
-    <h2 class="no-num no-toc">Draft Standard — 26 November 2009</h2>
+    <h2 class="no-num no-toc">Draft Standard — 1 December 2009</h2>
    </hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -64232,8 +64232,9 @@
       prematurely aborted by the "<a href=#kill-a-worker>kill a worker</a>" or
       "<a href=#terminate-a-worker>terminate a worker</a>" algorithms defined above.</p>
 
-      <p>If it failed to parse, then throw a <code>SyntaxError</code>
-      exception and abort all these steps.</p>
+      <p>If it failed to parse, then throw an ECMAScript
+      <code>SyntaxError</code> exception and abort all these
+      steps. <a href=#refsECMA262>[ECMA262]</a></p>
 
       <p>If an exception was raised or if the script was prematurely
       aborted, then abort all these steps, letting the exception or
@@ -65052,9 +65053,9 @@
   unless the rate of messages is high enough for this not to
   matter.</p> <!-- v2 can we get a better solution? -->
 
-  <p>Implementations that support HTTP's per-server connection
-  limitation might run into trouble when opening multiple pages from a
-  site if each page has an <code><a href=#eventsource>EventSource</a></code> to the same
+  <p>Clients that support HTTP's per-server connection limitation
+  might run into trouble when opening multiple pages from a site if
+  each page has an <code><a href=#eventsource>EventSource</a></code> to the same
   domain. Authors can avoid this using the relatively complex
   mechanism of using unique domain names per connection, or by
   allowing the user to enable or disable the <code><a href=#eventsource>EventSource</a></code>

Modified: source
===================================================================
--- source	2009-12-01 02:13:42 UTC (rev 4384)
+++ source	2009-12-01 06:47:52 UTC (rev 4385)
@@ -73221,8 +73221,9 @@
       prematurely aborted by the "<span>kill a worker</span>" or
       "<span>terminate a worker</span>" algorithms defined above.</p>
 
-      <p>If it failed to parse, then throw a <code>SyntaxError</code>
-      exception and abort all these steps.</p>
+      <p>If it failed to parse, then throw an ECMAScript
+      <code>SyntaxError</code> exception and abort all these
+      steps. <a href="#refsECMA262">[ECMA262]</a></p>
 
       <p>If an exception was raised or if the script was prematurely
       aborted, then abort all these steps, letting the exception or
@@ -74159,9 +74160,9 @@
   unless the rate of messages is high enough for this not to
   matter.</p> <!-- v2 can we get a better solution? -->
 
-  <p>Implementations that support HTTP's per-server connection
-  limitation might run into trouble when opening multiple pages from a
-  site if each page has an <code>EventSource</code> to the same
+  <p>Clients that support HTTP's per-server connection limitation
+  might run into trouble when opening multiple pages from a site if
+  each page has an <code>EventSource</code> to the same
   domain. Authors can avoid this using the relatively complex
   mechanism of using unique domain names per connection, or by
   allowing the user to enable or disable the <code>EventSource</code>