--- a/cover.html	Fri Jan 30 19:08:59 2015 +0100
+++ b/cover.html	Fri Jan 30 19:27:02 2015 +0100
@@ -945,7 +945,7 @@
           the responsibility of the Chair and Team Contact to ensure that new participants are subscribed to all relevant mailing lists.
           Refer to the list of <a href="https://www.w3.org/Member/Mail/">group mailing lists</a> [<a href="#ref-mailing-lists">MEM2</a>].</p>
         <p>A Chair <em class="rfc2119">may</em> form task forces (composed of group participants) to carry out assignments for the group.
-          The scope of these assignments <em class="rfc2119">must not</em> exceed the scope of the group's charter. A group <span class="rfc2119">SHOULD</span>
+          The scope of these assignments <em class="rfc2119">must not</em> exceed the scope of the group's charter. A group <em class="rfc2119">should</em>
           document the process it uses to create task forces (e.g., each task force might have an informal "charter"). Task forces do not
           publish <a href="#Reports">technical reports</a>; the Working Group <em class="rfc2119">may</em> choose to publish their results
           as part of a technical report.</p>
@@ -1097,7 +1097,7 @@
           modification of a Working Group or Interest Group charter.</p>
         <h4>6.2.5 <dfn id="charter-extension">Working Group and Interest Group Charter Extension</dfn></h4>
         <p>To extend a Working Group or Interest Group charter with no other substantive modifications, the Director announces the extension
-          to the Advisory Committee. The announcement <em class="rfc2119">must</em> indicate the new duration. The announcement <span class="rfc2119">MUST</span>
+          to the Advisory Committee. The announcement <em class="rfc2119">must</em> indicate the new duration. The announcement <em class="rfc2119">must</em>
           also include rationale for the extension, a reference to the <a href="#WGCharter">charter</a>, the name(s) of the group's <a href="#GeneralChairs">Chair(s)</a>,
           the name of the <a href="#TeamContact">Team Contact</a>, and instructions for joining the group.</p>
         <p>After a charter extension, Advisory Committee representatives and the Chair are <em class="rfc2119">not required</em> to
@@ -1114,8 +1114,8 @@
             milestones, and the process for the group participants to approve the release of these deliverables (including public
             intermediate results). A charter is <em class="rfc2119">not required</em> to include the schedule for a review of another
             group's deliverables;</li>
-          <li>Any dependencies by groups within or outside of W3C on the deliverables of this group. For any dependencies, the charter <span
-              class="rfc2119">MUST</span> specify the mechanisms for communication about the deliverables;</li>
+          <li>Any dependencies by groups within or outside of W3C on the deliverables of this group. For any dependencies, the charter <em
+              class="rfc2119">must</em> specify the mechanisms for communication about the deliverables;</li>
           <li>Any dependencies of this group on other groups within or outside of W3C. For example, one group's charter might specify that
             another group is expected to review a technical report before it can become a Recommendation. For any dependencies, the charter
             <em class="rfc2119">must</em> specify when required deliverables are expected from the other groups. The charter <em class="rfc2119">should</em>
@@ -1182,7 +1182,7 @@
       <p>Typically a series of Working Drafts are published, each of which refines a document under development to complete the scope of
         work envisioned by a Working Group's charter. For a technical specification, once review suggests the Working Group has met their
         requirements satisfactorily for a new standard, there is a Candidate Recommendation phase. This allows the entire W3C membership to
-        provide feedback on whether the specification should become a W3C Recommendation, while the Working Group formally collects
+        provide feedback on whether the specification is appropriate as a W3C Recommendation, while the Working Group formally collects
         implementation experience to demonstrate that the specification works in practice. The next phase is a Proposed Recommendation, to
         finalize the review of W3C Members. If the Director determines that W3C member review supports a specification becoming a standard,
         W3C publishes it as a Recommendation.</p>
@@ -1262,7 +1262,7 @@
         <dd class="changed">A Candidate Recommendation is a document that satisfies the Working Group's technical requirements, and has
           already received wide review. W3C publishes a Candidate Recommendation to
           <ul>
-            <li>signal to the wider community that a final review should be done</li>
+            <li>signal to the wider community that it is time to do a final review</li>
             <li>gather <a href="#implementation-experience">implementation experience</a></li>
             <li>begin formal review by the Advisory Committee, who <em class="rfc2119">may</em> recommend that the document be published as
               a W3C Recommendation, returned to the Working Group for further work, or abandoned.</li>
@@ -1416,7 +1416,7 @@
           meet all Working Group requirements.</li>
       </ul>
       <h4 id="first-wd">7.3.1 First Public Working Draft</h4>
