Making JSEP reference smarter.

w3c · Mar 17, 2017 · a4fe997 · a4fe997
1 parent c6f2c58
commit a4fe997
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/webrtc.html b/webrtc.html
@@ -388,11 +388,11 @@ <h4><dfn>RTCRtcpMuxPolicy</dfn> Enum</h4>
                 <td>Gather ICE candidates for both RTP and RTCP candidates. If
                 the remote-endpoint is capable of multiplexing RTCP, multiplex
                 RTCP on the RTP candidates. If it is not, use both the RTP and
-                RTCP candidates separately. Note that, as stated in [[!JSEP]],
-                Section 4.1.1, the user agent MAY not implement non-multiplexed
-                RTCP, in which case it will reject attempts to construct an
-                <a>RTCPeerConnection</a> with the <code>negotiate</code> policy.
-                </td>
+                RTCP candidates separately. Note that, as stated in <span
+                data-jsep="pc-constructor">[[!JSEP]]</span>, the user agent
+                MAY not implement non-multiplexed RTCP, in which case it will
+                reject attempts to construct an <a>RTCPeerConnection</a> with the
+                <code>negotiate</code> policy.</td>
               </tr>
               <tr>
                 <td><dfn><code>require</code></dfn></td>