[e] (0) Fix capitalisation of 'microformats' to follow official conve…

…ntion. Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=14631 git-svn-id: http://svn.whatwg.org/webapps@6797 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Nov 1, 2011 · 7de1874 · 7de1874
1 parent 4881bf5
commit 7de1874
Show file tree

Hide file tree

Showing 3 changed files with 27 additions and 27 deletions.
diff --git a/complete.html b/complete.html
@@ -4172,7 +4172,7 @@ <h4 id=extensibility><span class=secno>2.2.3 </span>Extensibility</h4>
    elements, while using the most applicable existing "real" HTML
    element, so that browsers and other tools that don't know of the
    extension can still support it somewhat well. This is the tack used
-   by Microformats, for example.</li>
+   by microformats, for example.</li>
 
    <li>Authors can include data for inline client-side scripts or
    server-side site-wide scripts to process using the <code title=attr-data-*><a href=#attr-data-*>data-*=""</a></code> attributes. These are
@@ -4187,7 +4187,7 @@ <h4 id=extensibility><span class=secno>2.2.3 </span>Extensibility</h4>
 
    <li>Authors can use the <code title=attr-hyperlink-rel><a href=#attr-hyperlink-rel>rel=""</a></code> mechanism to annotate
    links with specific meanings by registering <a href=#concept-rel-extensions title=concept-rel-extensions>extensions to the predefined set of
-   link types</a>. This is also used by Microformats.</li>
+   link types</a>. This is also used by microformats.</li>
 
    <li>Authors can embed raw data using the <code title=script><a href=#the-script-element>&lt;script type=""&gt;</a></code> mechanism with a custom
    type, for further handling by inline or server-side scripts.</li>
@@ -20491,12 +20491,12 @@ <h4 id=the-data-element><span class=secno>4.6.10 </span>The <dfn><code>data</cod
 
   <p>The element can be used for several purposes.</p>
 
-  <p>When combined with Microformats or the <a href=#microdata>microdata attributes</a> defined in this
+  <p>When combined with microformats or the <a href=#microdata>microdata attributes</a> defined in this
   specification, the element serves to provide both a machine-readable
   value for the purposes of data procesors, and a human-readable value
   for the purposes of rendering in a Web browser. In this case, the
   format to be used in the <code title=attr-data-value><a href=#attr-data-value>value</a></code>
-  attribute is determined by the Microformat or microdata
+  attribute is determined by the microformats or microdata
   vocabulary in use.</p>
 
   <p>The element can also, however, be used in conjunction with
@@ -20516,7 +20516,7 @@ <h4 id=the-data-element><span class=secno>4.6.10 </span>The <dfn><code>data</cod
   <div class=example>
 
    <p>The <code><a href=#the-data-element>data</a></code> element can be used to encode dates, for
-   example in Microformats. The following shows a hypothetical way of
+   example in microformats. The following shows a hypothetical way of
    encoding an event using a variant on hCalendar that uses the
    <code><a href=#the-data-element>data</a></code> element:</p>
 
@@ -56136,9 +56136,9 @@ <h5 id=other-link-types><span class=secno>4.12.5.14 </span>Other link types</h5>
   -->
 
   <p><dfn id=concept-rel-extensions title=concept-rel-extensions>Extensions to the predefined
-  set of link types</dfn> may be registered in the <a href=http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions>Microformats wiki existing-rel-values page</a>. <a href=#refsMFREL>[MFREL]</a></p>
+  set of link types</dfn> may be registered in the <a href=http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions>microformats wiki existing-rel-values page</a>. <a href=#refsMFREL>[MFREL]</a></p>
 
-  <p>Anyone is free to edit the <span title="">Microformats wiki
+  <p>Anyone is free to edit the <span title="">microformats wiki
   existing-rel-values page</span> at any time to add a type. Extension
   types must be specified with the following information:</p>
 
@@ -56284,7 +56284,7 @@ <h5 id=other-link-types><span class=secno>4.12.5.14 </span>Other link types</h5>
 
   </dl><div class=impl>
 
