Change the issues text to not use the 1st person, as insisted on the list.

Author: tabatkins

css-variables/Overview.html

@@ -292,12 +292,13 @@ <h2 id=defining-variables><span class=secno>2. </span> Defining Variables
    to them beyond the bare minimum that comes from them being valid
    properties.
 
-  <p class=issue>I'm using data-foo for their rough parallel (in terms of
-   being completely user-extensible) with the data-* attributes in HTML.
-   Might another name be better? Suggestions so far are "var-foo", "$foo",
-   and "var(foo)" (the latter two are intended to directly resemble the usage
-   of the variable). Obviously, usage of the variable should match, as
-   "var(foo)" or "$foo" or whatever.
+  <p class=issue>The naming here is loosely based on the form of custom data
+   attributes in HTML5. However, as defined here, the syntax for variable
+   usage is different from the syntax for variable definition (i.e. data-foo
+   for definition, data(foo) for usage). Some have suggested that the
+   syntaxes should should match, using functional syntax in both cases.
+   Others have suggested using a prefixed symbol instead of functional syntax
+   (e.g. $foo) for both the property and usage.
 
   <p>The valid possible values of a data property are almost completely
    unrestricted. A data property can contain anything that is valid according
@@ -637,9 +638,9 @@ <h3 id=cssom-cssvariable><span class=secno>4.1. </span> Interface
   <h3 id=cssstyledeclaration-interface><span class=secno>4.2. </span>
    Additions to the <code>CSSStyleDeclaration</code> Interface</h3>
 
-  <p class=issue>The set of data properties is open-ended, so I'm not sure
-   how best to represent this. I'd like to both expose the current set of
-   properties with a non-initial value and allow setting of arbitrary
+  <p class=issue>The set of data properties is open-ended, so it's not clear
+   how best to represent this. Ideally, the CSSOM would expose the current
+   set of properties with a non-initial value and allow setting of arbitrary
    properties. The most natural way seems to be to first, set up a getter
    behavior on the interface somehow that deals with data properties, and
    second, set up a <code>data</code> map that exposes the data properties

css-variables/Overview.src.html

@@ -119,7 +119,7 @@ <h2 id="defining-variables">
 
 	<p><em>Any</em> property name starting with the prefix "data-" is a <i>data property</i>.  Data properties are defined to be valid but meaningless as they are meant solely for allowing authors to pass custom data around their page, similar to the <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#embedding-custom-non-visible-data-with-the-data-*-attributes">custom data attributes</a> in HTML.  Other specifications and user agents must not assign a particular meaning to data properties or attach a specific effect to them beyond the bare minimum that comes from them being valid properties.</p>
 
-	<p class='issue'>I'm using data-foo for their rough parallel (in terms of being completely user-extensible) with the data-* attributes in HTML.  Might another name be better?  Suggestions so far are "var-foo", "$foo", and "var(foo)" (the latter two are intended to directly resemble the usage of the variable).  Obviously, usage of the variable should match, as "var(foo)" or "$foo" or whatever.</p>
+	<p class='issue'>The naming here is loosely based on the form of custom data attributes in HTML5.  However, as defined here, the syntax for variable usage is different from the syntax for variable definition (i.e. data-foo for definition, data(foo) for usage). Some have suggested that the syntaxes should should match, using functional syntax in both cases. Others have suggested using a prefixed symbol instead of functional syntax (e.g. $foo) for both the property and usage.</p>
 
 	<p>The valid possible values of a data property are almost completely unrestricted.  A data property can contain anything that is valid according to the <code>value</code> production in the <a href="http://www.w3.org/TR/CSS2/syndata.html#tokenization">CSS Core Grammar</a>.  The values do not have to correspond to any existing CSS values, as they are not evaluated except to replace variables occuring within them until they are actually referenced in a normal property with a variable.</p>
 
@@ -311,7 +311,7 @@ <h3 id='cssom-cssvariable'>
 <h3 id='cssstyledeclaration-interface'>
 Additions to the <code>CSSStyleDeclaration</code> Interface</h3>
 
-<p class='issue'>The set of data properties is open-ended, so I'm not sure how best to represent this.  I'd like to both expose the current set of properties with a non-initial value and allow setting of arbitrary properties.  The most natural way seems to be to first, set up a getter behavior on the interface somehow that deals with data properties, and second, set up a <code>data</code> map that exposes the data properties that aren't set to their initial value.</p>
+<p class='issue'>The set of data properties is open-ended, so it's not clear how best to represent this.  Ideally, the CSSOM would expose the current set of properties with a non-initial value and allow setting of arbitrary properties.  The most natural way seems to be to first, set up a getter behavior on the interface somehow that deals with data properties, and second, set up a <code>data</code> map that exposes the data properties that aren't set to their initial value.</p>
 
 <h2 id="conformance">
 Conformance</h2>