--- a/tr.html	Thu Oct 03 18:31:51 2013 +0400
+++ b/tr.html	Thu Oct 03 18:40:14 2013 +0400
@@ -699,11 +699,7 @@
       see the Team's <a href="http://www.w3.org/Guide/pubrules">Publication
         Rules</a>.</p>
     <p>A correction is first "proposed" by the Working Group. A correction
-      becomes normative -- of equal status as the text in the published
-      Recommendation -- through one of the processes described below. An errata
-      page <span class="rfc2119">MAY</span> include both proposed and normative
-      corrections. The Working Group <span class="rfc2119">MUST</span> clearly
-      identify which corrections are proposed and which are normative.</p>
+      becomes normative by the process described below.</p>
     <p>A Working Group <span class="rfc2119">SHOULD</span> keep their errata
       pages up-to-date, as errors are reported by readers and implementers. A
       Working Group <span class="rfc2119">MUST</span> report errata page
@@ -749,22 +745,8 @@
         incorporated.</li>
     </ol>
     <p>For the third class of change, the Working Group <span class="rfc2119">MUST</span>
-      either:</p>
-    <ol>
-      <li>Request that the Director issue a <a href="#cfr-edited">Call for
-          Review of an Edited Recommendation</a>, or</li>
-      <li>Issue a <a href="#cfr-corrections">Call for Review of Proposed
-          Corrections</a> that have not been incorporated into an edited draft
-        (e.g., those listed on an errata page). After this review, the Director
-        <span class="rfc2119">MAY</span> announce that the proposed corrections
-        are normative.</li>
-    </ol>
-    <p>While the second approach is designed so that a Working Group can
-      establish normative corrections quickly, it does not obviate the need to
-      incorporate changes into an edited version of the Recommendation. In
-      particular, when corrections are numerous or complex, integrating them
-      into a single document is important for interoperability; readers might
-      otherwise interpret the corrections differently.</p>
+      request that the Director issue a <a href="#cfr-edited">Call for Review
+        of an Edited Recommendation</a>.</p>
     <p>For the fourth class of change (new features), W3C <span class="rfc2119">MUST</span>
       follow the full process of <a href="#rec-advance">advancing a technical
         report to Recommendation</a>.</p>