Fixes and addresses a bunch of issues raised in horizontal review (#319)

* Fixes #311

* Fixes #312: Q42021

* Fixes #315

* Fixes #316

* Addresses #317

pe-2020.html

@@ -204,8 +204,6 @@ <h2>
           Deliverables
         </h2>
 
-        <p>More detailed milestones and updated publication schedules are available on the <a href="https://www.w3.org/wiki/[groupname]/PubStatus">group publication status page</a>.</p>
-
         <p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval. <i>Expected completion</i> indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.</p>
 
         <section id="normative">
@@ -222,7 +220,7 @@ <h3>
 
               <p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/pointerevents3/">Working Draft</a></p>
 
-              <p class="milestone"><b>Expected completion:</b> Q4 2020</p>
+              <p class="milestone"><b>Expected completion:</b> Q4 2021</p>
               <p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2020/WD-pointerevents3-20201001/">Pointer Events (Level 3), 1 October 2020</a></p>
       <p><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2019/WD-pointerevents3-20191212/">Pointer Events (Level 3), 12 December 2020</a><br>
         associated <a href='https://www.w3.org/mid/[email protected]'> Call for Exclusion</a> on 12-Dec-2019
@@ -278,6 +276,11 @@ <h2>Coordination</h2>
         <section>
           <h3 id="w3c-coordination">W3C Groups</h3>
           <dl>
+            <dt><a href="https://www.w3.org/das/">Devices and Sensors Working Group</a></dt>
+            <dd>
+              The mission of the Devices and Sensors Working Group (DAS WG) is to create secure and privacy-preserving client-side APIs that enable the development of web applications that interact with device capabilities.
+              Mitigating of fingerprinting risks should be coordinated with this Group.
+            </dd>
             <dt><a href="https://www.w3.org/community/touchevents/">Touch Events Community Group</a></dt>
             <dd>
             The Touch Events community group was formed by members of the Web Events Working Group (responsible for the Touch Events specification) and the Pointer Events Working Group (responsible for the Pointer Events spec). The group's focus is to determine differences in touch event behavior between browsers.
@@ -331,7 +334,7 @@ <h2>
         The meetings themselves are not open to public participation, however.
         </p>
         <p>
-          Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="">Pointer Events Working Group home page.</a>
+          Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="https://www.w3.org/2012/pointerevents/">Pointer Events Working Group home page.</a>
         </p>
         <p>
           Most Pointer Events Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
@@ -360,7 +363,7 @@ <h2>
         <p>
           To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional.
 
-          A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period from <span id='cfc'><i class="todo">[pick a duration within:] one week to 10 working days</i></span>, depending on the chair's evaluation of the group consensus on the issue.
+          A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period of <span id='cfc'>one week</span>, depending on the chair's evaluation of the group consensus on the issue.
 
           If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.
         </p>