-  <p>Conformance checkers must use the information given on the <span title="">Microformats wiki existing-rel-values page</span> to
+  <p>Conformance checkers must use the information given on the <span title="">microformats wiki existing-rel-values page</span> to
   establish if a value is allowed or not: values defined in this
   specification or marked as "proposed" or "ratified" must be accepted
   when used on the elements for which they apply as described in the
@@ -56301,7 +56301,7 @@ <h5 id=other-link-types><span class=secno>4.12.5.14 </span>Other link types</h5>
 
   </div>
 
-  <p>Types defined as extensions in the <a href=http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions>Microformats
+  <p>Types defined as extensions in the <a href=http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions>microformats
   wiki existing-rel-values page</a> with the status "proposed" or
   "ratified" may be used with the <code title="">rel</code> attribute
   on <code><a href=#the-link-element>link</a></code>, <code><a href=#the-a-element>a</a></code>, and <code><a href=#the-area-element>area</a></code> elements

diff --git a/index b/index
@@ -4172,7 +4172,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
    elements, while using the most applicable existing "real" HTML
    element, so that browsers and other tools that don't know of the
    extension can still support it somewhat well. This is the tack used
-   by Microformats, for example.</li>
+   by microformats, for example.</li>
 
    <li>Authors can include data for inline client-side scripts or
    server-side site-wide scripts to process using the <code title=attr-data-*><a href=#attr-data-*>data-*=""</a></code> attributes. These are
@@ -4187,7 +4187,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
 
    <li>Authors can use the <code title=attr-hyperlink-rel><a href=#attr-hyperlink-rel>rel=""</a></code> mechanism to annotate
    links with specific meanings by registering <a href=#concept-rel-extensions title=concept-rel-extensions>extensions to the predefined set of
-   link types</a>. This is also used by Microformats.</li>
+   link types</a>. This is also used by microformats.</li>
 
    <li>Authors can embed raw data using the <code title=script><a href=#the-script-element>&lt;script type=""&gt;</a></code> mechanism with a custom
    type, for further handling by inline or server-side scripts.</li>
@@ -20491,12 +20491,12 @@ this specification: the &lt;abbr&gt;WHATWG&lt;/abbr&gt; and the
 
   <p>The element can be used for several purposes.</p>
 
-  <p>When combined with Microformats or the <a href=#microdata>microdata attributes</a> defined in this
+  <p>When combined with microformats or the <a href=#microdata>microdata attributes</a> defined in this
   specification, the element serves to provide both a machine-readable
   value for the purposes of data procesors, and a human-readable value
   for the purposes of rendering in a Web browser. In this case, the
   format to be used in the <code title=attr-data-value><a href=#attr-data-value>value</a></code>
-  attribute is determined by the Microformat or microdata
+  attribute is determined by the microformats or microdata
   vocabulary in use.</p>
 
   <p>The element can also, however, be used in conjunction with
@@ -20516,7 +20516,7 @@ this specification: the &lt;abbr&gt;WHATWG&lt;/abbr&gt; and the
   <div class=example>
 
    <p>The <code><a href=#the-data-element>data</a></code> element can be used to encode dates, for
-   example in Microformats. The following shows a hypothetical way of
+   example in microformats. The following shows a hypothetical way of
    encoding an event using a variant on hCalendar that uses the
    <code><a href=#the-data-element>data</a></code> element:</p>
 
@@ -56136,9 +56136,9 @@ fur
   -->
 
   <p><dfn id=concept-rel-extensions title=concept-rel-extensions>Extensions to the predefined
-  set of link types</dfn> may be registered in the <a href=http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions>Microformats wiki existing-rel-values page</a>. <a href=#refsMFREL>[MFREL]</a></p>
+  set of link types</dfn> may be registered in the <a href=http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions>microformats wiki existing-rel-values page</a>. <a href=#refsMFREL>[MFREL]</a></p>
 
-  <p>Anyone is free to edit the <span title="">Microformats wiki
+  <p>Anyone is free to edit the <span title="">microformats wiki
   existing-rel-values page</span> at any time to add a type. Extension
   types must be specified with the following information:</p>
 
@@ -56284,7 +56284,7 @@ fur
 
   </dl><div class=impl>
 
