[e] (0) typo

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=8055 git-svn-id: http://svn.whatwg.org/webapps@4352 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Oct 27, 2009 · 060dbab · 060dbab
1 parent 67be4eb
commit 060dbab
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/complete.html b/complete.html
@@ -70069,7 +70069,7 @@ <h5 id=determining-the-character-encoding><span class=secno>11.2.2.1 </span>Dete
   <p class=note>This algorithm is a <a href=#willful-violation>willful violation</a>
   of the HTTP specification, which requires that the encoding be
   assumed to be ISO-8859-1 in the absence of a <a href=#character-encoding-declaration>character
-  encoding declaration</a> to the contrary, and of the RFC 2046,
+  encoding declaration</a> to the contrary, and of RFC 2046,
   which requires that the encoding be assumed to be US-ASCII in the
   absence of a <a href=#character-encoding-declaration>character encoding declaration</a> to the
   contrary. This specification's third approach is motivated by a

diff --git a/index b/index
@@ -61040,7 +61040,7 @@ interface <dfn id=messageport>MessagePort</dfn> {
   <p class=note>This algorithm is a <a href=#willful-violation>willful violation</a>
   of the HTTP specification, which requires that the encoding be
   assumed to be ISO-8859-1 in the absence of a <a href=#character-encoding-declaration>character
-  encoding declaration</a> to the contrary, and of the RFC 2046,
+  encoding declaration</a> to the contrary, and of RFC 2046,
   which requires that the encoding be assumed to be US-ASCII in the
   absence of a <a href=#character-encoding-declaration>character encoding declaration</a> to the
   contrary. This specification's third approach is motivated by a

diff --git a/source b/source
@@ -78869,7 +78869,7 @@ interface <dfn>MessagePort</dfn> {
   <p class="note">This algorithm is a <span>willful violation</span>
   of the HTTP specification, which requires that the encoding be
   assumed to be ISO-8859-1 in the absence of a <span>character
-  encoding declaration</span> to the contrary, and of the RFC 2046,
+  encoding declaration</span> to the contrary, and of RFC 2046,
   which requires that the encoding be assumed to be US-ASCII in the
   absence of a <span>character encoding declaration</span> to the
   contrary. This specification's third approach is motivated by a