Skip to content

Commit

Permalink
[e] (0) Fix some typos or copypasta.
Browse files Browse the repository at this point in the history
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=19838
Affected topics: DOM APIs

git-svn-id: http://svn.whatwg.org/webapps@7503 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Nov 5, 2012
1 parent 65b194c commit dfff023
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 5 deletions.
4 changes: 2 additions & 2 deletions complete.html
Expand Up @@ -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 &mdash; Last Updated 2 November 2012</h2>
<h2 class="no-num no-toc">Living Standard &mdash; 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>
Expand Down Expand Up @@ -86683,7 +86683,7 @@ <h4 id=broadcasting-to-many-ports><span class=secno>10.5.4 </span>Broadcasting t

<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
Expand Down
4 changes: 2 additions & 2 deletions index
Expand Up @@ -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 &mdash; Last Updated 2 November 2012</h2>
<h2 class="no-num no-toc">Living Standard &mdash; 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>
Expand Down Expand Up @@ -86683,7 +86683,7 @@ interface <dfn id=messagechannel>MessageChannel</dfn> {

<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
Expand Down
2 changes: 1 addition & 1 deletion source
Expand Up @@ -100823,7 +100823,7 @@ interface <dfn>MessageChannel</dfn> {

<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
Expand Down

0 comments on commit dfff023

Please sign in to comment.