- From: Sam Ruby via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 25 Sep 2012 18:38:45 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/decision-policy In directory hutz:/tmp/cvs-serv8105 Modified Files: decision-policy-v3.html Log Message: More wordsmithing Index: decision-policy-v3.html =================================================================== RCS file: /sources/public/html5/decision-policy/decision-policy-v3.html,v retrieving revision 1.7 retrieving revision 1.8 diff -u -d -r1.7 -r1.8 --- decision-policy-v3.html 25 Sep 2012 18:36:47 -0000 1.7 +++ decision-policy-v3.html 25 Sep 2012 18:38:43 -0000 1.8 @@ -75,7 +75,8 @@ The Process by which the Working Group decides whether a specification that extends any HTML WG specification can be integrated into the original specification.</li> -<li><a href="#cr-remove-early">13. Removing some at-risk features early in CR</a> - The Process by which the Working Group may drop certain at-risk features early in CR..</li> +<li><a href="#cr-remove-early">13. Removing some at-risk features early in +CR</a> - The Process by which the Working Group may remove certain at-risk features early in CR.</li> </ul> @@ -916,7 +917,7 @@ removals, probably are.</li> <li>During Candidate Recommendation, if anything beyond very minor technical -changes are made, other than dropping features marked "at risk", then the WG +changes are made, other than removing features marked "at risk", then the WG cannot proceed to Proposed Recommendation and must return to Working Draft status.</li> @@ -1160,7 +1161,7 @@ <dl> <dt>1. Marking as at risk</dt> -<dd>To be eligible to be dropped early, the feature must be approved +<dd>To be eligible to be removed early, the feature must be approved by the Working Group to be on the list of at-risk features prior to CR.</dd>
Received on Tuesday, 25 September 2012 18:38:46 UTC