Skip to content
Permalink
Browse files

[e] (0) never say 'may not' in a spec, RFC2119 doesn't define that; a…

…nd never say 'may' in non-normative content, it's just confusing.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=11645

git-svn-id: http://svn.whatwg.org/webapps@5823 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Feb 3, 2011
1 parent ce67c02 commit 482b2fa6b5429dca58c52160e7420d6e23584104
Showing with 3 additions and 3 deletions.
  1. +1 −1 complete.html
  2. +1 −1 index
  3. +1 −1 source
data in a table is useful to everyone; explaining how to read the
table, if not obvious from the headers alone, is useful to everyone;
describing the structure of the table, if it is easy to grasp
visually, may not be useful to everyone, but it might also not be
visually, might not be useful to everyone, but it might also not be
useful to users who can quickly navigate the table with an
accessibility tool.</p>

2 index
data in a table is useful to everyone; explaining how to read the
table, if not obvious from the headers alone, is useful to everyone;
describing the structure of the table, if it is easy to grasp
visually, may not be useful to everyone, but it might also not be
visually, might not be useful to everyone, but it might also not be
useful to users who can quickly navigate the table with an
accessibility tool.</p>

2 source
data in a table is useful to everyone; explaining how to read the
table, if not obvious from the headers alone, is useful to everyone;
describing the structure of the table, if it is easy to grasp
visually, may not be useful to everyone, but it might also not be
visually, might not be useful to everyone, but it might also not be
useful to users who can quickly navigate the table with an
accessibility tool.</p>

0 comments on commit 482b2fa

Please sign in to comment.
You can’t perform that action at this time.