[e] (0) clarification

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9259 git-svn-id: http://svn.whatwg.org/webapps@4925 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Mar 31, 2010 · de17505 · de17505
1 parent 22420c8
commit de17505
Show file tree

Hide file tree

Showing 3 changed files with 12 additions and 12 deletions.
diff --git a/complete.html b/complete.html
@@ -61143,10 +61143,10 @@ <h3 id=the-hidden-attribute><span class=secno>8.1 </span>The <dfn title=attr-hid
   used to hide content that could legitimately be shown in another
   presentation. For example, it is incorrect to use <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> to hide panels in a tabbed dialog,
   because the tabbed interface is merely a kind of overflow
-  presentation &mdash; showing all the form controls in one big page
-  with a scrollbar would be equivalent, and no less correct. It is
-  similarly incorrect to use this attribute to hide content just from
-  one presentation &mdash; if something is marked <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code>, it is hidden from all
+  presentation &mdash; one could equally well just show all the form
+  controls in one big page with a scrollbar. It is similarly incorrect
+  to use this attribute to hide content just from one presentation
+  &mdash; if something is marked <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code>, it is hidden from all
   presentations, including, for instance, screen readers.</p>
 
   <!-- for example, "<a hidden href=#content>Skip to content</a>" would be inappropriate. -->

diff --git a/index b/index
@@ -61070,10 +61070,10 @@ interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {
   used to hide content that could legitimately be shown in another
   presentation. For example, it is incorrect to use <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> to hide panels in a tabbed dialog,
   because the tabbed interface is merely a kind of overflow
-  presentation &mdash; showing all the form controls in one big page
-  with a scrollbar would be equivalent, and no less correct. It is
-  similarly incorrect to use this attribute to hide content just from
-  one presentation &mdash; if something is marked <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code>, it is hidden from all
+  presentation &mdash; one could equally well just show all the form
+  controls in one big page with a scrollbar. It is similarly incorrect
+  to use this attribute to hide content just from one presentation
+  &mdash; if something is marked <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code>, it is hidden from all
   presentations, including, for instance, screen readers.</p>
 
   <!-- for example, "<a hidden href=#content>Skip to content</a>" would be inappropriate. -->

diff --git a/source b/source
@@ -69059,10 +69059,10 @@ interface <dfn>NavigatorAbilities</dfn> {
   presentation. For example, it is incorrect to use <code
   title="attr-hidden">hidden</code> to hide panels in a tabbed dialog,
   because the tabbed interface is merely a kind of overflow
-  presentation &mdash; showing all the form controls in one big page
-  with a scrollbar would be equivalent, and no less correct. It is
-  similarly incorrect to use this attribute to hide content just from
-  one presentation &mdash; if something is marked <code
+  presentation &mdash; one could equally well just show all the form
+  controls in one big page with a scrollbar. It is similarly incorrect
+  to use this attribute to hide content just from one presentation
+  &mdash; if something is marked <code
   title="attr-hidden">hidden</code>, it is hidden from all
   presentations, including, for instance, screen readers.</p>