Fix inaccuracy in Component values section reported in <http://lists.w3.org/Archives/Public/www-style/2012Apr/0080.html> (but with a completely different edit from that suggested).

Author: fantasai

css3-values/Overview.html

@@ -469,17 +469,18 @@ <h3 id=component-whitespace><span class=secno>2.4. </span> Component values
    href="http://www.w3.org/TR/CSS21/syndata.html#tokenization">Chapter 4</a>
    of <a href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>. As the
    grammar allows spaces between tokens in the components of the
-   <code>value</code> production, spaces may appear between tokens in
+   <code>value</code> production, spaces may appear between components in
    property values.
 
   <p class=note>Note: In many cases, spaces will in fact be <em>required</em>
-   between tokens in order to distinguish them from each other. For example,
-   the value ‘<code class=css>1em2em</code>’ would be parsed as a single
-   <code>DIMEN</code> token with the number ‘<code class=css>1</code>’
-   and the identifier ‘<code class=css>em2em</code>’, which is an invalid
-   unit. In this case, a space would be required before the ‘<code
-   class=css>2</code>’ to get this parsed as the two lengths ‘<code
-   class=css>1em</code>’ and ‘<code class=css>2em</code>’.
+   between components in order to distinguish them from each other. For
+   example, the value ‘<code class=css>1em2em</code>’ would be parsed as
+   a single <code>DIMEN</code> token with the number ‘<code
+   class=css>1</code>’ and the identifier ‘<code
+   class=css>em2em</code>’, which is an invalid unit. In this case, a space
+   would be required before the ‘<code class=css>2</code>’ to get this
+   parsed as the two lengths ‘<code class=css>1em</code>’ and ‘<code
+   class=css>2em</code>’.
 
   <h3 id=value-examples><span class=secno>2.5. </span> Property value
    examples</h3>

css3-values/Overview.src.html

@@ -208,11 +208,11 @@ <h3 id="component-whitespace">
 	href="http://www.w3.org/TR/CSS21/syndata.html#tokenization">Chapter 4</a>
 	of [[!CSS21]].
 	As the grammar allows spaces between tokens in the components of the
-	<code>value</code> production, spaces may appear between tokens in
+	<code>value</code> production, spaces may appear between components in
 	property values.
 
 	<p class=note>Note: In many cases, spaces will in fact be
-	<em>required</em> between tokens in order to distinguish them from
+	<em>required</em> between components in order to distinguish them from
 	each other. For example, the value ''1em2em'' would be parsed as a
 	single <code>DIMEN</code> token with the number ''1'' and the identifier
 	''em2em'', which is an invalid unit. In this case, a space would be

css3-values/issues-lc-2012.txt

@@ -26,7 +26,7 @@ Summary:  Eliminate the 'integer' type entirely.
 From:     Kenny Lu
 Comment:  http://lists.w3.org/Archives/Public/www-style/2012Apr/0260.html
 Response: http://lists.w3.org/Archives/Public/www-style/2012Apr/0624.html
-Closed:   Rejected.
+Closed:   Rejected
 ----
 Issue 5.
 Summary:  attr() needs to either clarify what element it draws from when not in a rule (and where exactly it's allowed), or disallow that case
@@ -68,19 +68,19 @@ Summary:  Can calc() return an <integer>? If so, clarify when it does so.
 From:     Kenny Lu
 Comment:  http://lists.w3.org/Archives/Public/www-style/2012Apr/0260.html
 Response: http://lists.w3.org/Archives/Public/www-style/2012Apr/0624.html
-Open:     Accepted pending WG resolution
+Open:     Accepted
 ----
 Issue 11.
 Summary:  calc() should refer to <number> etc. *types*, not grammar tokens, so attr() etc. can be used.
 From:     fantasai and Tab Atkins
-Open:     pending WG resolution
+Closed:   Accepted (to allow attr(), still referring to tokens)
 ----
 Issue 12.
 Summary:  cycle() and values that have commas.
 From:     Kenny Lu
 Comment:  http://lists.w3.org/Archives/Public/www-style/2012Apr/0151.html
 Response: http://lists.w3.org/Archives/Public/www-style/2012Apr/0626.html
-Closed:   Deferred
+Closed:   Rejected
 ----
 Issue 13.
 Summary:  cycle() can't skip levels, or easily refer to non-inherited properties
@@ -94,26 +94,26 @@ Summary:  Example UA stylesheet using cycle() for <ul> is incorrect.
 From:     Kenny Lu
 Comment:  http://lists.w3.org/Archives/Public/www-style/2012Apr/0207.html
 Response: http://lists.w3.org/Archives/Public/www-style/2012Apr/0627.html
-Closed:   Deferred
+Closed:   Accepted
 ----
 Issue 15.
 Summary:  Value equality of components of cycle() ill-defined
 From:     Kenny Lu
 Comment:  http://lists.w3.org/Archives/Public/www-style/2012Apr/0207.html
 Response: http://lists.w3.org/Archives/Public/www-style/2012Apr/0627.html
-Closed:   Deferred
+Closed:   Invalid
 ----
 Issue 16.
 Summary:  Defer cycle() to level 4
 From:     fantasai and Tab Atkins
 Note:     Possibly switch current function to toggle(), and create a new cycle() that addresses Kenny's issues about <ul>,<table>,etc.
-Open:     pending WG resolution
+Closed:   Partially accepted
 ----
 Issue 17.
 Summary:  Switch URL reference to abarth's url spec.
 From:     Kenny Lu
 Comment:  http://lists.w3.org/Archives/Public/www-style/2012Apr/0204.html
-Open:     pending advice
+Closed:   Rejected
 ----
 Issue 18.
 Summary:  Define (or reference from elsewhere) a specific always-invalid URL.
@@ -186,4 +186,4 @@ From:     fantasai
 Comment:  http://lists.w3.org/Archives/Public/www-style/2012Apr/0566.html
 Response: 
 Closed:   Deferred
-----
+----