--- a/html-data-guide/index.html	Mon Dec 19 11:35:28 2011 +0000
+++ b/html-data-guide/index.html	Mon Dec 19 11:54:06 2011 +0000
@@ -206,13 +206,16 @@
       <dl>
         <dt>Are you able to publish using HTML5?</dt>
         <dd>
-          If you are using a content-management system that doesn't support adding new attributes such as <code>@itemprop</code> or <code>@typeof</code> or if your publishing guidelines require validity against an older version of HTML, then you will be constrained to using microformats. If your publishing guidelines require validity against XHTML, then you might be able to use XHTML+RDFa, depending on how exacting your publishing guidelines are.
+          If you are using a content-management system that doesn't support adding new attributes such as <code>@itemprop</code> or <code>@typeof</code> then you will be constrained to using microformats.
         </dd>
         <dt>Are there development tools available?</dt>
         <dd>
           Because it is not visible within a web page, it can be hard to tell whether HTML data has been written correctly. Consumers should provide validators that enable you to check that your data has been correctly detected and interpreted, but you may also want to consider tool support for generating the HTML data.
         </dd>
       </dl>
+      <p class="note">
+        Microdata requires the use of attributes which are introduced by HTML5 and RDFa can be used with XHTML 1.1 or HTML5, while microformats can be used with all versions of HTML. Your organisation's publishing guidelines may need to be brought up to date to sanction use of microdata or RDFa.
+      </p>
       <p>
         Once you have considered both your target consumers and the tooling support that is available, you will be in one of four situations:
       </p>
@@ -851,7 +854,7 @@
               Error correction in HTML parsing can restructure invalid HTML is restructured to make it valid, for example non-table markup within a table is moved to before the table. This includes <code>link</code> and <code>meta</code> elements that are directly within the <code>table</code> element. You can avoid this restructuring by making sure that your HTML is valid so that it is not needed.
             </li>
             <li>
-              Some older browsers may move <code>meta</code> and/or <code>link</code> elements in the <code>body</code> of an HTML document to within the <code>head</code> element, because they could not validly appear within the body in older versions of HTML. If you are targeting consumers which run within older browsers, such as scripts or extensions, you can avoid this restructuring by using empty <code>span</code> or other elements instead of <code>link</code> or <code>meta</code>; other consumers should be using an up-to-date HTML5 parser which will not do this.
+              Firefox 3.5 and 3.6 move <code>meta</code> elements in the <code>body</code> of an HTML document to within the <code>head</code> element, because they cannot not validly appear within the body in older versions of HTML. If you are targeting consumers which run within these old browsers, such as scripts or extensions, you can avoid this restructuring by using empty <code>span</code> or other elements instead of <code>link</code> or <code>meta</code>; other consumers should be using an up-to-date HTML5 parser which will not do this.
             </li>
           </ul>
         </section>