[css-conditional-3] Changes, from GitHub history

Author: svgeesus

css-conditional-3/Overview.bs

@@ -684,18 +684,26 @@ The following (non-editorial) changes were made to this specification since the
 <a href="https://www.w3.org/TR/2013/CR-css3-conditional-20130404/">4 April 2013 Candidate Recommendation</a>:
 
 <ul>
-  <li>Explicit call to [=CSS/parse=] rather than "matches the grammar"
-  <li>Drop requirement for spaces around ''and'', ''or'', and ''not'' keywords
+  <li>Added explicit call to [=CSS/parse=] rather than "matches the grammar"
+  <li>Removed duplicate CSSGroupingRule, which is already defined by CSSOM
+  <li>Rewrote the supports() text into algorithm form,
+      to make it easier to express that you pay attention to
+      the syntax of registered custom properties in the supports(prop, val) form.
+  <li>Moved the definition of @supports selector to css-conditional-4.
+  <li>''@supports''' is no longer at risk.
+  <li>Rewrote to use CSS Syntax grammars, not CSS 2.1 grammars
+  <li>Dropped requirement for spaces around ''and'', ''or'', and ''not'' keywords
       for consistency with <a href="http://www.w3.org/TR/css3-mediaqueries/">Media Queries</a>
       (which are themselves constrained by compatibility with the output of some CSS minimizers
       that rely on some of the more arcane aspects of CSS tokenization).
       Note that white space--or a comment--is still required <em>after</em> these keywords,
       since without it they and the ensuing opening parenthesis will be tokenized as a function opening token.
-  <li>Allow the <code title=''>supports()</code> method
+  <li>Allowed the <code title=''>supports()</code> method
       to imply parentheses for simple declarations,
       for consistency with the ''@import'' rule’s ''supports()'' function.
   <li>Fixed missing semicolons in IDL code.
   <li>Updated links, terminology, and example code in response to changes to other modules.
+  <li>Spelling and grammatical corrections
   <li>Added section on privacy and security considerations.
 </ul>