[e] (0) wording fix; internal comment

git-svn-id: http://svn.whatwg.org/webapps@6338 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Jul 29, 2011 · 46b5f60 · 46b5f60
1 parent e16649e
commit 46b5f60
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 6 deletions.
diff --git a/complete.html b/complete.html
@@ -46896,7 +46896,7 @@ <h6 id=the-list-attribute><span class=secno>4.10.7.2.3 </span>The <code title=at
    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>&lt;p&gt;
@@ -74111,7 +74111,7 @@ <h4 id=implementation-notes><span class=secno>8.8.6 </span>Implementation notes<
 
 <!--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

diff --git a/index b/index
@@ -46768,7 +46768,7 @@ interface <dfn id=htmlformelement>HTMLFormElement</dfn> : <a href=#htmlelement>H
    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>&lt;p&gt;
@@ -74009,7 +74009,7 @@ interface <dfn>FunctionObjectCallback</dfn> {
 
 <!--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

diff --git a/source b/source
@@ -52402,7 +52402,7 @@ interface <dfn>HTMLFormElement</dfn> : <span>HTMLElement</span> {
    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 @@ interface <dfn>FunctionObjectCallback</dfn> {
 
 <!--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