--- a/hnreq/hnreq.html	Wed Nov 23 10:39:12 2011 +0100
+++ b/hnreq/hnreq.html	Wed Nov 23 10:43:21 2011 +0100
@@ -50,7 +50,7 @@
     </section>
 
     <section id="sotd">
-      <p>Recommendations in this document are the result of discussion in the Home Network Task Force of the Web and TV Interest Group. The Home Network Task Force believes that most of these recommendations listed in this document will be refined and addressed within the Device APIs Working Group, as part of its work on a devices and services discovery API standard. In particular, while the Home Network Task Force may continue to discuss areas of home networking scenarios that have not already been raised in this document, it does not anticipate further work on the scenarios and requirements highlighted in this document within the Web and TV Interest Group.</p>
+      <p>Recommendations in this document are the result of discussions in the Home Network Task Force of the Web and TV Interest Group. The Home Network Task Force believes that most of these recommendations listed in this document will be refined and addressed within the Device APIs Working Group, as part of its work on a devices and services discovery API standard. In particular, while the Home Network Task Force may continue to discuss areas of home networking scenarios that have not already been raised in this document, it does not anticipate further work on the scenarios and requirements highlighted in this document within the Web and TV Interest Group.</p>
     </section>
 
     <section>
@@ -989,7 +989,7 @@
               <li>report an estimate of the timing synchronism accuracy that is achievable</li>
               <li>provide synchronization to within lip-sync accuracy if all devices involved support it</li>
             </ul>
-            <p>The processing engine that implements the API may utilize existing home networking protocols to achieve the required accuracy. A likely necessary component will be the synchronization of clocks between the television or media rendering device and the device on which the application is running. Possible protocols that might be used to achieve this include: Precision Time Protocol (IEEE 1588-2002) [[IEEE1588]], IEEE 802.11AS @@@ [[IEEE802]], UPnP Precision Time Synchronization @@@ [[UPNP-AV4]].</p>
+            <p>The processing engine that implements the API may utilize existing home networking protocols to achieve the required accuracy. A likely necessary component will be the synchronization of clocks between the television or media rendering device and the device on which the application is running. Possible protocols that might be used to achieve this include: Precision Time Protocol (IEEE 1588-2002) [[IEEE1588]], IEEE 802.1AS [[IEEE802-1AS]], UPnP Precision Time Synchronization [[UPNP-AVT3]].</p>
             <p>Applications will benefit if the API presents a simple unified set of functions such that the application does not need know which protocols are being used.</p>
             <p>Scenario: An application plays alternative audio that is time synchronized to a programme that the user is watching. The synchronization is sufficiently accurate to maintain 'lip-sync' between the alternative audio and the programme video. The alternative audio may be delivered to the application independently of the television device - such as via a direct stream from a broadcaster's internet based server.</p>
           </dd>