--- a/discovery-api/WD-20130905.html	Mon Sep 02 21:40:23 2013 +0200
+++ b/discovery-api/WD-20130905.html	Thu Sep 05 15:52:22 2013 +0200
@@ -269,10 +269,11 @@
               </p>
 
             <p>
-              This version of the specification is an update to the previously published <a href="http://www.w3.org/TR/2012/WD-discovery-api-20130404/">4th April 2013 Working Draft</a> version of the same document. A full <a href="#change-log">change log</a> is available for this specification.
+              This version of the specification is an update to the previously published <a href="http://www.w3.org/TR/2012/WD-discovery-api-20130404/">4th April 2013 Working Draft</a> version of the same document.
+            </p>
 
             <p>
-              This document represents the early consensus of the group on the scope and features of the proposed <abbr title="Application Programming Interface">API</abbr>.
+              A full <a href="#change-log">change log</a> is available for this specification. Significant changes from the previously published working draft include adding DIAL support, using Promises, adding privacy and security considerations, and other technical clarifications.
             </p>
 
               <p>
@@ -384,9 +385,7 @@
         Introduction
       </h2><p><em>This section is non-normative.</em></p>
       <p>
-        To enable Web pages to connect and communicate with Local-networked Services provided over <abbr title="Hypertext Transfer Protocol">HTTP</abbr>, this
-        specification introduces the <a href="#navigatornetworkservice"><code>NavigatorNetworkService</code></a>
-        interface.
+        This specification defines the <a href="#navigatornetworkservice"><code>NavigatorNetworkService</code></a> interface to enable Web pages to connect and communicate with Local-networked Services provided over HTTP. This enables access to services and content provided by home network devices, including the discovery and playback of content available to those devices, both from services such as traditional broadcast media and internet based services as well as local services. Initial design goals and requirements provided by the <a href="http://www.w3.org/2011/webtv/">W3C Web &amp; TV interest group</a> are documented in <a href="#bib-hnreq">[hnreq]</a>.
       </p>
       <p>
         Using this <abbr title="Application Programming Interface">API</abbr> consists of requesting a well-known
@@ -1127,7 +1126,7 @@
           service type</a> of the service.
         </p>
         <p>
-          The <dfn id="dom-networkservice-url"><code>url</code></dfn> attribute is an <a href="http://www.w3.org/TR/html5/urls.html#absolute-url" class="externalDFN">absolute <abbr title="Uniform Resource Locator">URL</abbr></a> pointing to the root <abbr title="Hypertext Transfer Protocol">HTTP</abbr> endpoint for the service that has been
+          The <dfn id="dom-networkservice-url"><code>url</code></dfn> attribute is an <a href="http://url.spec.whatwg.org/#concept-absolute-url" class="externalDFN">absolute <abbr title="Uniform Resource Locator">URL</abbr></a> pointing to the root <abbr title="Hypertext Transfer Protocol">HTTP</abbr> endpoint for the service that has been
              added to the <a href="#dfn-entry-script-origin-s-url-whitelist" class="internalDFN">entry script origin's <abbr title="Uniform Resource Locator">URL</abbr> whitelist</a>. Web pages can subsequently use this value for
              implicit cross-document messaging via various existing mechanisms (e.g. Web Sockets, Server-Sent Events,
              Web Messaging, XMLHttpRequest).
@@ -3000,4 +2999,5 @@
 </dd><dt id="bib-RFC2119">[RFC2119]</dt><dd rel="dcterms:requires">S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119.  URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
 </dd><dt id="bib-UPNP-DEVICEARCH11">[UPNP-DEVICEARCH11]</dt><dd rel="dcterms:requires"><a href="http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.1.pdf"><cite>UPnP Device Architecture 1.1</cite></a>. 15 October 2008. UPnP Forum. PDF document. URL: <a href="http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.1.pdf">http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.1.pdf</a>
 </dd><dt id="bib-WEBIDL">[WEBIDL]</dt><dd rel="dcterms:requires">Cameron McCormack. <a href="http://www.w3.org/TR/WebIDL/"><cite>Web IDL</cite></a>. 19 April 2012. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/WebIDL/">http://www.w3.org/TR/WebIDL/</a>
+</dd></dl></section>  <section id="informative-references" typeof="bibo:Chapter" resource="#informative-references" rel="bibo:chapter"><h3 aria-level="2" role="heading" id="h3_informative-references"><span class="secno">D.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-hnreq">[hnreq]</dt><dd rel="dcterms:requires">Giuseppe Pascale. <a href="http://www.w3.org/TR/hnreq/"><cite>Requirements for Home Networking Scenarios</cite></a>. 01 December 2011. URL: <a href="http://www.w3.org/TR/hnreq/">http://www.w3.org/TR/hnreq/</a>
 </dd></dl></section></section></body></html>
\ No newline at end of file