-      <p>To publish the First Public Working Draft of a document, a Working Group must meet the applicable <a href="#transition-reqs">general
+      <p>To publish the First Public Working Draft of a document, a Working Group <em class="rfc2119">must</em> meet the applicable <a href="#transition-reqs">general
           requirements for advancement</a>.</p>
       <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 public. </p>
@@ -1468,8 +1468,8 @@
           removed before advancement to Proposed Recommendation without a requirement to publish a new Candidate Recommendation.</li>
       </ul>
       <p>The Director <em class="rfc2119">must</em> announce the publication of a Candidate Recommendation to other W3C groups and to the
-        public, and <em class="rfc2119">must</em> begin an Advisory Committee Review on the question of whether W3C should publish the
-        specification as a W3C Recommendation.</p>
+        public, and <em class="rfc2119">must</em> begin an Advisory Committee Review on the question of whether the specification is
+        appropriate to publish as a W3C Recommendation.</p>
       <p> A Candidate Recommendation corresponds to a "Last Call Working Draft" as used in the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C
           Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]. Publishing a Candidate Recommendation triggers a Call for Exclusions,
         per <a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section 4</a> of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C
@@ -1800,7 +1800,7 @@
         Committee support the appeal request, the Team <em class="rfc2119">must</em> organize an appeal vote asking the Advisory Committee
         to approve or reject the decision.
         <!-- Voting procedure to be determined --></p>
-      <h3 id="ACVotes">8.3Advisory Committee Votes</h3>
+      <h3 id="ACVotes">8.3 Advisory Committee Votes</h3>
       <p>The Advisory Committee votes in <a href="#AB-TAG-elections">elections for seats on the TAG or Advisory Board</a>, and in the event
         of a formal appeal of a <a href="#def-w3c-decision">W3C decision</a>. Whenever the Advisory Committee votes, each Member or group
         of <a href="#MemberRelated">related Members</a> has one vote. In the case of <a href="#AB-TAG-elections">Advisory Board and TAG
@@ -1904,24 +1904,24 @@
         Submission process to build consensus around concrete proposals for new work.</p>
       <p>Members <em class="rfc2119">should not</em> submit materials covering topics well outside the scope of <a href="https://www.w3.org/Consortium/mission">W3C's
           mission</a> [<a href="#ref-mission">PUB15</a>].</p>
-      <h4 id="SubmissionReqs">11.1.2Information Required in a Submission Request</h4>
+      <h4 id="SubmissionReqs">11.1.2 Information Required in a Submission Request</h4>
       <p>The Submitter(s) and any other authors of the submitted material <em class="rfc2119">must</em> agree that, if the request is
         acknowledged, the documents in the Member Submission will be subject to the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C
           Document License</a> [<a href="#ref-doc-license">PUB18</a>] and will include a reference to it. The Submitter(s) <em class="rfc2119">may</em>
         hold the copyright for the documents in a Member Submission.</p>
-      <p>The request must satisfy the Member Submission licensing commitments of <a href="https://www.w3.org/Consortium/Patent-Policy#sec-submissions">section
+      <p>The request <em class="rfc2119">must</em> satisfy the Member Submission licensing commitments of <a href="https://www.w3.org/Consortium/Patent-Policy#sec-submissions">section
           3.3</a> of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
       <p>The Submitter(s) <em class="rfc2119">must</em> include the following information:</p>
       <ul>
         <li>The list of all submitting Members.</li>
-        <li>Position statements from all submitting Members (gathered by the Submitter). All position statements must appear in a separate
-          document.</li>
+        <li>Position statements from all submitting Members (gathered by the Submitter). All position statements <em class="rfc2119">must</em>
+          appear in a separate document.</li>
         <li>Complete electronic copies of any documents submitted for consideration (e.g., a technical specification, a position paper,
-          etc.) If the Submission request is acknowledged, these documents will be published by W3C and therefore must satisfy the
-          Communication Team's <a href="https://www.w3.org/Guide/pubrules">Publication Rules</a> [<a href="#ref-pubrules">PUB31</a>].
-          Submitters may hold the copyright for the material contained in these documents, but when published by W3C, these documents <span
-            class="rfc2119">MUST</span> be subject to the provisions of the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C
-            Document License</a> [<a href="#ref-doc-license">PUB18</a>].</li>
+          etc.) If the Submission request is acknowledged, these documents will be published by W3C and therefore <em class="rfc2119">must</em>
+          satisfy the Communication Team's <a href="https://www.w3.org/Guide/pubrules">Publication Rules</a> [<a href="#ref-pubrules">PUB31</a>].
+          Submitters may hold the copyright for the material contained in these documents, but when published by W3C, these documents <em class="rfc2119">must</em>
+          be subject to the provisions of the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a> [<a
+            href="#ref-doc-license">PUB18</a>].</li>
       </ul>
       <p>The request <em class="rfc2119">must</em> also answer the following questions.</p>
       <ul>