[e] (0) Let's try some more explanatory text

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=21416 Affected topics: DOM APIs git-svn-id: http://svn.whatwg.org/webapps@7892 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Jun 4, 2013 · cb92db3 · cb92db3
1 parent f84eb44
commit cb92db3
Show file tree

Hide file tree

Showing 3 changed files with 44 additions and 14 deletions.
diff --git a/complete.html b/complete.html
@@ -256,7 +256,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 &mdash; Last Updated 3 June 2013</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 4 June 2013</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>
@@ -82374,10 +82374,20 @@ <h4 id=message-ports><span class=secno>10.5.3 </span>Message ports</h4>
 
    </li>
 
-   <li><p>Associate the two ports to be entangled, so that they form
-   the two parts of a new channel. (There is no
-   <code><a href=#messagechannel>MessageChannel</a></code> object that represents this
-   channel.)</li>
+   <li>
+
+    <p>Associate the two ports to be entangled, so that they form the two parts of a new channel.
+    (There is no <code><a href=#messagechannel>MessageChannel</a></code> object that represents this channel.)</p>
+
+    <p>Two ports A and B that have gone through this step are now said to be entangled; one is
+    entangled to the other, and vice versa.</p>
+
+    <p class=note>While this specification describes this process as instantaneous,
+    implementations are more likely to implement it via message passing. As with all algorithms, the
+    key is "merely" that the end result be indistinguishable, in a black-box sense, from the
+    specification.</p>
+
+   </li>
 
   </ol><p>When the user agent is to <dfn id=clone-a-port>clone a port</dfn> <var title="">original port</var>, with the clone being owned by <var title="">owner</var>, it must run the following steps, which return
   a new <code><a href=#messageport>MessagePort</a></code> object. These steps must be run

diff --git a/index b/index
@@ -256,7 +256,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 &mdash; Last Updated 3 June 2013</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 4 June 2013</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>
@@ -82374,10 +82374,20 @@ interface <dfn id=messagechannel>MessageChannel</dfn> {
 
    </li>
 
-   <li><p>Associate the two ports to be entangled, so that they form
-   the two parts of a new channel. (There is no
-   <code><a href=#messagechannel>MessageChannel</a></code> object that represents this
-   channel.)</li>
+   <li>
+
+    <p>Associate the two ports to be entangled, so that they form the two parts of a new channel.
+    (There is no <code><a href=#messagechannel>MessageChannel</a></code> object that represents this channel.)</p>
+
+    <p>Two ports A and B that have gone through this step are now said to be entangled; one is
+    entangled to the other, and vice versa.</p>
+
+    <p class=note>While this specification describes this process as instantaneous,
+    implementations are more likely to implement it via message passing. As with all algorithms, the
+    key is "merely" that the end result be indistinguishable, in a black-box sense, from the
+    specification.</p>
+
+   </li>
 
   </ol><p>When the user agent is to <dfn id=clone-a-port>clone a port</dfn> <var title="">original port</var>, with the clone being owned by <var title="">owner</var>, it must run the following steps, which return
   a new <code><a href=#messageport>MessagePort</a></code> object. These steps must be run

diff --git a/source b/source
@@ -91886,10 +91886,20 @@ interface <dfn>MessageChannel</dfn> {
 
    </li>
 
-   <li><p>Associate the two ports to be entangled, so that they form
-   the two parts of a new channel. (There is no
-   <code>MessageChannel</code> object that represents this
-   channel.)</p></li>
+   <li>
+
+    <p>Associate the two ports to be entangled, so that they form the two parts of a new channel.
+    (There is no <code>MessageChannel</code> object that represents this channel.)</p>
+
+    <p>Two ports A and B that have gone through this step are now said to be entangled; one is
+    entangled to the other, and vice versa.</p>
+
+    <p class="note">While this specification describes this process as instantaneous,
+    implementations are more likely to implement it via message passing. As with all algorithms, the
+    key is "merely" that the end result be indistinguishable, in a black-box sense, from the
+    specification.</p>
+
+   </li>
 
   </ol>