--- a/cover.html	Sat Sep 13 20:35:33 2014 +0200
+++ b/cover.html	Sat Sep 13 23:13:45 2014 +0200
@@ -1396,54 +1396,29 @@
       <section class="issue" id="chapterActivities">
         <h2>5 Activities</h2>
         <p><em>This section is being removed, leaving internal management of
-            work to W3C Team. In <strong>this</strong> draft, points not
-            covered elsewhere and relevant beyond the structure of "Activites"
-            have been left here, until there is a resolution on what to do about
-            them.</em></p>
-        <br>
+            work to W3C Team. In <strong>this</strong> draft, unresolved issues
+            dealing with material not covered elsewhere and relevant beyond the
+            structure of "Activities" have been left here, until there is a
+            resolution on what to do about them.</em></p>
         <p>The progress of each Activity is documented in an Activity Statement.
           At least before each <a href="#ACMeetings">Advisory Committee meeting</a>,
           the Team <span class="rfc2119">SHOULD</span> revise the Activity
           Statement for each Activity that has not been closed. <span class="issue">Should
-            we put this requirement on charters?</span></p>
-        <h3>5.2 Advisory Committee Review of an Activity Proposal</h3>
-        <br>
-        <br>
+            we put this requirement on charters? <a href="http://www.w3.org/community/w3process/track/issues/115">ISSUE-115</a><br>
+          </span></p>
         <h3>5.6 Activity Proposals</h3>
         <p>An Activity Proposal defines the initial scope and structure of an
           Activity. The proposal <span class="rfc2119">MUST</span> include or
           reference the following information:</p>
         <ul>
-          <li>Context information. Why is this Activity being proposed now? What
-            is the situation in the world (e.g., with respect to the Web
-            community, market, research, or society)? within the scope of the
-            proposal? Who or what currently exists that is pertinent to this
-            Activity? Is the community mature/growing/developing a niche? What
-            competing technologies exist? What competing organizations exist? <span
-              class="issue">For Activities the appeal required dissent in the
-              review. Should we have that constraint?</span></li>
-          <li>A description of the Activity's scope. How might a potential
-            Recommendation interact and overlap with existing international
-            standards and Recommendations? What organizations are likely to be
-            affected by potential overlap (see the section on <a href="#Liaisons">liaisons
-              with other organizations</a>)? What should be changed if the
-            Activity is approved? <span class="issue">Do we need this info
-              beyond the dependency information already required?</span></li>
-          <li>The proposal <span class="rfc2119">MAY</span> specify the
-            threshold level of effort that Members are expected to pledge in
-            order for the Activity to be accepted. <span class="issue">The team
-              adopted a best practice to do this</span></li>
           <li>Intellectual property information. What are the intellectual
             property (including patents and copyright) considerations affecting
             the success of the Activity? In particular, is there any reason to
             believe that it will be difficult to meet the Royalty-Free licensing
             goals of section 2 of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
               Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]? <span
-              class="issue">Should we put this requirement on charters?</span></li>
-          <li>A list of supporters and references. What community is expected to
-            benefit from this Activity? Are members of this community part of
-            W3C now? Are they expected to join the effort? <span class="issue">Should
-              we put this requirement on charters?</span></li>
+              class="issue">Should we put this requirement on charters? <a href="http://www.w3.org/community/w3process/track/issues/121">ISSUE-121</a><br>
+            </span></li>
         </ul>
       </section>
       <section id="ChapterGroups">
@@ -1964,22 +1939,21 @@
             or to maintain the group, according to priorities established within
             W3C.</li>
           <li>The group produces chartered deliverables ahead of schedule.</li>
-          <li>The Activity to which the group belongs terminates.</li>
         </ul>
         <p>The Director closes a Working Group or Interest Group by announcement
           to the Advisory Committee.</p>
         <p>Closing a Working Group has implications with respect to the <a href="http://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</a></h3>
-        <p>W3C Activities interact in many ways. There are dependencies between
-          groups within the same Activity or in different Activities. There are
-          also dependencies between W3C Activities and the activities of other
-          organizations. Examples of dependencies include the use by one
-          technology of another being developed elsewhere, scheduling
-          constraints between groups, and the synchronization of publicity for
-          the announcement of deliverables. Coordination Groups are created to
-          manage dependencies so that issues are resolved fairly and the
-          solutions are consistent with W3C's mission and results.</p>
+        <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 dependencies
+          include the use by one technology of another being developed
+          elsewhere, scheduling constraints between groups, and the
+          synchronization of publicity for the announcement of deliverables.
+          Coordination Groups are created to manage dependencies so that issues
+          are resolved fairly and the solutions are consistent with W3C's
+          mission and results.</p>
         <p>Where a Coordination Group's scope covers two groups with unresolved
           disputes or tensions, it is the first locus of resolution of these
           disputes.</p>