--- a/tr.html	Fri Oct 18 02:20:38 2013 +0200
+++ b/tr.html	Fri Oct 18 02:50:16 2013 +0200
@@ -730,16 +730,16 @@
       published as Recommendation, the W3C Process focuses on those changes to a
       technical report that might affect the conformance of content or deployed
       software.</p>
-    <p>Working Groups <span class="rfc2119">MUST</span> track errata on an
+    <p>Working Groups <span class="rfc2119">must</span> track errata on an
       "errata page." An errata page is a list of enumerated errors, possibly
       accompanied by corrections. Each Recommendation links to an errata page;
       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 by the process described below.</p>
-    <p>A Working Group <span class="rfc2119">SHOULD</span> keep their errata
+    <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
+      Working Group <span class="rfc2119">must</span> report errata page
       changes to interested parties, notably when corrections are proposed or
       become normative, according to the Team's requirements. For instance, the
       Team might set up a mailing list per Recommendation where a Working Group
@@ -750,13 +750,13 @@
       Recommendation.</p>
     <dl>
       <dt>1. No changes to text content</dt>
-      <dd>These changes include fixing broken links or invalid markup.</dd>
-      <dt>2. Corrections that do not affect conformance</dt>
-      <dd>Editorial changes or clarifications that do not change the technical
-        content of the specification.</dd>
-      <dt>3. Corrections that <span class="rfc2119">MAY</span> affect
-        conformance, but add no new features</dt>
-      <dd>These changes <span class="rfc2119">MAY</span> affect conformance to
+      <dd>These changes include fixing broken style sheets or invalid markup.</dd>
+      <dt>2. Corrections to references</dt>
+      <dd>Updates to references, e.g. because the original reference is outdated
+        or no longer available, that do not affect conformance to the
+        specification.</dd>
+      <dt>3. Corrections that do not add new features</dt>
+      <dd>These changes <span class="rfc2119">may</span> affect conformance to
         the Recommendation. A change that affects conformance is one that:
         <ul>
           <li>turns conforming data, processors, or other conforming agents into
@@ -770,16 +770,18 @@
       <dt>4. New features</dt>
     </dl>
     <p>The first two classes of change require no technical review of the
-      proposed changes, although a Working Group <span class="rfc2119">MAY</span>
-      issue a Call for Review. The modified Recommendation is published
-      according to the Team's requirements, including <a href="http://www.w3.org/Guide/pubrules">Publication
-        Rules</a> [<a href="refs.html#ref-pubrules">PUB31</a>].</p>
-    <p>For the third class of change, the Working Group <span class="rfc2119">MUST</span>
-      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>
+      proposed changes. A Working Group <span class="rfc2119">may</span>
+      request republication of a Recommenation for these classes of change, or
+      W3C <span class="rfc2119">may</span> republish a Recommendation with this
+      class of change. The modified Recommendation is published according to the
+      Team's requirements, including <a href="http://www.w3.org/Guide/pubrules">Publication
+        Rules</a> [<a href="refs.html#ref-pubrules">PUB31</a>] and the <a href="http://www.w3.org/2003/01/republishing/">Requirements
+        for modification of W3C Technical Reports</a> [PUB@@].</p>
+    <p>For the third class of change, a Working Group <span class="rfc2119">must</span>
+      request publication of an <a href="#rec-edited">Edited Recommendation</a>.</p>
+    <p>For the fourth class of change, which introduces a new feature or
+      features, W3C <span class="rfc2119">must</span> follow the full process
+      of <a href="#rec-advance">advancing a technical report to Recommendation</a>.</p>
     <h3>7.7 <a name="rec-rescind" id="rec-rescind">Rescinding a W3C
         Recommendation</a></h3>
     <p>W3C <em class="rfc2119">may</em> rescind a Recommendation, for example