W3C home > Mailing lists > Public > public-html-diffs@w3.org > November 2011

hixie: Fix capitalisation of 'microformats' to follow official convention. (whatwg r6797)

From: poot <cvsmail@w3.org>
Date: Tue, 01 Nov 2011 01:46:28 -0400
To: public-html-diffs@w3.org
Message-Id: <E1RL7B6-0007TP-Nv@jay.w3.org>
hixie: Fix capitalisation of 'microformats' to follow official
convention. (whatwg r6797)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5438&r2=1.5439&f=h
http://html5.org/tools/web-apps-tracker?from=6796&to=6797

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5438
retrieving revision 1.5439
diff -u -d -r1.5438 -r1.5439
--- Overview.html	1 Nov 2011 03:34:50 -0000	1.5438
+++ Overview.html	1 Nov 2011 05:44:13 -0000	1.5439
@@ -3411,7 +3411,7 @@
    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
@@ -3426,7 +3426,7 @@
 
    <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>
@@ -16988,12 +16988,12 @@
   contents, along with a machine-readable form of those contents in
   the <code title="attr-data-value"><a href="#attr-data-value">value</a></code> attribute.<p>The <dfn id="attr-data-value" title="attr-data-value"><code>value</code></dfn>
   attribute must be present. Its value must be a representation of the
-  element's contents in a machine-readable format.<p>The element can be used for several purposes.<p>When combined with Microformats or the <a href="#microdata">microdata attributes</a> defined in this
+  element's contents in a machine-readable format.<p>The element can be used for several purposes.<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>The element can also, however, be used in conjunction with
   scripts in the page, for when a script has a literal value to store
   alongside a human-readable value. In such cases, the format to be
@@ -17007,7 +17007,7 @@
   </div><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>
 
@@ -42690,7 +42690,7 @@
   the <code title="rel-prev"><a href="#link-type-prev">prev</a></code> keyword.</p>
 
   </div><h5 id="other-link-types"><span class="secno">4.12.4.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>Anyone is free to edit the <span title="">Microformats wiki
+  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>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:<dl><dt>Keyword</dt>
 
@@ -42834,7 +42834,7 @@
 
   </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
@@ -42849,7 +42849,7 @@
   add the value to the Wiki, with the details described above, with
   the "proposed" status.</p>
 
-  </div><p>Types defined as extensions in the <a href="http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions">Microformats
+  </div><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
Received on Tuesday, 1 November 2011 05:48:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 1 November 2011 05:48:35 GMT