Fixing some typos / grammar errors (Thanks to Wayne Carr)
authorcharles
Tue, 03 Dec 2013 22:46:26 +0100
changeset 48 2097fedfe542
parent 47 b29f6b51a034
child 49 673eedc75a9a
Fixing some typos / grammar errors (Thanks to Wayne Carr)
tr.html
--- a/tr.html	Tue Oct 22 03:01:28 2013 +0100
+++ b/tr.html	Tue Dec 03 22:46:26 2013 +0100
@@ -266,7 +266,7 @@
       style, and <a name="document-copyright" id="document-copyright">copyright
         requirements</a>). These rules are subject to change by the Team from
       time to time. The Team <em class="rfc2119">must</em> inform group Chairs
-      and the Advisory Board of any changes to these rules.</p>
+      and the Advisory Committee of any changes to these rules.</p>
     <p>The primary language for W3C Technical Reports is English. W3C encourages
       the translation of its Technical Reports. <a href="http://www.w3.org/Consortium/Translation/">Information
         about translations of W3C technical reports</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-translations">PUB18</a>]
@@ -315,16 +315,15 @@
       <dt><a name="WGNote" id="WGNote">Working Group Note, Interest Group Note
           (NOTE) </a></dt>
       <dd>A Working Group Note or Interest Group Note is published by a
-        chartered Working Group or Interest Group to &gt;provide a stable
-        reference for some document that is not intended to be a normative
-        specification, but is nevertheless useful. For example, supporting
-        documents such as Use case and Requirements documents, or Design
-        Principles, that explain what the Working Group was trying to achieve
-        with a specification, or non-normative 'Good Practices" documents. A
-        Working Group <em class="rfc2119">may</em> also publish a specification
-        as a Note if they stop work without producing a Recommendation. A
-        Working Group or Interest Group <em class="rfc2119">may</em> publish a
-        Note with or without its prior publication as a Working Draft.</dd>
+        chartered Working Group or Interest Group to provide a stable reference
+        for a document that is not intended to be a normative specification, but
+        is nevertheless useful. Examples include supporting documents such as
+        Use case and Requirements documents, Design Principles that explain what
+        the Working Group was trying to achieve with a specification, or 'Good
+        Practices" documents. A Working Group <em class="rfc2119">may</em> also
+        publish a specification as a Note if they stop work without producing a
+        Recommendation. A Working Group or Interest Group <em class="rfc2119">may</em>
+        publish a Note with or without its prior publication as a Working Draft.</dd>
       <dt><a name="RescindedRec" id="RescindedRec">Rescinded Recommendation</a></dt>
       <dd>A Rescinded Recommendation is an entire Recommendation that W3C no
         longer endorses. See also clause 10 of the licensing requirements for
@@ -403,7 +402,7 @@
       relevant stakeholder community.</p>
     <h4 id="implementation-experience">7.2.3 Implementation Experience</h4>
     <p>Implementation experience is required to show that a specification is
-      sufficiently clear, complete, and relevant to market needs that
+      sufficiently clear, complete, and relevant to market needs, to ensure that
       independent interoperable implementations of each feature of the
       specification will be realized. While no exhaustive list of requirements
       is provided here, when assessing that there is <dfn>adequate
@@ -473,7 +472,8 @@
         parts of the document on which the Working Group does not have
         consensus, and</li>
       <li> <em class="rfc2119">may</em> request publication of a Working Draft
-        even if it is unstable and does not meet all Working Group requirements.</li>
+        even if its content is considered unstable and does not meet all Working
+        Group requirements.</li>
     </ul>
     <p>The Director <em class="rfc2119">must</em> announce the publication of a
       First Public Working Draft publication to other W3C groups and to the
@@ -509,7 +509,8 @@
       <li><em class="rfc2119">should</em> document outstanding issues and parts
         of the document on which the Working Group does not have consensus, and</li>
       <li><em class="rfc2119">may</em> request publication of a Working Draft
-        even if it is unstable and does not meet all Working Group requirements.</li>
+        even if its content is considered unstable and does not meet all Working
+        Group requirements.</li>
     </ul>
     <p>Possible next steps:</p>
     <ul>
@@ -667,8 +668,8 @@
       If the Director <a href="http://www.w3.org/2005/10/Process-20051014/groups.html#GeneralTermination">closes
         a Working Group</a> W3C <em class="rfc2119">must </em> publish any
       unfinished specifications on the Recommendation track as Working Group
-      Notes. If a Working group decides, or the Director requires the Working
-      Group to discontinue work on a technical report before completion the
+      Notes. If a Working group decides, or the Director requires, the Working
+      Group to discontinue work on a technical report before completion, the
       Working Group <em class="rfc2119">should</em> publish the document as a
       Working Group Note. </p>
     <p>In order to publish a Note a Working Group or Interest Group: </p>