--- a/light/Overview.html	Thu May 23 10:00:57 2013 -0400
+++ b/light/Overview.html	Mon May 27 09:20:54 2013 +0300
@@ -391,7 +391,7 @@
   </p>
   <h1 class="title p-name" id="title">Ambient Light Events</h1>
   
-  <h2 id="w3c-editor-s-draft-21-may-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2013-05-21">21 May 2013</time></h2>
+  <h2 id="w3c-editor-s-draft-27-may-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2013-05-27">27 May 2013</time></h2>
   <dl>
     
       <dt>This version:</dt>
@@ -590,7 +590,7 @@
     <section class="informative" id="security-and-privacy-considerations">
       <!--OddPage--><h2><span class="secno">4. </span>Security and privacy considerations</h2><p><em>This section is non-normative.</em></p>
       <p>
-        Privacy threats can arise when this specification is used in
+        Privacy risks can arise when this specification is used in
         combination with other functionality or when used over time,
         specifically with the risk of correlation of data and user
         identification through fingerprinting. Web application developers
@@ -607,7 +607,7 @@
         event rates available to web application developers.
       </p>
       <p>
-        If the same JavasScript code using the API can be used simultaneously in
+        If the same JavaScript code using the API can be used simultaneously in
         different window contexts on the same device it may be possible for
         that code to correlate the user across those two contexts, creating
         unanticipated tracking mechanisms.
@@ -850,7 +850,7 @@
     </section>
   
 
-<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">B. </span>References</h2><section id="normative-references"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-DOM4">[DOM4]</dt><dd>Anne van Kesteren; Aryeh Gregor; Lachlan Hunt; Ms2ger. <a href="http://www.w3.org/TR/2012/WD-dom-20121206"><cite>DOM4</cite></a>. 6 December 2012. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2012/WD-dom-20121206">http://www.w3.org/TR/2012/WD-dom-20121206</a>
+<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">B. </span>References</h2><section id="normative-references"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-DOM4">[DOM4]</dt><dd>Anne van Kesteren; Aryeh Gregor; Lachlan Hunt; Ms2ger. <a href="http://www.w3.org/TR/dom/"><cite>DOM4</cite></a>. 6 December 2012. W3C Working Draft. URL: <a href="http://www.w3.org/TR/dom/">http://www.w3.org/TR/dom/</a>
 </dd><dt id="bib-HTML5">[HTML5]</dt><dd>Robin Berjon et al. <a href="http://www.w3.org/TR/html5/"><cite>HTML5</cite></a>. 17 December 2012. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a>
 </dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>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></dl></section></section></body></html>
\ No newline at end of file

--- a/light/Overview.src.html	Thu May 23 10:00:57 2013 -0400
+++ b/light/Overview.src.html	Mon May 27 09:20:54 2013 +0300
@@ -116,7 +116,7 @@
     <section class="informative">
       <h2>Security and privacy considerations</h2>
       <p>
-        Privacy threats can arise when this specification is used in
+        Privacy risks can arise when this specification is used in
         combination with other functionality or when used over time,
         specifically with the risk of correlation of data and user
         identification through fingerprinting. Web application developers
@@ -133,7 +133,7 @@
         event rates available to web application developers.
       </p>
       <p>
-        If the same JavasScript code using the API can be used simultaneously in
+        If the same JavaScript code using the API can be used simultaneously in
         different window contexts on the same device it may be possible for
         that code to correlate the user across those two contexts, creating
         unanticipated tracking mechanisms.

--- a/proximity/Overview.html	Thu May 23 10:00:57 2013 -0400
+++ b/proximity/Overview.html	Mon May 27 09:20:54 2013 +0300
@@ -391,7 +391,7 @@
   </p>
   <h1 class="title p-name" id="title">Proximity Events</h1>
   
-  <h2 id="w3c-editor-s-draft-21-may-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2013-05-21">21 May 2013</time></h2>
+  <h2 id="w3c-editor-s-draft-27-may-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2013-05-27">27 May 2013</time></h2>
   <dl>
     
       <dt>This version:</dt>
@@ -623,7 +623,7 @@
     <section class="informative" id="security-and-privacy-considerations">
       <!--OddPage--><h2><span class="secno">4. </span>Security and privacy considerations</h2><p><em>This section is non-normative.</em></p>
       <p>
-        Privacy threats can arise when this specification is used in
+        Privacy risks can arise when this specification is used in
         combination with other functionality or when used over time,
         specifically with the risk of correlation of data and user
         identification through fingerprinting. Web application developers
@@ -640,7 +640,7 @@
         application developers.
       </p>
       <p>
-        If the same JavasScript code using the API can be used simultaneously in
+        If the same JavaScript code using the API can be used simultaneously in
         different window contexts on the same device it may be possible for
         that code to correlate the user across those two contexts, creating
         unanticipated tracking mechanisms.
@@ -867,7 +867,7 @@
     </section>
   
 
-<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">B. </span>References</h2><section id="normative-references"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-DOM4">[DOM4]</dt><dd>Anne van Kesteren; Aryeh Gregor; Lachlan Hunt; Ms2ger. <a href="http://www.w3.org/TR/2012/WD-dom-20121206"><cite>DOM4</cite></a>. 6 December 2012. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2012/WD-dom-20121206">http://www.w3.org/TR/2012/WD-dom-20121206</a>
+<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">B. </span>References</h2><section id="normative-references"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-DOM4">[DOM4]</dt><dd>Anne van Kesteren; Aryeh Gregor; Lachlan Hunt; Ms2ger. <a href="http://www.w3.org/TR/dom/"><cite>DOM4</cite></a>. 6 December 2012. W3C Working Draft. URL: <a href="http://www.w3.org/TR/dom/">http://www.w3.org/TR/dom/</a>
 </dd><dt id="bib-HTML5">[HTML5]</dt><dd>Robin Berjon et al. <a href="http://www.w3.org/TR/html5/"><cite>HTML5</cite></a>. 17 December 2012. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a>
 </dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>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></dl></section></section></body></html>
\ No newline at end of file
+</dd></dl></section></section><div style="position: fixed; width: 400px; top: 10px; padding: 1em; border: 5px solid #90b8de; background: #fff"><h4>Save Options</h4><button>Save as HTML</button><button>Save as HTML (Source)</button><button>Save as XHTML</button><button>Save as XHTML (Source)</button></div></body></html>
\ No newline at end of file

--- a/proximity/Overview.src.html	Thu May 23 10:00:57 2013 -0400
+++ b/proximity/Overview.src.html	Mon May 27 09:20:54 2013 +0300
@@ -149,7 +149,7 @@
     <section class="informative">
       <h2>Security and privacy considerations</h2>
       <p>
-        Privacy threats can arise when this specification is used in
+        Privacy risks can arise when this specification is used in
         combination with other functionality or when used over time,
         specifically with the risk of correlation of data and user
         identification through fingerprinting. Web application developers
@@ -166,7 +166,7 @@
         application developers.
       </p>
       <p>
-        If the same JavasScript code using the API can be used simultaneously in
+        If the same JavaScript code using the API can be used simultaneously in
         different window contexts on the same device it may be possible for
         that code to correlate the user across those two contexts, creating
         unanticipated tracking mechanisms.