Sending a message through PresentationSession: editorial changes

w3c · Jun 25, 2015 · d71ce56 · d71ce56
1 parent b5b978f
commit d71ce56
Show file tree

Hide file tree

Showing 2 changed files with 20 additions and 20 deletions.
diff --git a/Overview.src.html b/Overview.src.html
@@ -648,14 +648,14 @@ <h4>
             Sending a message through <code>PresentationSession</code>
           </h4>
           <p class="note">
-            Presentation API does not mandate a specific transport for the
-            connection between the <span>controlling browsing context</span>
-            and the <span>presenting browsing context</span>, except that for
-            multiple calls to <code>send</code> it has to be ensured that
+            No specific transport for the connection between the
+            <span>controlling browsing context</span> and the <span>presenting
+            browsing context</span> is mandated, except that for multiple calls
+            to <code title="send">send()</code> it has to be ensured that
             messages are delivered to the other end reliably and in sequence.
             The transport should function equivalently to an
-            <span data-anolis-spec="webrtc">RTCDataChannel</span> in reliable
-            mode.
+            <span data-anolis-spec="webrtc"><code>RTCDataChannel</code></span>
+            in reliable mode.
           </p>
           <p>
             Let <dfn>presentation message data</dfn> be the payload data to be
@@ -682,13 +682,14 @@ <h4>
             <li>Assign the <dfn>destination browsing context</dfn> as follows:
               <ol>
                 <li>Let the the <span>destination browsing context</span> be
-                the <span>controlling browsing context</span> if
-                <span>send</span> is called in the <span>presenting browsing
+                the <span>controlling browsing context</span> if <code title=
+                "send">send()</code> is called in the <span>presenting browsing
                 context</span>.
                 </li>
                 <li>Let <span>destination browsing context</span> be the <span>
-                  presenting browsing context</span> if <span>send</span> is
-                  called from the <span>opening browsing context</span>.
+                  presenting browsing context</span> if <code title=
+                  "send">send()</code> is called from the <span>controlling
+                  browsing context</span>.
                 </li>
               </ol>
             </li>

diff --git a/index.html b/index.html
@@ -735,14 +735,14 @@ <h4 id="sending-a-message-through-presentationsession"><span class="secno">6.2.1
             Sending a message through <a href="#presentationsession"><code>PresentationSession</code></a>
           </h4>
           <p class="note">
-            Presentation API does not mandate a specific transport for the
-            connection between the <a href="#controlling-browsing-context">controlling browsing context</a>
-            and the <a href="#presenting-browsing-context">presenting browsing context</a>, except that for
-            multiple calls to <a href="#send"><code>send</code></a> it has to be ensured that
+            No specific transport for the connection between the
+            <a href="#controlling-browsing-context">controlling browsing context</a> and the <a href="#presenting-browsing-context">presenting
+            browsing context</a> is mandated, except that for multiple calls
+            to <a href="#send"><code title="send">send()</code></a> it has to be ensured that
             messages are delivered to the other end reliably and in sequence.
             The transport should function equivalently to an
-            <a class="external" data-anolis-spec="webrtc" href="http://w3c.github.io/webrtc-pc/#idl-def-RTCDataChannel">RTCDataChannel</a> in reliable
-            mode.
+            <a class="external" data-anolis-spec="webrtc" href="http://w3c.github.io/webrtc-pc/#idl-def-RTCDataChannel"><code>RTCDataChannel</code></a>
+            in reliable mode.
           </p>
           <p>
             Let <dfn id="presentation-message-data">presentation message data</dfn> be the payload data to be
@@ -769,13 +769,12 @@ <h4 id="sending-a-message-through-presentationsession"><span class="secno">6.2.1
             <li>Assign the <dfn id="destination-browsing-context">destination browsing context</dfn> as follows:
               <ol>
                 <li>Let the the <a href="#destination-browsing-context">destination browsing context</a> be
-                the <a href="#controlling-browsing-context">controlling browsing context</a> if
-                <a href="#send">send</a> is called in the <a href="#presenting-browsing-context">presenting browsing
+                the <a href="#controlling-browsing-context">controlling browsing context</a> if <a href="#send"><code title="send">send()</code></a> is called in the <a href="#presenting-browsing-context">presenting browsing
                 context</a>.
                 </li>
                 <li>Let <a href="#destination-browsing-context">destination browsing context</a> be the <a href="#presenting-browsing-context">
-                  presenting browsing context</a> if <a href="#send">send</a> is
-                  called from the <span>opening browsing context</span>.
+                  presenting browsing context</a> if <a href="#send"><code title="send">send()</code></a> is called from the <a href="#controlling-browsing-context">controlling
+                  browsing context</a>.
                 </li>
               </ol>
             </li>