--- a/cover.html	Tue Sep 30 19:41:27 2014 +0400
+++ b/cover.html	Wed Oct 22 00:56:18 2014 +0200
@@ -19,7 +19,7 @@
     <div class="head"><a href="https://www.w3.org/"><img alt="W3C" src="https://www.w3.org/Icons/w3c_home"
           height="48" width="72"></a>
       <h1>W3C Draft Process Document</h1>
-      <h2 class="notoc">30 September 2014 Editor's Draft</h2>
+      <h2 class="notoc">21 Otober 2014 Editor's Draft</h2>
       <dl>
         <dt>Latest Editor's version:</dt>
         <dd> <a href="https://dvcs.w3.org/hg/AB/raw-file/default/cover.html">https://dvcs.w3.org/hg/AB/raw-file/default/cover.html</a></dd>
@@ -61,26 +61,26 @@
     <p>For more information about the W3C mission and the history of W3C, please
       refer to <a href="https://www.w3.org/Consortium/">About W3C</a> [<a href="#ref-mission">PUB15</a>].</p>
     <h2 class="notoc"><a id="status">Status of this Document</a></h2>
-    <p>This is the 30 September 2014 Editor's draft for the proposed next
-      version of the W3C Process Document. This document is based on the 1
-      August 2014 Process, developed between the <a href="/2002/ab/">W3C
-        Advisory Board</a> and the <a href="https://www.w3.org/community/w3process/">Revising
-        W3C Process Community Group</a> and adopted as the currently operative
-      Process. During the rest of 2014 the document will be developed in
-      preparation for adopting a revised process in 2015.</p>
     <p>W3C, including all existing chartered groups, follows the <a href="https://www.w3.org/Consortium/Process/">most
         recent operative Process Document</a> announced to the Membership.</p>
-    <p>In <em>this draft</em>, Chapter 5 (Activities) has been removed, with a
-      few requirements maintained in other parts of the process. Section 6.2.1.7
-      "Good standing in a working group" has also been removed.</p>
-    <p>This draft is offered to the W3C Advisory Comittee for review, as an
-      interim Working Draft. Public comment is also invited on the draft.</p>
-    <p>Please send comments about this document to the <a href="https://www.w3.org/community/w3process/">Revising
+    <p>This is the 21 October 2014 Editor's draft for the proposed next version
+      of the W3C Process Document. This document is based on 30 September review
+      draft, itself based on the 1 August 2014 Process, developed between the <a
+        href="/2002/ab/">W3C Advisory Board</a> and the <a href="https://www.w3.org/community/w3process/">Revising
+        W3C Process Community Group</a> and adopted as the currently operative
+      Process. </p>
+    <p>In <em>this draft</em>, Section 6.2.7 "Heartbeat" requirement has been
+      removed. A <a href="#changes">change history</a> compared to the 2014
+      Process Document forms part of the draft.</p>
+    <p>During the rest of 2014 the document will be developed in preparation for
+      adopting a revised process in 2015.</p>
+    <p>Public comment is invited on the draft. Please send comments about this
+      document to the <a href="https://www.w3.org/community/w3process/">Revising
         W3C Process Community Group</a> (<a href="https://lists.w3.org/Archives/Public/public-w3process/">Mailing
         list archive</a>, publicly available) or to process-issues@w3.org (<a href="https://lists.w3.org/Archives/Member/process-issues">Member-only
         archive</a>). A <a href="https://www.w3.org/community/w3process/track/">Public
         Issue Tracker</a> and <a href="https://dvcs.w3.org/hg/AB/">detailed
-        changelogs</a> are available online.</p>
+        changelogs</a> are available online. </p>
     <h2 class="notoc"><a id="pp">Relation of Process Document to Patent Policy</a></h2>
     <p>W3C Members' attention is called to the fact that provisions of the
       Process Document are binding on Members per the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
@@ -120,8 +120,7 @@
               Policies for W3C Groups</a></li>
           <li class="tocline2"><a href="#dissemination" class="tocxref">4
               Dissemination Policies</a></li>
-          <li class="tocline2"><s><a href="#chapterActivities" class="tocxref">5
-                Activities</a></s></li>
+          <li class="tocline2"><s>5 Activities</s></li>
           <li class="tocline2"><a href="#GAGeneral" class="tocxref">6 Working
               Groups, Interest Groups, and Coordination Groups</a></li>
           <li class="tocline2"><a href="#Reports" class="tocxref">7 W3C
@@ -258,8 +257,8 @@
                     Group and Interest Group Charter Extension</a></li>
                 <li class="tocline4"><a href="#WGCharter">6.2.6 Working Group
                     and Interest Group Charters</a></li>
-                <li class="tocline4"><a href="#three-month-rule">6.2.7 Working
-                    Group "Heartbeat" Requirement</a></li>
+                <li class="tocline4"><s>6.2.7 Working Group "Heartbeat"
+                    Requirement</s></li>
                 <li class="tocline4"><a href="#GeneralTermination">6.2.8 Working
                     Group and Interest Group Closure</a></li>
               </ul>
@@ -410,11 +409,11 @@
           Workshop and/or discussion on an <a href="#ACCommunication">Advisory
             Committee mailing list</a>), the Director announces the <a href="#ActivityDevelopment">development
             of a proposal for one or more new</a> or Interest Group or <a href="#WGCharterDevelopment">Working
