[html5] r1841 - [e] (0) xref typos

[whatwg at whatwg.org]

Author: ianh
Date: 2008-07-03 02:01:50 -0700 (Thu, 03 Jul 2008)
New Revision: 1841

Modified:
   index
   source
Log:
[e] (0) xref typos

Modified: index
===================================================================
--- index	2008-07-03 08:36:37 UTC (rev 1840)
+++ index	2008-07-03 09:01:50 UTC (rev 1841)
@@ -41349,8 +41349,8 @@
    title=dom-WebSocket-disconnect><code>disconnect()</code></dfn> method must
    <a href="#close1">close the Web Socket connection</a> or connection
    attempt, if any. If the connection is already closed, it must do nothing.
-   Closing the connection causes a <code
-   title=event-connection-close>close</code> event to be fired and the <code
+   Closing the connection causes a <code title=event-WebSocket-close><a
+   href="#close0">close</a></code> event to be fired and the <code
    title=dom-WebSocket-readyState><a
    href="#readystate1">readyState</a></code> attribute's value to change, as
    <a href="#closeWebSocket">described below</a>.
@@ -41409,9 +41409,9 @@
    <code><a href="#websocket0">WebSocket</a></code> object being created
    — and thus the connection being established — and the current
    script completing; or, during the execution of a <code
-   title=event-connection-read>read</code> event handler) must be buffered,
-   and those events queued up and each one individually fired after the
-   script has completed.</p>
+   title=event-WebSocket-read><a href="#read">read</a></code> event handler)
+   must be buffered, and those events queued up and each one individually
+   fired after the script has completed.</p>
   <!-- XXX make this more generic
   -->
 

Modified: source
===================================================================
--- source	2008-07-03 08:36:37 UTC (rev 1840)
+++ source	2008-07-03 09:01:50 UTC (rev 1841)
@@ -38917,7 +38917,7 @@
   method must <span>close the Web Socket connection</span> or
   connection attempt, if any. If the connection is already closed, it
   must do nothing. Closing the connection causes a <code
-  title="event-connection-close">close</code> event to be fired and
+  title="event-WebSocket-close">close</code> event to be fired and
   the <code title="dom-WebSocket-readyState">readyState</code>
   attribute's value to change, as <a href="#closeWebSocket">described
   below</a>.</p>
@@ -38975,7 +38975,7 @@
   the <code>WebSocket</code> object being created — and thus the
   connection being established — and the current script
   completing; or, during the execution of a <code
-  title="event-connection-read">read</code> event handler) must be
+  title="event-WebSocket-read">read</code> event handler) must be
   buffered, and those events queued up and each one individually fired
   after the script has completed.</p> <!-- XXX make this more generic
   -->