Typo fix.

Author: tabatkins

css-variables/Overview.html

@@ -21,15 +21,15 @@
 
    <h1>CSS Variables Module Level 1</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 10 April 2012</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 9 May 2012</h2>
 
    <dl>
     <dt>This version:
-     <!--<dd><a href="http://www.w3.org/TR/2012/WD-css-variables-20120410/">http://www.w3.org/TR/2012/ED-css-variables-20120410/</a>-->
+     <!--<dd><a href="http://www.w3.org/TR/2012/WD-css-variables-20120509/">http://www.w3.org/TR/2012/ED-css-variables-20120509/</a>-->
 
 
     <dd><a href="http://dev.w3.org/csswg/css-variables/">Editor's draft</a>
-     (version of 10 April 2012)
+     (version of 9 May 2012)
 
     <dt>Latest version:
 
@@ -211,7 +211,7 @@ <h2 id=intro><span class=secno>1. </span> Introduction</h2>
    property with an author-chosen name, and then use those values in other
    properties elsewhere in the document. This makes it easier to read large
    files, as seemingly-arbitrary values now have informative names, and makes
-   editting such files much easier and less error-prone, as one only has to
+   editing such files much easier and less error-prone, as one only has to
    change the value once, at the variable definition site, and the change
    will propagate to all uses of that variable automatically.
 
@@ -304,7 +304,7 @@ <h2 id=defining-variables><span class=secno>2. </span> Defining Variables
    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
+   values, as they are not evaluated except to replace variables occurring
    within them until they are actually referenced in a normal property with a
    variable.
 

css-variables/Overview.src.html

@@ -70,7 +70,7 @@ <h2 id="intro">
 
 	<p>Large documents or applications (and even small ones) can contain quite a bit of CSS.  Many of the values in the CSS file will be duplicate data; for example, a site may establish a color scheme and reuse three or four colors throughout the site.  Altering this data can be difficult and error-prone, since it's scattered throughout the CSS file (and possibly across multiple files), and may not be amenable to Find-and-Replace.</p>
 
-	<p>This module introduces a family of custom user-defined properties known collectively as <i>variable properties</i>, which allow an author to assign arbitrary values to a property with an author-chosen name, and then use those values in other properties elsewhere in the document.  This makes it easier to read large files, as seemingly-arbitrary values now have informative names, and makes editting such files much easier and less error-prone, as one only has to change the value once, at the variable definition site, and the change will propagate to all uses of that variable automatically.</p>
+	<p>This module introduces a family of custom user-defined properties known collectively as <i>variable properties</i>, which allow an author to assign arbitrary values to a property with an author-chosen name, and then use those values in other properties elsewhere in the document.  This makes it easier to read large files, as seemingly-arbitrary values now have informative names, and makes editing such files much easier and less error-prone, as one only has to change the value once, at the variable definition site, and the change will propagate to all uses of that variable automatically.</p>
 
 <h3 id="placement">
 Module Interactions</h3>
@@ -121,7 +121,7 @@ <h2 id="defining-variables">
 
 	<p class='issue'>As defined here, the syntax for variable usage is different from the syntax for variable definition (i.e. var-foo for definition, var(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 variable property are almost completely unrestricted.  A variable 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>
+	<p>The valid possible values of a variable property are almost completely unrestricted.  A variable 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 occurring within them until they are actually referenced in a normal property with a variable.</p>
 
 	<p>This specification reserves the use of all function tokens starting with the prefix "var" within variable properties.  Authors must not use any such functions except as defined in this specification or future updates.  If a variable property contains such a function, it must match the grammar defined in this specification or future updates; the use of such a function that does not follow the grammar, or that utilizes such a function that is not yet defined, makes the variable property invalid and it must be ignored.</p>