-            Group charter</a>, depending on the breadth of the topic of interest.
-          W3C Members <a href="#ActivityCreation">review</a> the proposed
-          charters. When there is support within W3C for investing resources in
-          the topic of interest, the Director approves the group(s) and they
-          begin their work.</li>
+            Group charter</a>, depending on the breadth of the topic of
+          interest. W3C Members <a href="#ActivityCreation">review</a> the
+          proposed charters. When there is support within W3C for investing
+          resources in the topic of interest, the Director approves the group(s)
+          and they begin their work.</li>
         <li>There are three types of Working Group participants: <a href="#member-rep">Member
             representatives</a>, <a href="#invited-expert-wg">Invited Experts</a>,
           and <a href="#Team">Team representatives</a>. Team representatives
@@ -1776,48 +1775,6 @@
           those of the W3C Process Document (e.g., limits on the number of
           individuals in a Working Group who represent the same Member
           organization or group of <a href="#MemberRelated">related Members</a>).</p>
-        <h4>6.2.7 <a id="three-month-rule">Working Group "Heartbeat"
-            Requirement</a></h4>
-        <p>It is important that a Working Group keep the Membership and public
-          informed of its activity and progress. To this end, each Working Group
-          <span class="rfc2119">SHOULD</span> publish in the <a href="https://www.w3.org/TR/">W3C
-            technical reports index</a> a new draft of <em>each active
-            technical report</em> at least once every three months. An active
-          technical report is a Working Draft, Candidate Recommendation,
-          Proposed Recommendation, or Proposed Edited Recommendation. Each
-          Working Group <span class="rfc2119">MUST</span> publish a new draft
-          of <em>at least one of its active technical reports</em> on the <a href="https://www.w3.org/TR/">W3C
-            technical reports index</a> [<a href="#ref-doc-list">PUB11</a>] at
-          least once every three months.</p>
-        <p>Public progress reports are also important when a Working Group does
-          not update a technical report within three months (for example, when
-          the delay is due to a challenging technical issue) or when a Working
-          Group has no active technical reports (for example, because it is
-          developing a test suite).</p>
-        <p>In exceptional cases, the Chair <span class="rfc2119">MAY</span> ask
-          the Director to be excused from this publication requirement. However,
-          in this case, the Working Group <span class="rfc2119">MUST</span>
-          issue a public status report with rationale why a new draft has not
-          been published.</p>
-        <p>There are several reasons for this Working Group "heartbeat"
-          requirement:</p>
-        <ul>
-          <li>To promote public accountability;</li>
-          <li>To encourage Working Groups to keep moving forward, and to
-            incorporate their decisions into readable public documents. People
-            cannot be expected to read several months of a group's mailing list
-            archive to understand where the group stands;</li>
-          <li>To notify interested parties of updated work in familiar a place
-            such as the W3C home page and index of technical reports.</li>
-        </ul>
-        <p>As an example, suppose a Working Group has one technical report as a
-          deliverable, which it publishes as a Proposed Recommendation. Per the
-          heartbeat requirement, the Working Group is required to publish a new
-          draft of the Proposed Recommendation at least once every three months,
-          even if it is only to revise the status of the Proposed Recommendation
-          document (e.g., to provide an update on the status of the decision to
-          advance). The heartbeat requirement stops when the document becomes a
-          Recommendation (or a Working Group Note).</p>
         <h4>6.2.8 <a id="GeneralTermination">Working Group and Interest Group
             Closure</a></h4>
         <p>A Working Group or Interest Group charter specifies a duration for
@@ -1836,8 +1793,8 @@
         <p>Closing a Working Group has implications with respect to the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C
             Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
         <h3>6.3 <a id="GroupsCG">Coordination Groups&nbsp;<span class="issue">
-              <a href="https://www.w3.org/community/w3process/track/issues/129">ISSUE-129</a>
-              proposes to remove the separate definition of Coordination Groups.</span></a></h3>
+            </span></a><a href="https://www.w3.org/community/w3process/track/issues/129">ISSUE-129</a>
+          proposes to remove the separate definition of Coordination Groups.</h3>
         <p>W3C activities interact in many ways. There are dependencies between
           groups within the same area, in different areas, and between W3C
           activities and the activities of other organizations. Examples of
@@ -3289,7 +3246,15 @@
       <h2 id="changes">15 Changes</h2>
       <p>This document is based on 1 August 2014 Process. <a href="https://dvcs.w3.org/hg/AB/">Detailed
           change logs</a> are available.</p>
-      <p>Notable changes include:</p>
+      <p>The notable changes include:</p>
+      <h3><span style="color: black;">Current Editor's draft</span></h3>
+      <ul>
+        <li>Remove section <span id="three-month-rule">6.2.7 "Heartbeat"
+            publishing requirement</span></li>
+      </ul>
+      <h3><span style="color: black;">30 September "AC intermediate review"</span></h3>
+      <p>Provided to the Advisory Committee to review the following changes made
+        compared to the 1 August 2014 Operative Process document</p>
       <ul>
         <li>Remove <a id="def-Activity">A</a><a id="ActivityStatement">c</a><a
             id="ActivityDevelopment">t</a><a id="ActivityCreation">i</a><a id="ActivityModification">v</a><a