[html5] r6338 - [e] (0) wording fix; internal comment

[whatwg at whatwg.org]

Author: ianh
Date: 2011-07-28 18:41:50 -0700 (Thu, 28 Jul 2011)
New Revision: 6338

Modified:
   complete.html
   index
   source
Log:
[e] (0) wording fix; internal comment

Modified: complete.html
===================================================================
--- complete.html	2011-07-29 00:26:38 UTC (rev 6337)
+++ complete.html	2011-07-29 01:41:50 UTC (rev 6338)
@@ -46896,7 +46896,7 @@
    important to the content, then simply using a <code><a href=#the-datalist-element>datalist</a></code>
    element with children <code><a href=#the-option-element>option</a></code> elements is enough. To
    prevent the values from being rendered in legacy user agents, they
-   should be placed inside the <code title=attr-option-value><a href=#attr-option-value>value</a></code> attribute instead of
+   need to be placed inside the <code title=attr-option-value><a href=#attr-option-value>value</a></code> attribute instead of
    inline.</p>
 
    <pre><p>
@@ -74111,7 +74111,7 @@
 
 <!--FIND-->
 
-  <h3 id=text-search-apis><span class=secno>8.9 </span>Text search APIs</h3>
+  <h3 id=text-search-apis><span class=secno>8.9 </span>Text search APIs</h3> <!-- window.find() -->
 
   <p class=critical>This legacy API is not very interoperably
   implemented, and has a number of design problems (such as having six

Modified: index
===================================================================
--- index	2011-07-29 00:26:38 UTC (rev 6337)
+++ index	2011-07-29 01:41:50 UTC (rev 6338)
@@ -46768,7 +46768,7 @@
    important to the content, then simply using a <code><a href=#the-datalist-element>datalist</a></code>
    element with children <code><a href=#the-option-element>option</a></code> elements is enough. To
    prevent the values from being rendered in legacy user agents, they
-   should be placed inside the <code title=attr-option-value><a href=#attr-option-value>value</a></code> attribute instead of
+   need to be placed inside the <code title=attr-option-value><a href=#attr-option-value>value</a></code> attribute instead of
    inline.</p>
 
    <pre><p>
@@ -74009,7 +74009,7 @@
 
 <!--FIND-->
 
-  <h3 id=text-search-apis><span class=secno>8.9 </span>Text search APIs</h3>
+  <h3 id=text-search-apis><span class=secno>8.9 </span>Text search APIs</h3> <!-- window.find() -->
 
   <p class=critical>This legacy API is not very interoperably
   implemented, and has a number of design problems (such as having six

Modified: source
===================================================================
--- source	2011-07-29 00:26:38 UTC (rev 6337)
+++ source	2011-07-29 01:41:50 UTC (rev 6338)
@@ -52402,7 +52402,7 @@
    important to the content, then simply using a <code>datalist</code>
    element with children <code>option</code> elements is enough. To
    prevent the values from being rendered in legacy user agents, they
-   should be placed inside the <code
+   need to be placed inside the <code
    title="attr-option-value">value</code> attribute instead of
    inline.</p>
 
@@ -84536,7 +84536,7 @@
 
 <!--FIND-->
 
-  <h3>Text search APIs</h3>
+  <h3>Text search APIs</h3> <!-- window.find() -->
 
   <p class="critical">This legacy API is not very interoperably
   implemented, and has a number of design problems (such as having six