[html5] r7503 - [e] (0) Fix some typos or copypasta. Fixing https://www.w3.org/Bugs/Public/show_ [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2012-11-05 12:14:10 -0800 (Mon, 05 Nov 2012)
New Revision: 7503

Modified:
   complete.html
   index
   source
Log:
[e] (0) Fix some typos or copypasta.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=19838
Affected topics: DOM APIs

Modified: complete.html
===================================================================
--- complete.html	2012-11-02 22:32:30 UTC (rev 7502)
+++ complete.html	2012-11-05 20:14:10 UTC (rev 7503)
@@ -248,7 +248,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 2 November 2012</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 5 November 2012</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -86683,7 +86683,7 @@
 
   <p>Broadcasting to many ports is in principle relatively simple: keep an array of
   <code><a href=#messageport>MessagePort</a></code> objects to send messages to, and iterate through the array to send a
-  message. However, this has one rather unfortuante effect: it prevents the ports from being garbage
+  message. However, this has one rather unfortunate effect: it prevents the ports from being garbage
   collected, even if the other side has gone away.</p>
 
   <p>To avoid this problem, the <code><a href=#portcollection>PortCollection</a></code> object can be used. It acts as an opaque

Modified: index
===================================================================
--- index	2012-11-02 22:32:30 UTC (rev 7502)
+++ index	2012-11-05 20:14:10 UTC (rev 7503)
@@ -248,7 +248,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 2 November 2012</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 5 November 2012</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -86683,7 +86683,7 @@
 
   <p>Broadcasting to many ports is in principle relatively simple: keep an array of
   <code><a href=#messageport>MessagePort</a></code> objects to send messages to, and iterate through the array to send a
-  message. However, this has one rather unfortuante effect: it prevents the ports from being garbage
+  message. However, this has one rather unfortunate effect: it prevents the ports from being garbage
   collected, even if the other side has gone away.</p>
 
   <p>To avoid this problem, the <code><a href=#portcollection>PortCollection</a></code> object can be used. It acts as an opaque

Modified: source
===================================================================
--- source	2012-11-02 22:32:30 UTC (rev 7502)
+++ source	2012-11-05 20:14:10 UTC (rev 7503)
@@ -100823,7 +100823,7 @@
 
   <p>Broadcasting to many ports is in principle relatively simple: keep an array of
   <code>MessagePort</code> objects to send messages to, and iterate through the array to send a
-  message. However, this has one rather unfortuante effect: it prevents the ports from being garbage
+  message. However, this has one rather unfortunate effect: it prevents the ports from being garbage
   collected, even if the other side has gone away.</p>
 
   <p>To avoid this problem, the <code>PortCollection</code> object can be used. It acts as an opaque