--- a/html-data-guide/index.html Sun Dec 18 20:06:13 2011 +0000
+++ b/html-data-guide/index.html Mon Dec 19 11:31:27 2011 +0000
@@ -80,7 +80,7 @@
<body>
<section id='abstract'>
<p>
- Microformats, RDFa and microdata all enable consumers to extract data from HTML pages. This data may be embedded within enhanced search engine results, exposed to users through browser plug-ins, aggregated across websites or used by scripts running within those HTML pages.
+ Microformats, RDFa and microdata all enable consumers to extract data from HTML pages. This data may be embedded within enhanced search engine results, exposed to users through browser extensions, aggregated across websites or used by scripts running within those HTML pages.
</p>
<p>
This guide aims to help publishers and consumers of HTML data use it well. With several <a title="syntax">syntaxes</a> and <a title="vocabulary">vocabularies</a> to choose from, it provides guidance about how to decide which meets the publisher's or consumer's needs. It discusses when it is necessary to mix syntaxes and vocabularies and how to publish and consume data that uses multiple formats. It describes how to create vocabularies that can be used in multiple syntaxes and general best practices about the publication and consumption of HTML data.
@@ -97,7 +97,7 @@
</p>
<ul>
<li>scripting libraries</li>
- <li>browsers and browser plug-ins</li>
+ <li>browsers and browser extensions</li>
<li>general-purpose search engines</li>
<li>vertical or domain-specific search engines</li>
<li>data reusers known and unknown to the publisher of the data</li>
@@ -195,7 +195,7 @@
</p>
<ul>
<li>scripting libraries</li>
- <li>browsers and browser plug-ins</li>
+ <li>browsers and browser extensions</li>
<li>general-purpose search engines</li>
<li>vertical or domain-specific search engines</li>
<li>data reusers with whom you have agreements</li>
@@ -851,7 +851,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 plug-ins, 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.
+ 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.
</li>
</ul>
</section>