Fix a few typos and switch to more typical W3C-RFC2119 style.

Author: dbaron

css3-conditional/Overview.html

@@ -17,13 +17,13 @@
 
    <h1>CSS Conditional Rules Module Level 3</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 4 June 2011</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 5 June 2011</h2>
 
    <dl>
     <dt>This version:
 
-    <dd><a href="http://www.w3.org/TR/2011/ED-css3-conditional-20110604/">
-     http://www.w3.org/TR/2011/ED-css3-conditional-20110604</a>
+    <dd><a href="http://www.w3.org/TR/2011/ED-css3-conditional-20110605/">
+     http://www.w3.org/TR/2011/ED-css3-conditional-20110605</a>
 
     <dt>Latest version:
 
@@ -224,7 +224,7 @@ <h3 id=context><span class=secno>1.1. </span>Background</h3>
    <code>@media</code> rule provides the ability to have media-specific style
    sheets, which is also provided by style sheet linking features such as
    <code>@import</code> and <code>&lt;link&gt;</code>. The restrictions on
-   the contents of <code>@media</code> rules made them less useful; they
+   the contents of <code>@media</code> rules made them less useful; they have
    forced authors using CSS features involving @-rules in media-specific
    style sheets to use separate style sheets for each medium.
 
@@ -245,7 +245,7 @@ <h3 id=context><span class=secno>1.1. </span>Background</h3>
    mechanisms, and for other cases where a set of related styles needs to be
    conditioned on property support.
 
-  <p>The <code>@document</code> rule allows CSS to be condition on the page
+  <p>The <code>@document</code> rule allows CSS to be conditioned on the page
    to which the style sheet is being applied. This allows users to apply
    styles to a particular page or group of pages, which greatly increases the
    power of user style sheets.
@@ -273,10 +273,8 @@ <h3 id=conventions><span class=secno>1.3. </span>Document Conventions</h3>
    NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”,
    “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the
    normative parts of this document are to be interpreted as described in RFC
-   2119.
-   <!--However, for readability, these words do not appear in all uppercase
-  letters in this specification.-->
-   
+   2119. However, for readability, these words do not appear in all uppercase
+   letters in this specification.
 
   <p>All of the text of this specification is normative except sections
    explicitly marked as non-normative, examples, and notes. <a
@@ -326,12 +324,13 @@ <h2 id=processing><span class=secno>2. </span>Processing of conditional
   </div>
 
   <p>Each conditional group rule has a condition, which at any time evaluates
-   to true or false. When the condition is true, CSS processors MUST apply
-   the rules inside the group rule as though they were at the group rule's
-   location; when the condition is false, CSS processors MUST not apply any
-   of rules inside the group rule. The current state of the condition does
-   not affect the CSS object model, in which the contents of the group rule
-   always remain within the group rule.
+   to true or false. When the condition is true, CSS processors
+   <strong>must</strong> apply the rules inside the group rule as though they
+   were at the group rule's location; when the condition is false, CSS
+   processors <strong>must</strong> not apply any of rules inside the group
+   rule. The current state of the condition does not affect the CSS object
+   model, in which the contents of the group rule always remain within the
+   group rule.
 
   <p>This means that when multiple conditional group rules are nested, a rule
    inside of both of them applies only when all of the rules' conditions are
@@ -354,10 +353,10 @@ <h2 id=processing><span class=secno>2. </span>Processing of conditional
    or equal to 12 centimeters.</div>
 
   <p>When the condition for a conditional group rule changes, CSS processors
