html5/decision-policy decision-policy-v2.html,1.22,1.23

Update of /sources/public/html5/decision-policy
In directory hutz:/tmp/cvs-serv27113

Modified Files:
	decision-policy-v2.html 
Log Message:
Various typos in Decision Policy
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12733


Index: decision-policy-v2.html
===================================================================
RCS file: /sources/public/html5/decision-policy/decision-policy-v2.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- decision-policy-v2.html	18 May 2011 18:25:54 -0000	1.22
+++ decision-policy-v2.html	29 May 2011 21:58:45 -0000	1.23
@@ -597,7 +597,7 @@
 for a future version of HTML.
 </dd>
 
-<dt id="lc-review-step-4">4. Editors Complete Initial Pesponses</dt>
+<dt id="lc-review-step-4">4. Editors Complete Initial Responses</dt>
 <dd>Within two months of the end of the comment period, or a different
 period as determined by the Chairs in consultation with the Editors
 and the Working Group, all bugs submitted by the end of that review
@@ -612,9 +612,9 @@
 <dd>Within two weeks of the editor's response deadline, or a different
 period as determined by the Chairs in consultation with the Editors
 and the Working Group, all bugs from the review period must
-be <a href="basic-step-5d">Escalted to Issues</a> if the commentor or
+be <a href="basic-step-5d">Escalated to Issues</a> if the commentor or
 any other WG member is dissatisfied with the Editor's Response. Any
-further escalations beoyond this date will not be treated as a Last
+further escalations beyond this date will not be treated as a Last
 Call or pre-Last Call comment (whichever is applicable). Such
 escalations can be taken up during a subsequent LC or CR period.
 </dd>
@@ -625,7 +625,7 @@
 and the Working Group, all <a href="#escalation-step-1">Calls for
 Change Proposals</a> will be complete. Any issue that does not have a
 Change Proposal by this date will be closed without prejudice and
-marked POSTPONED. Such issuescan be reconsidered during a subsequent
+marked POSTPONED. Such issues can be reconsidered during a subsequent
 LC, CR, or for a later version of HTML.
 </dd>
 
@@ -680,7 +680,7 @@
 Member may identify new information relevant to the decision which,
 per the W3C Process, could lead
 to <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#WGChairReopen">the
-decisopn being reopened</a>.</p>
+decision being reopened</a>.</p>
 
 <p>The following are the steps to request reopening :</p>
 
@@ -689,7 +689,7 @@
 <dt id="reopen-step-1">1. Submit a Reopen Request</dt>
 <dd>
 <p>A request to reopen an issue should be submitted to
-the <a href="mailto:public-html@w3c.org">public-html@w3c.org</a>
+the <a href="mailto:public-html@w3.org">public-html@w3.org</a>
 mailing list. A request to reopen should identify the issue to be
 reopened, and should include the following:</p>
 

Received on Sunday, 29 May 2011 21:58:48 UTC