[html5] r5823 - [e] (0) never say 'may not' in a spec, RFC2119 doesn't define that; and never sa [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2011-02-03 13:01:06 -0800 (Thu, 03 Feb 2011)
New Revision: 5823

Modified:
   complete.html
   index
   source
Log:
[e] (0) never say 'may not' in a spec, RFC2119 doesn't define that; and never say 'may' in non-normative content, it's just confusing.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=11645

Modified: complete.html
===================================================================
--- complete.html	2011-02-03 20:59:18 UTC (rev 5822)
+++ complete.html	2011-02-03 21:01:06 UTC (rev 5823)
@@ -35951,7 +35951,7 @@
   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>
 

Modified: index
===================================================================
--- index	2011-02-03 20:59:18 UTC (rev 5822)
+++ index	2011-02-03 21:01:06 UTC (rev 5823)
@@ -35933,7 +35933,7 @@
   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>
 

Modified: source
===================================================================
--- source	2011-02-03 20:59:18 UTC (rev 5822)
+++ source	2011-02-03 21:01:06 UTC (rev 5823)
@@ -39779,7 +39779,7 @@
   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>