Minor Editorial improvements as proposed by Wayne Carr (including modification from Ralph Swick) - thread from http://www.w3.org/mid/[email protected]
authorcharles
Wed, 19 Mar 2014 12:48:55 +0100
changeset 92 a5988ded2629
parent 91 7e3c49854fba
child 93 0c295d14a635
Minor Editorial improvements as proposed by Wayne Carr (including modification from Ralph Swick) - thread from http://www.w3.org/mid/[email protected]
tr.html
--- a/tr.html	Wed Mar 19 12:43:42 2014 +0100
+++ b/tr.html	Wed Mar 19 12:48:55 2014 +0100
@@ -434,13 +434,11 @@
         with other groups.</li>
       <li><em class="rfc2119">should</em> document known implementation.</li>
     </ul>
-    <p>Because the requirements for First Public Working Drafts are fairly
-      mechanical, approval is normally fairly automatic. For later stages,
-      especially transition to Candidate or Proposed Recommendation, there is
-      generally a formal review meeting to ensure the requirements have been met
-      before Director's approval is given.</p>
-    <p>Note that for a First Public Working Draft there is no "previous maturity
-      level".</p>
+    <p>For a First Public Working Draft there is no "previous maturity level",
+      so many requirements do not apply and approval is normally fairly
+      automatic.. For later stages, especially transition to Candidate or
+      Proposed Recommendation, there is generally a formal review meeting to
+      ensure the requirements have been met before Director's approval is given.</p>
     <h4 id="doc-reviews">7.2.3 Reviews and Review Responsibilities</h4>
     <p>A document is available for review from the moment it is first published.
       Working Groups <em class="rfc2119">should</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
@@ -787,17 +785,18 @@
       interested parties, notably when corrections are proposed or incorporated
       into an Edited Recommendation, according to the Team's requirements.</p>
     <h4 id="revised-rec">7.7.2 Revising a Recommendation</h4>
-    <p>Editorial changes to a Recommendation require no technical review of the
-      proposed changes. A Working Group <span class="rfc2119">may</span>
-      request republication of a Recommendation 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
+    <p><a href="#editorial-change">Editorial changes</a> to a Recommendation
+      require no technical review of the proposed changes. A Working Group <span
+        class="rfc2119">may</span> request republication of a Recommendation 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> [[email protected]@].</p>
-    <p>For substantive changes that do not add new features, a Working Group <span
-        class="rfc2119">must</span> request publication of an <a href="#rec-edited">Edited
-        Recommendation</a>.</p>
+    <p>For <a href="#substantive-change">substantive changes</a> that do not
+      add new features, a Working Group <span class="rfc2119">must</span>
+      request publication of an <a href="#rec-edited">Edited Recommendation</a>.</p>
     <p>To publish an Edited Recommendation as a W3C Recommendation, in addition
       to meeting the <a href="#rec-requirements">requirements for all W3C
         Recommendations</a>, a Working Group</p>
@@ -816,8 +815,8 @@
       specification as Notes. This includes supporting documentation for a
       specification such as explanations of design principles or use cases and
       requirements, non-normative guides to good practices, as well as
-      specifications where work has been stopped and there is no longer interest
-      in making them a new standard.</p>
+      specifications where work has been stopped and there is no longer
+      consensus for making them a new standard.</p>
     <p>In order to publish a Note, a Working Group or Interest Group: </p>
     <ul>
       <li> <em class="rfc2119">may</em> publish a Note with or without its