Update post-Rec status of the document

webrtc.html

@@ -46,47 +46,14 @@
       </p>
     </section>
     <section id="sotd" class="updateable-rec">
-      <p>
-        The API is based on preliminary work done in the WHATWG.
-      </p>
-      <p>
-        The specification is feature complete and is expected to be stable with
-        no further substantive change. Since the <a href=
-        "https://www.w3.org/TR/2019/CR-webrtc-20191213/">previous Candidate
-        Recommendation</a>, the following substantive changes have been brought
-        to the specification:
-      </p>
-      <ul>
-        <li>the specification allows administrative prohibiting of ICE
-        candidates to help prevent WebRTC to be used for portscanning
-        </li>
-        <li>the support for setting multiple DTLS certificates has been
-        deprecated
-        </li>
-        <li>
-          <code>voiceActivityFlag</code> has been marked at risk for lack of
-          implementation
-        </li>
-        <li>the state machine when closing a <code>PeerConnection</code> has
-        been clarified
-        </li>
-        <li>Align with latest changes in <a href=
-        "https://w3c.github.io/webrtc-stats/">WebRTC Statistics</a>
-        </li>
-      </ul>
+      <p>This document includes <a href="#changes">Candidate Amendments</a> to the current <a href="https://www.w3.org/TR/2021/REC-webrtc-20210126/">W3C Recommendation dated January 26, 2021</a>.</p>
+       <div class="correction"><a href="https://www.w3.org/Consortium/Process/#candidate-correction">Candidate corrections</a> are marked in the document.</div>
       <p>
         Its <a href=
         "https://github.com/web-platform-tests/wpt/tree/master/webrtc">associated
-        test suite</a> will be used to build an <a href=
+        test suite</a> has been used to build an <a href=
         "https://w3c.github.io/webrtc-interop-reports/webrtc-pc-report.html">implementation
-        report</a> of the API.
-      </p>
-      <p>
-        To go into Proposed Recommendation status, the group expects to
-        demonstrate implementation of each feature in at least two deployed
-        browsers, and at least one implementation of each optional feature.
-        Mandatory feature with only one implementation may be marked as
-        optional in a revised Candidate Recommendation where applicable.
+        report</a> of the API at the time of its initial publication as a Recommendation.
       </p>
     </section>
     <section class="informative" id="intro">