- From: Maciej Stachowiak via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 07 Oct 2009 09:53:24 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/decision-policy
In directory hutz:/tmp/cvs-serv13818
Modified Files:
decision-policy.html
Log Message:
More typo fixes thanks to Simon Peters and Smylers.
Index: decision-policy.html
===================================================================
RCS file: /sources/public/html5/decision-policy/decision-policy.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- decision-policy.html 7 Oct 2009 09:06:26 -0000 1.5
+++ decision-policy.html 7 Oct 2009 09:53:22 -0000 1.6
@@ -99,7 +99,7 @@
<li>At least one suggested way to solve the problem. Optionally, this can include sample spec text. Listing multiple alternatives is ok, and even a vague suggestion is fine at this stage.</li>
</ul>
<p>
-<b>Note:</b> These components are not absolutely mandatory for a bug
+<b>Note:</b> These components are not absolutely mandatory for all bug
reports. But bug reports that do not have enough information to
identify a problem or potential action may be closed as INVALID.
</p>
@@ -270,12 +270,12 @@
<li>With prior permission from the chairs, a high-level prose description of the changes to be made.</li>
</ul>
<li>Impact: Effects, both positive and negative, of the change. What conformance classes will have to change? What are the risks?</li>
-
- <li>Complete Change Proposals should be recorded somewhere in W3C
- space (wiki, dev.w3.org, archived mailing list) and the Working
- Group should be notified by email.
</ol>
+<p>>Complete Change Proposals should be recorded somewhere in W3C
+space (wiki, dev.w3.org, archived mailing list) and the Working
+Group should be notified by email.</p>
+
<p>If a Change Proposal is not complete by the deadline (default one month), proceed to <a href="#escalation-step-2a">step 2.a</a>.
</dd>
Received on Wednesday, 7 October 2009 09:53:26 UTC