Fix headings, improve :read-write wording

Author: fantasai

selectors4/Overview.html

@@ -15,13 +15,13 @@
 
    <h1 id=title>Selectors Level 4</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 10 August 2011</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 12 August 2011</h2>
 
    <dl>
     <dt>This version:
 
-    <dd> <!-- <a href="http://www.w3.org/TR/2011/ED-selectors4-20110810/">
-             http://www.w3.org/TR/2011/WD-selectors4-20110810</a> -->
+    <dd> <!-- <a href="http://www.w3.org/TR/2011/ED-selectors4-20110812/">
+             http://www.w3.org/TR/2011/WD-selectors4-20110812</a> -->
      <a href="http://dev.w3.org/csswg/selectors4">
      http://dev.w3.org/csswg/selectors4</a>
 
@@ -298,14 +298,14 @@ <h2 class="no-num no-toc" id=contents>Table of contents</h2>
      <li><a href="#pseudo-range"><span class=secno>11.6. </span> The range
       pseudo-classes <code>:in-range</code> and
       <code>:out-of-range</code></a>
-      <ul class=toc>
-       <li><a href="#pseudo-required-value"><span class=secno>11.6.1.
-        </span><span>:required</span> and <span>:optional</span></a>
 
-       <li><a href="#pseudo-ro-rw"><span class=secno>11.6.2. </span> The
-        mutability pseudo-classes <code>:read-only</code> and
-        <code>:read-write</code></a>
-      </ul>
+     <li><a href="#pseudo-required-value"><span class=secno>11.7. </span> The
+      optionality pseudo-classes <code>:required</code> and
+      <code>:optional</code></a>
+
+     <li><a href="#pseudo-ro-rw"><span class=secno>11.8. </span> The
+      alterability pseudo-classes <code>:read-only</code> and
+      <code>:read-write</code></a>
     </ul>
 
    <li><a href="#structural-pseudos"><span class=secno>12. </span>
@@ -2315,31 +2315,31 @@ <h3 id=pseudo-range><span class=secno>11.6. </span> The range
    <code>:in-range</code> nor <code>:out-of-range</code>. E.g. a slider
    element with a value of 11 presented as a slider control that only
    represents the values from 1-10 is :out-of-range. Another example is a
-   menu element with a value of "E" that happens to be presented as a popup
+   menu element with a value of "E" that happens to be presented in a popup
    menu that only has choices "A", "B" and "C".
 
-  <h4 id=pseudo-required-value><span class=secno>11.6.1. </span><span
-   id=pseudo-required>:required</span> and <span
-   id=pseudo-optional>:optional</span></h4>
+  <h3 id=pseudo-required-value><span class=secno>11.7. </span> The
+   optionality pseudo-classes <code id=pseudo-required>:required</code> and
+   <code id=pseudo-optional>:optional</code></h3>
 
   <p>A form element is <code>:required</code> or <code>:optional<code> if a
    value for it is, respectively, required or optional before the form it
    belongs to can be validly submitted. Elements that are not form elements
    are neither required nor optional. </code></code>
 
-  <h4 id=pseudo-ro-rw><span class=secno>11.6.2. </span> The mutability
+  <h3 id=pseudo-ro-rw><span class=secno>11.8. </span> The alterability
    pseudo-classes <code id=pseudo-read-only>:read-only</code> and <code
-   id=pseudo-read-write>:read-write</code></h4>
+   id=pseudo-read-write>:read-write</code></h3>
 
   <p>An element whose contents are not user-alterable is
    <code>:read-only</code>. However, elements whose contents are
    user-alterable (such as text input fields) are considered to be in a
    :read-write state. In typical documents, most elements are
-   <code>:read-only</code>. However it may be possible (e.g. in the context
-   of an editor) for any element to become <code>:read-write</code>.
-
-  <p class=issue>I don't think it makes sense for an editor to match
-   selectors differently because it is an editor rather than a renderer.
+   <code>:read-only</code>. However it may be possible, depending on the
+   document language, for any element to become <code>:read-write</code>. For
+   example, in HTML5 any element with the <code>contenteditable</code>
+   attribute set to the true state is considered user-alterable. <a
+   href="#HTML5" rel=biblioentry>[HTML5]<!--{{HTML5}}--></a>
 
   <h2 id=structural-pseudos><span class=secno>12. </span> Tree-Structural
    pseudo-classes</h2>

selectors4/Overview.src.html

@@ -1762,30 +1762,30 @@ <h3 id="pseudo-range">
   E.g. a slider element with a value of 11 presented as a slider control
   that only represents the values from 1-10 is :out-of-range.  Another
   example is a menu element with a value of "E" that happens to be
-  presented as a popup menu that only has choices "A", "B" and "C".
+  presented in a popup menu that only has choices "A", "B" and "C".
 
-<h4 id="pseudo-required-value"><span id="pseudo-required">:required</span> 
-and <span id="pseudo-optional">:optional</span></h4>
+<h3 id="pseudo-required-value">
+The optionality pseudo-classes <code id="pseudo-required">:required</code> 
+and <code id="pseudo-optional">:optional</code></h3>
 
   <p>A form element is <code>:required</code> or <code>:optional<code>
   if a value for it is, respectively, required or optional before the
   form it belongs to can be validly submitted. Elements that are not
   form elements are neither required nor optional.
 
-<h4 id="pseudo-ro-rw">
-The mutability pseudo-classes <code id="pseudo-read-only">:read-only</code> 
-and <code id="pseudo-read-write">:read-write</code></h4>
+<h3 id="pseudo-ro-rw">
+The alterability pseudo-classes <code id="pseudo-read-only">:read-only</code> 
+and <code id="pseudo-read-write">:read-write</code></h3>
 
   <p>An element whose contents are not user-alterable is
   <code>:read-only</code>.  However, elements whose contents are
   user-alterable (such as text input fields) are considered to be
   in a :read-write state.  In typical documents, most elements are
-  <code>:read-only</code>. However it may be possible (e.g. in the
-  context of an editor) for any element to become <code>:read-write</code>.</p>
-
-  <p class="issue">I don't think it makes sense for an editor to
-  match selectors differently because it is an editor rather than
-  a renderer.
+  <code>:read-only</code>. However it may be possible, depending
+  on the document language, for any element to become
+  <code>:read-write</code>. For example, in HTML5 any element with
+  the <code>contenteditable</code> attribute set to the true state
+  is considered user-alterable. [[HTML5]]
 
 <h2 id=structural-pseudos>
 Tree-Structural pseudo-classes</h2>