Fixed a broken link to HTML5 and made the link point to the official

HTML5 draft, instead of the WhatWG document. Replaced the "this
version" link with something arbitrary to reset the status to
"editor's draft.

Author: bert-github

css-variables/Overview.src.html

@@ -16,12 +16,12 @@
 
 <h1>CSS Variables Module Level 1</h1>
 
-<!--<h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>-->
-<h2 class='no-num no-toc'>W3C Working Draft 15 March 2012</h2>
+<h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
 
 <dl>
 	<dt>This version:
-		<dd><a href="http://www.w3.org/TR/2012/WD-css-variables-20120315/">http://www.w3.org/TR/2012/WD-css-variables-20120315/</a>
+		<!--<dd><a href="http://www.w3.org/TR/[YEAR]/WD-css-variables-[CDATE]/">[VERSION]</a>-->
+		<dd><a href="http://dev.w3.org/csswg/[SHORTNAME]/">Editor's draft</a> (version of [DATE])
 
 	<dt>Latest version:
 		<dd><a href="http://www.w3.org/TR/[SHORTNAME]/">http://www.w3.org/TR/[SHORTNAME]/</a>
@@ -117,7 +117,7 @@ <h2 id="defining-variables">
 			<td>all
 	</table>
 
-	<p><em>Any</em> property name starting with the prefix "var-" is a <i>variable property</i>.  Variable 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-var-with-the-var-*-attributes">custom data attributes</a> in HTML.  Other specifications and user agents must not assign a particular meaning to <i>variable properties</i> or attach a specific effect to them beyond the bare minimum that comes from them being valid properties.</p>
+	<p><em>Any</em> property name starting with the prefix "var-" is a <i>variable property</i>.  Variable 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.w3.org/TR/html5/global-attributes.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 <i>variable properties</i> or attach a specific effect to them beyond the bare minimum that comes from them being valid properties.</p>
 
 	<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>