[html5] r7449 - [e] (0) Fix some typos or copypasta. Affected topics: Server-Sent Events

[whatwg at whatwg.org]

Author: ianh
Date: 2012-10-10 15:12:37 -0700 (Wed, 10 Oct 2012)
New Revision: 7449

Modified:
   complete.html
   index
   source
Log:
[e] (0) Fix some typos or copypasta.
Affected topics: Server-Sent Events

Modified: complete.html
===================================================================
--- complete.html	2012-10-10 20:14:40 UTC (rev 7448)
+++ complete.html	2012-10-10 22:12:37 UTC (rev 7449)
@@ -249,7 +249,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 9 October 2012</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 10 October 2012</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -84066,18 +84066,16 @@
 
   <p>The default event type is "message".</p>
 
-  <hr><p>Event streams requests can be redirected using HTTP 301 and 307
-  redirects as with normal HTTP requests. Clients will reconnect if
-  the connection is closed; a client can be told to stop reconnecting
-  using the HTTP 204 No Content response code.</p>
+  <hr><p>Event stream requests can be redirected using HTTP 301 and 307 redirects as with normal HTTP
+  requests. Clients will reconnect if the connection is closed; a client can be told to stop
+  reconnecting using the HTTP 204 No Content response code.</p>
 
-  <p>Using this API rather than emulating it using
-  <code>XMLHttpRequest</code> or an <code><a href=#the-iframe-element>iframe</a></code> allows the
-  user agent to make better use of network resources in cases where
-  the user agent implementor and the network operator are able to
-  coordinate in advance. Amongst other benefits, this can result in
-  significant savings in battery life on portable devices. This is
-  discussed further in the section below on <a href=#eventsource-push>connectionless push</a>.</p>
+  <p>Using this API rather than emulating it using <code>XMLHttpRequest</code> or an
+  <code><a href=#the-iframe-element>iframe</a></code> allows the user agent to make better use of network resources in cases where
+  the user agent implementor and the network operator are able to coordinate in advance. Amongst
+  other benefits, this can result in significant savings in battery life on portable devices. This
+  is discussed further in the section below on <a href=#eventsource-push>connectionless
+  push</a>.</p>
 
 
   <h4 id=the-eventsource-interface><span class=secno>10.2.2 </span>The <code><a href=#eventsource>EventSource</a></code> interface</h4>

Modified: index
===================================================================
--- index	2012-10-10 20:14:40 UTC (rev 7448)
+++ index	2012-10-10 22:12:37 UTC (rev 7449)
@@ -249,7 +249,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 9 October 2012</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 10 October 2012</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -84066,18 +84066,16 @@
 
   <p>The default event type is "message".</p>
 
-  <hr><p>Event streams requests can be redirected using HTTP 301 and 307
-  redirects as with normal HTTP requests. Clients will reconnect if
-  the connection is closed; a client can be told to stop reconnecting
-  using the HTTP 204 No Content response code.</p>
+  <hr><p>Event stream requests can be redirected using HTTP 301 and 307 redirects as with normal HTTP
+  requests. Clients will reconnect if the connection is closed; a client can be told to stop
+  reconnecting using the HTTP 204 No Content response code.</p>
 
-  <p>Using this API rather than emulating it using
-  <code>XMLHttpRequest</code> or an <code><a href=#the-iframe-element>iframe</a></code> allows the
-  user agent to make better use of network resources in cases where
-  the user agent implementor and the network operator are able to
-  coordinate in advance. Amongst other benefits, this can result in
-  significant savings in battery life on portable devices. This is
-  discussed further in the section below on <a href=#eventsource-push>connectionless push</a>.</p>
+  <p>Using this API rather than emulating it using <code>XMLHttpRequest</code> or an
+  <code><a href=#the-iframe-element>iframe</a></code> allows the user agent to make better use of network resources in cases where
+  the user agent implementor and the network operator are able to coordinate in advance. Amongst
+  other benefits, this can result in significant savings in battery life on portable devices. This
+  is discussed further in the section below on <a href=#eventsource-push>connectionless
+  push</a>.</p>
 
 
   <h4 id=the-eventsource-interface><span class=secno>10.2.2 </span>The <code><a href=#eventsource>EventSource</a></code> interface</h4>

Modified: source
===================================================================
--- source	2012-10-10 20:14:40 UTC (rev 7448)
+++ source	2012-10-10 22:12:37 UTC (rev 7449)
@@ -97654,19 +97654,16 @@
 
   <hr>
 
-  <p>Event streams requests can be redirected using HTTP 301 and 307
-  redirects as with normal HTTP requests. Clients will reconnect if
-  the connection is closed; a client can be told to stop reconnecting
-  using the HTTP 204 No Content response code.</p>
+  <p>Event stream requests can be redirected using HTTP 301 and 307 redirects as with normal HTTP
+  requests. Clients will reconnect if the connection is closed; a client can be told to stop
+  reconnecting using the HTTP 204 No Content response code.</p>
 
-  <p>Using this API rather than emulating it using
-  <code>XMLHttpRequest</code> or an <code>iframe</code> allows the
-  user agent to make better use of network resources in cases where
-  the user agent implementor and the network operator are able to
-  coordinate in advance. Amongst other benefits, this can result in
-  significant savings in battery life on portable devices. This is
-  discussed further in the section below on <a
-  href="#eventsource-push">connectionless push</a>.</p>
+  <p>Using this API rather than emulating it using <code>XMLHttpRequest</code> or an
+  <code>iframe</code> allows the user agent to make better use of network resources in cases where
+  the user agent implementor and the network operator are able to coordinate in advance. Amongst
+  other benefits, this can result in significant savings in battery life on portable devices. This
+  is discussed further in the section below on <a href="#eventsource-push">connectionless
+  push</a>.</p>
 
 <!--END complete-->
   <!--BOILERPLATE middle-w3c-api-intro-->