CVS html5/websockets

Update of /sources/public/html5/websockets
In directory roscoe:/tmp/cvs-serv26611

Modified Files:
	Overview.html 
Log Message:
The giant clean-up of 2013. Improved internal consistency, adjusted section order to make more sense, started a move away from abusing title='' for cross-references, fixed minor typos, cleaned up some dangling TODOs, very minor typo fixes, dropped some obsolete comments, un-commented-out minor things that had previously been commented out for reasons that no longer apply, etc. No normative changes. (whatwg r8229)

--- /sources/public/html5/websockets/Overview.html	2013/07/26 17:57:15	1.300
+++ /sources/public/html5/websockets/Overview.html	2013/10/18 06:28:15	1.301
@@ -216,7 +216,7 @@
 
    <h1>The WebSocket API</h1>
    
-   <h2 class="no-num no-toc" id="editor-s-draft-26-july-2013">Editor's Draft 26 July 2013</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-18-october-2013">Editor's Draft 18 October 2013</h2>
    <dl><dt>Latest Published Version:</dt>
     <dd><a href="http://www.w3.org/TR/websockets/">http://www.w3.org/TR/websockets/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -350,7 +350,7 @@
   </dl><p>The W3C <a href="http://www.w3.org/2008/webapps/">Web Applications
   Working Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation track.
-  This specification is the 26 July 2013 Editor's Draft.
+  This specification is the 18 October 2013 Editor's Draft.
   </p>
 
 
@@ -402,14 +402,12 @@
 
   <p><i>This section is non-normative.</i></p>
 
-  <p>To enable Web applications to maintain bidirectional
-  communications with server-side processes, this specification
-  introduces the <code><a href="#websocket">WebSocket</a></code> interface.</p>
-
-  <p class="note">This interface does not allow for raw access to the
-  underlying network. For example, this interface could not be used to
-  implement an IRC client without proxying messages through a custom
-  server.</p>
+  <p>To enable Web applications to maintain bidirectional communications with server-side processes,
+  this specification introduces the <code><a href="#websocket">WebSocket</a></code> interface.</p>
+
+  <p class="note">This interface does not allow for raw access to the underlying network. For
+  example, this interface could not be used to implement an IRC client without proxying messages
+  through a custom server.</p>
 
 
   
@@ -539,7 +537,7 @@
   equivalent to the empty array. Each string in the array is a subprotocol name. The connection will
   only be established if the server reports that it has selected one of these subprotocols. The
   subprotocol names must all be strings that match the requirements for elements that comprise the
-  value of <code title="http-sec-websocket-protocol">Sec-WebSocket-Protocol</code> header fields as
+  value of <code title="http-sec-websocket-protocol">Sec-WebSocket-Protocol</code> fields as
   defined by the WebSocket protocol specification. <a href="#refsWSP">[WSP]</a></p>
 
   <p>When the <code>WebSocket()</code> constructor is invoked, the UA must run these steps:</p>
@@ -576,7 +574,7 @@
    </li>
 
    <li><p>If any of the values in <var title="">protocols</var> occur more than once or otherwise
-   fail to match the requirements for elements that comprise the value of <code title="http-sec-websocket-protocol">Sec-WebSocket-Protocol</code> header fields as defined by the
+   fail to match the requirements for elements that comprise the value of <code title="http-sec-websocket-protocol">Sec-WebSocket-Protocol</code> fields as defined by the
    WebSocket protocol specification, then throw a <code>SyntaxError</code> exception and abort these
    steps. <a href="#refsWSP">[WSP]</a></li>
 
@@ -1153,8 +1151,8 @@
   when a <code>Document</code> object goes away), the user agent must follow the first appropriate
   set of steps from the following list:</p>
 
-  <dl class="switch"><dt>If the WebSocket connection is not yet <i title="the WebSocket
-   connection is established">established</i> <a href="#refsWSP">[WSP]</a></dt>
+  <dl class="switch"><dt>If the WebSocket connection is not yet <i title="the WebSocket connection is
+   established">established</i> <a href="#refsWSP">[WSP]</a></dt>
 
    <dd>
 
@@ -1163,14 +1161,13 @@
    </dd>
 
 
-   <dt>If the WebSocket closing handshake has not yet been <i title="the WebSocket closing handshake is started">started</i>
-   <a href="#refsWSP">[WSP]</a></dt>
+   <dt>If the WebSocket closing handshake has not yet been <i title="the WebSocket closing handshake
+   is started">started</i> <a href="#refsWSP">[WSP]</a></dt>
 
    <dd>
 
-    <p><i>Start the WebSocket closing handshake</i>, with the
-    status code<!--CLOSE CODE--> to use in the WebSocket Close message
-    being 1001. <a href="#refsWSP">[WSP]</a></p>
+    <p><i>Start the WebSocket closing handshake</i>, with the status code<!--CLOSE CODE--> to use in
+    the WebSocket Close message being 1001. <a href="#refsWSP">[WSP]</a></p>
 
    </dd>

Received on Friday, 18 October 2013 06:28:16 UTC