W3C home > Mailing lists > Public > public-html-commits@w3.org > August 2012

html5/decision-policy decision-policy-v3.html,1.3,1.4

From: Sam Ruby via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 20 Aug 2012 02:07:24 +0000
To: public-html-commits@w3.org
Message-Id: <E1T3HOm-0008It-9o@lionel-hutz.w3.org>
Update of /sources/public/html5/decision-policy
In directory hutz:/tmp/cvs-serv31905

Modified Files:
	decision-policy-v3.html 
Log Message:
Fix typos


Index: decision-policy-v3.html
===================================================================
RCS file: /sources/public/html5/decision-policy/decision-policy-v3.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- decision-policy-v3.html	13 Aug 2012 17:06:51 -0000	1.3
+++ decision-policy-v3.html	20 Aug 2012 02:07:21 -0000	1.4
@@ -769,7 +769,7 @@
 <p>
 Whereas the <a href="#enhanced">Enhanced Change Control</a> process merely
 encouraged changes to be pre-flighted with the group, at this point in the
-process every every commit that makes a substantive change or introduces
+process every commit that makes a substantive change or introduces
 additional willful violations of other standards -- even in non-normative
 text, like examples -- must be pre-approved by the WG as a whole before being
 applied.  Approvals will take place on the <a
@@ -777,7 +777,7 @@
 mailing list, can be done in batches by simply enumerating the bug report
 numbers.  Ideally, such bug reports will already have proposed fixes in the
 form of patches linked to the bug before an approval request is made, but at a
-minimum such any bugs submitted for approval will have a proposed solution
+minimum any such bugs submitted for approval will have a proposed solution
 described in prose in sufficient detail for the Working Group to make a
 determination as to whether or not to allow the spec to be changed in this
 manner.
Received on Monday, 20 August 2012 02:07:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 20 August 2012 02:07:26 GMT