[e] (0) typo

git-svn-id: http://svn.whatwg.org/webapps@6086 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · May 5, 2011 · 41335e0 · 41335e0
1 parent a941af9
commit 41335e0
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 6 deletions.
diff --git a/complete.html b/complete.html
@@ -7076,7 +7076,7 @@ <h4 id=content-type-sniffing><span class=secno>2.7.3 </span>Determining the type
 
   <p>The <dfn id=content-type-sniffing:-image title="Content-Type sniffing: image">rules for sniffing
   images specifically</dfn> and the <dfn id=content-type-sniffing:-text-or-binary title="Content-Type sniffing:
-  text or binary">rules for distingushing if a resource is text or
+  text or binary">rules for distinguishing if a resource is text or
   binary</dfn> are also defined in the Media Type Sniffing
   specification. Both sets of rules return a <a href=#mime-type>MIME type</a> as
   their result. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
@@ -24784,7 +24784,7 @@ <h4 id=the-object-element><span class=secno>4.8.4 </span>The <dfn><code>object</
             resource's Content-Type metadata</a> is
             "<code>text/plain</code>", and the result of applying the
             <a href=#content-type-sniffing:-text-or-binary title="Content-Type sniffing: text or binary">rules
-            for distingushing if a resource is text or binary</a>
+            for distinguishing if a resource is text or binary</a>
             to the resource is that the resource is not
             <code>text/plain</code>, then set <var title="">binary</var> to true.</p>
 

diff --git a/index b/index
@@ -7101,7 +7101,7 @@ explained in the previous section, which talks about RFC 2119. -->
 
   <p>The <dfn id=content-type-sniffing:-image title="Content-Type sniffing: image">rules for sniffing
   images specifically</dfn> and the <dfn id=content-type-sniffing:-text-or-binary title="Content-Type sniffing:
-  text or binary">rules for distingushing if a resource is text or
+  text or binary">rules for distinguishing if a resource is text or
   binary</dfn> are also defined in the Media Type Sniffing
   specification. Both sets of rules return a <a href=#mime-type>MIME type</a> as
   their result. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
@@ -24812,7 +24812,7 @@ href="?audio"&gt;audio&lt;/a&gt; test instead.)&lt;/p&gt;</pre>
             resource's Content-Type metadata</a> is
             "<code>text/plain</code>", and the result of applying the
             <a href=#content-type-sniffing:-text-or-binary title="Content-Type sniffing: text or binary">rules
-            for distingushing if a resource is text or binary</a>
+            for distinguishing if a resource is text or binary</a>
             to the resource is that the resource is not
             <code>text/plain</code>, then set <var title="">binary</var> to true.</p>
 

diff --git a/source b/source
@@ -6879,7 +6879,7 @@ is conforming depends on which specs apply, and leaves it at that. -->
 
   <p>The <dfn title="Content-Type sniffing: image">rules for sniffing
   images specifically</dfn> and the <dfn title="Content-Type sniffing:
-  text or binary">rules for distingushing if a resource is text or
+  text or binary">rules for distinguishing if a resource is text or
   binary</dfn> are also defined in the Media Type Sniffing
   specification. Both sets of rules return a <span>MIME type</span> as
   their result. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></p>
@@ -26748,7 +26748,7 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
             resource's Content-Type metadata</span> is
             "<code>text/plain</code>", and the result of applying the
             <span title="Content-Type sniffing: text or binary">rules
-            for distingushing if a resource is text or binary</span>
+            for distinguishing if a resource is text or binary</span>
             to the resource is that the resource is not
             <code>text/plain</code>, then set <var
             title="">binary</var> to true.</p>