html5/spec Overview.html,1.4224,1.4225

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv18437

Modified Files:
	Overview.html 
Log Message:
referenced spec name change update (whatwg r5302)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4224
retrieving revision 1.4225
diff -u -d -r1.4224 -r1.4225
--- Overview.html	16 Aug 2010 21:39:04 -0000	1.4224
+++ Overview.html	16 Aug 2010 21:47:19 -0000	1.4225
@@ -5608,27 +5608,27 @@
 
   <p>The <dfn id="content-type" title="Content-Type">Content-Type metadata</dfn> of a
   resource must be obtained and interpreted in a manner consistent
-  with the requirements of the Content-Type Processing Model
+  with the requirements of the Media Type Sniffing
   specification. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></p>
 
   <p>The <dfn id="content-type-sniffing-0" title="Content-Type sniffing">sniffed type of a
   resource</dfn> must be found in a manner consistent with the
-  requirements given in the Content-Type Processing Model
+  requirements given in the Media Type Sniffing
   specification for finding the <i>sniffed-type</i> of the relevant
   sequence of octets. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></p>
 
   <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
-  binary</dfn> are also defined in the Content-Type Processing Model
+  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>
 
   <p class="warning">It is imperative that the rules in the
-  Content-Type Processing Model specification be followed
+  Media Type Sniffing specification be followed
   exactly. When a user agent uses different heuristics for content
   type detection than the server expects, security problems can
-  occur. For more details, see the Content-Type Processing Model
+  occur. For more details, see the Media Type Sniffing
   specification. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></p>
 
   <p>The <dfn id="algorithm-for-extracting-an-encoding-from-a-content-type">algorithm for extracting an encoding from a
@@ -64645,7 +64645,7 @@
     <dl><dt>Magic number(s):</dt>
      <dd>No sequence of bytes can uniquely identify an HTML
      document. More information on detecting HTML documents is
-     available in the Content-Type Processing Model specification. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></dd>
+     available in the Media Type Sniffing specification. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></dd>
      <dt>File extension(s):</dt>
      <dd>"<code title="">html</code>" and "<code title="">htm</code>"
      are commonly, but certainly not exclusively, used as the
@@ -67935,8 +67935,8 @@
    N. Poppelier. W3C.</dd>
 
    <dt id="refsMIMESNIFF">[MIMESNIFF]</dt>
-   <dd><cite><a href="http://tools.ietf.org/html/draft-abarth-mime-sniff">Content-Type
-   Processing Model</a></cite>, A. Barth, I. Hickson. IETF.</dd>
+   <dd><cite><a href="http://tools.ietf.org/html/draft-abarth-mime-sniff">Media
+   Type Sniffing</a></cite>, A. Barth, I. Hickson. IETF.</dd>
 
    <dt id="refsMQ">[MQ]</dt>
    <!--

Received on Monday, 16 August 2010 21:47:25 UTC