-  <p>Conformance checkers must use the information given on the <span title="">Microformats wiki existing-rel-values page</span> to
+  <p>Conformance checkers must use the information given on the <span title="">microformats wiki existing-rel-values page</span> to
   establish if a value is allowed or not: values defined in this
   specification or marked as "proposed" or "ratified" must be accepted
   when used on the elements for which they apply as described in the
@@ -56301,7 +56301,7 @@ fur
 
   </div>
 
-  <p>Types defined as extensions in the <a href=http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions>Microformats
+  <p>Types defined as extensions in the <a href=http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions>microformats
   wiki existing-rel-values page</a> with the status "proposed" or
   "ratified" may be used with the <code title="">rel</code> attribute
   on <code><a href=#the-link-element>link</a></code>, <code><a href=#the-a-element>a</a></code>, and <code><a href=#the-area-element>area</a></code> elements

diff --git a/source b/source
@@ -3144,7 +3144,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
    elements, while using the most applicable existing "real" HTML
    element, so that browsers and other tools that don't know of the
    extension can still support it somewhat well. This is the tack used
-   by Microformats, for example.</li>
+   by microformats, for example.</li>
 
    <li>Authors can include data for inline client-side scripts or
    server-side site-wide scripts to process using the <code
@@ -3162,7 +3162,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
    title="attr-hyperlink-rel">rel=""</code> mechanism to annotate
    links with specific meanings by registering <span
    title="concept-rel-extensions">extensions to the predefined set of
-   link types</span>. This is also used by Microformats.</li>
+   link types</span>. This is also used by microformats.</li>
 
    <li>Authors can embed raw data using the <code
    title="script">&lt;script type=""></code> mechanism with a custom
@@ -21864,13 +21864,13 @@ this specification: the &lt;abbr>WHATWG&lt;/abbr> and the
 
   <p>The element can be used for several purposes.</p>
 
-  <p>When combined with Microformats or the <a
+  <p>When combined with microformats or the <a
   href="#microdata">microdata attributes</a> defined in this
   specification, the element serves to provide both a machine-readable
   value for the purposes of data procesors, and a human-readable value
   for the purposes of rendering in a Web browser. In this case, the
   format to be used in the <code title="attr-data-value">value</code>
-  attribute is determined by the Microformat or microdata
+  attribute is determined by the microformats or microdata
   vocabulary in use.</p>
 
   <p>The element can also, however, be used in conjunction with
@@ -21891,7 +21891,7 @@ this specification: the &lt;abbr>WHATWG&lt;/abbr> and the
   <div class="example">
 
    <p>The <code>data</code> element can be used to encode dates, for
-   example in Microformats. The following shows a hypothetical way of
+   example in microformats. The following shows a hypothetical way of
    encoding an event using a variant on hCalendar that uses the
    <code>data</code> element:</p>
 
@@ -63282,10 +63282,10 @@ fur
 
   <p><dfn title="concept-rel-extensions">Extensions to the predefined
   set of link types</dfn> may be registered in the <a
-  href="http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions">Microformats wiki existing-rel-values page</a>. <a
+  href="http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions">microformats wiki existing-rel-values page</a>. <a
   href="#refsMFREL">[MFREL]</a></p>
 
-  <p>Anyone is free to edit the <span title="">Microformats wiki
+  <p>Anyone is free to edit the <span title="">microformats wiki
   existing-rel-values page</span> at any time to add a type. Extension
   types must be specified with the following information:</p>
 
@@ -63449,7 +63449,7 @@ fur
   <div class="impl">
 
   <p>Conformance checkers must use the information given on the <span
-  title="">Microformats wiki existing-rel-values page</span> to
+  title="">microformats wiki existing-rel-values page</span> to
   establish if a value is allowed or not: values defined in this
   specification or marked as "proposed" or "ratified" must be accepted
   when used on the elements for which they apply as described in the
@@ -63467,7 +63467,7 @@ fur
   </div>
 
   <p>Types defined as extensions in the <a
-  href="http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions">Microformats
+  href="http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions">microformats
   wiki existing-rel-values page</a> with the status "proposed" or
   "ratified" may be used with the <code title="">rel</code> attribute
   on <code>link</code>, <code>a</code>, and <code>area</code> elements