-   MUST reflect that the rules now apply or no longer apply, except for
-   properties whose definitions define effects of computed values that
-   persist past the lifetime of that value (such as for some properties in <a
-   href="#CSS3-TRANSITIONS"
+   <strong>must</strong> reflect that the rules now apply or no longer apply,
+   except for properties whose definitions define effects of computed values
+   that persist past the lifetime of that value (such as for some properties
+   in <a href="#CSS3-TRANSITIONS"
    rel=biblioentry>[CSS3-TRANSITIONS]<!--{{CSS3-TRANSITIONS}}--></a> and <a
    href="#CSS3-ANIMATIONS"
    rel=biblioentry>[CSS3-ANIMATIONS]<!--{{!CSS3-ANIMATIONS}}--></a>).
@@ -408,13 +407,13 @@ <h2 id=contents><span class=secno>3. </span>Contents of conditional group
    forbidden to occur after some other types of rules should modify this
    <code>nested_statement</code> production to keep the grammar accurate.
 
-  <p>Style sheets MUST NOT use rules other than the allowed ones inside
-   conditional group rules.
+  <p>Style sheets <strong>must not</strong> use rules other than the allowed
+   ones inside conditional group rules.
 
   <h3 id=group-error><span class=secno>3.1. </span>Error handling</h3>
 
-  <p>Implementations MUST ignore rules that are not allowed within a group
-   rule.
+  <p>Implementations <strong>must</strong> ignore rules that are not allowed
+   within a group rule.
 
   <p class=issue>Define error handling rules for unknown things.
 
@@ -437,7 +436,7 @@ <h2 id=at-media><span class=secno>4. </span>Media-specific style sheets:
 
    <p>has the condition <code>print, (max-width: 600px)</code>, which is true
     for print media and for devices whose width is at most 600px. When either
-    of this is true, the condition of the rule is true, and the rule
+    of these is true, the condition of the rule is true, and the rule
     <code>#extra_navigation { display: none }</code> is applied.
   </div>
 
@@ -709,10 +708,10 @@ <h2 id=at-document><span class=secno>6. </span>Document queries: the
    iframe/object/embed/img; it should probably not apply to the URL of an
    svg:use.
 
-  <p>Implementations MUST treat any unknown URL matching functions as a
-   syntax error, and thus ignore the <code>@document</code> rule. <span
-   class=issue>Should we instead have more complicated error handling
-   rules?</span>
+  <p>Implementations <strong>must</strong> treat any unknown URL matching
+   functions as a syntax error, and thus ignore the <code>@document</code>
+   rule. <span class=issue>Should we instead have more complicated error
+   handling rules?</span>
 
   <p>This extends the lexical scanner in the <a
    href="http://www.w3.org/TR/CSS21/grammar.html">Grammar of CSS 2.1</a> (<a

css3-conditional/Overview.src.html

@@ -98,7 +98,7 @@ <h3 id="context">Background</h3>
   have media-specific style sheets, which is also provided by style
   sheet linking features such as <code>@import</code> and
   <code>&lt;link&gt;</code>.  The restrictions on the contents of
-  <code>@media</code> rules made them less useful; they forced authors
+  <code>@media</code> rules made them less useful; they have forced authors
   using CSS features involving @-rules in media-specific style sheets to
   use separate style sheets for each medium.</p>
 
@@ -119,7 +119,7 @@ <h3 id="context">Background</h3>
   mechanisms, and for other cases where a set of related styles needs to
   be conditioned on property support.</p>
 
-  <p>The <code>@document</code> rule allows CSS to be condition on the
+  <p>The <code>@document</code> rule allows CSS to be conditioned on the
   page to which the style sheet is being applied.  This allows users to
   apply styles to a particular page or group of pages, which greatly
   increases the power of user style sheets.</p>
@@ -143,8 +143,8 @@ <h3 id="conventions">Document Conventions</h3>
   “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
   “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
   document are to be interpreted as described in RFC 2119.
-  <!--However, for readability, these words do not appear in all uppercase
-  letters in this specification.-->
+  However, for readability, these words do not appear in all uppercase
+  letters in this specification.
 
   <p>All of the text of this specification is normative except sections
   explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p>
@@ -188,11 +188,12 @@ <h2 id="processing">Processing of conditional group rules</h2>
 
 <p>Each conditional group rule has a condition, which at any time
 evaluates to true or false.  When the condition is true, CSS processors
-MUST apply the rules inside the group rule as though they were at the
-group rule's location; when the condition is false, CSS processors MUST
-not apply any of rules inside the group rule.  The current state of the
-condition does not affect the CSS object model, in which the contents of
-the group rule always remain within the group rule.</p>
+<strong>must</strong> apply the rules inside the group rule as though
+they were at the group rule's location; when the condition is false, CSS
+processors <strong>must</strong> not apply any of rules inside the group
+rule.  The current state of the condition does not affect the CSS object
+model, in which the contents of the group rule always remain within the
+group rule.</p>
 
 <p>This means that when multiple conditional group rules are nested,
 a rule inside of both of them applies only when all of the rules'
@@ -214,11 +215,12 @@ <h2 id="processing">Processing of conditional group rules</h2>
 is applied to print media <em>and</em> the width of the page box is less
 than or equal to 12 centimeters.</div>
 
-<p>When the condition for a conditional group rule changes,
-CSS processors MUST reflect that the rules now apply or no longer apply,
-except for properties whose definitions define effects of computed
-values that persist past the lifetime of that value (such as for some
-properties in [[CSS3-TRANSITIONS]] and [[!CSS3-ANIMATIONS]]).</p>
+<p>When the condition for a conditional group rule changes, CSS
+processors <strong>must</strong> reflect that the rules now apply or no
+longer apply, except for properties whose definitions define effects of
+computed values that persist past the lifetime of that value (such as
+for some properties in [[CSS3-TRANSITIONS]] and
+[[!CSS3-ANIMATIONS]]).</p>
 
 <h2 id="contents">Contents of conditional group rules</h2>
 
@@ -261,13 +263,13 @@ <h2 id="contents">Contents of conditional group rules</h2>
 this <code>nested_statement</code> production to keep the grammar
 accurate.</p>
 
-<p>Style sheets MUST NOT use rules other than the allowed ones inside
+<p>Style sheets <strong>must not</strong> use rules other than the allowed ones inside
 conditional group rules.</p>
 
 <h3 id="group-error">Error handling</h3>
 
-<p>Implementations MUST ignore rules that are not allowed within a group
-rule.</p>
+<p>Implementations <strong>must</strong> ignore rules that are not
+allowed within a group rule.</p>
 
 <p class="issue">Define error handling rules for unknown things.</p>
 
@@ -286,7 +288,7 @@ <h2 id="at-media">Media-specific style sheets:  the <code>@media</code> rule</h2
 }</pre>
 <p>has the condition <code>print, (max-width: 600px)</code>, which is
 true for print media and for devices whose width is at most 600px.  When
-either of this is true, the condition of the rule is true, and the rule
+either of these is true, the condition of the rule is true, and the rule
 <code>#extra_navigation { display: none }</code> is applied.
 </div>
 
@@ -547,10 +549,10 @@ <h2 id="at-document">Document queries: the <code>@document</code> rule</h2>
 iframe/object/embed/img; it should probably not apply to the URL of an
 svg:use.</p>
 
-<p>Implementations MUST treat any unknown URL matching functions as a
-syntax error, and thus ignore the <code>@document</code> rule.  <span
-class="issue">Should we instead have more complicated error handling
-rules?</span></p>
+<p>Implementations <strong>must</strong> treat any unknown URL matching
+functions as a syntax error, and thus ignore the <code>@document</code>
+rule.  <span class="issue">Should we instead have more complicated error
+handling rules?</span></p>
 
 <p>This extends the lexical scanner in the
 <a href="http://www.w3.org/TR/CSS21/grammar.html">Grammar of CSS 2.1</a>