[editorial][css-syntax] Update changes list, fix links.

Author: tabatkins

css-syntax-3/Overview.bs

@@ -3154,13 +3154,13 @@ CSS stylesheets</h2>
 Style rules</h3>
 
 	A <dfn>style rule</dfn> is a <a>qualified rule</a>
-	that associates a <a href="https://drafts.csswg.org/selectors4/#selector-list">selector list</a> [[!SELECT]]
+	that associates a <a>selector list</a> [[!SELECT]]
 	with a list of property declarations.
 	They are also called
 	<a href="https://www.w3.org/TR/CSS21/syndata.html#rule-sets">rule sets</a> in [[!CSS21]].
 	CSS Cascading and Inheritance [[!CSS3CASCADE]] defines how the declarations inside of style rules participate in the cascade.
 
-	The prelude of the qualified rule is <a lt="parse something according to a CSS grammar">parsed</a>
+	The prelude of the qualified rule is [=CSS/parsed=]
 	as a <<selector-list>>.
 	If this returns failure,
 	the entire style rule is <a>invalid</a>.
@@ -3422,6 +3422,11 @@ Changes from the 20 February 2014 Candidate Recommendation</h3>
 
 	* Define all tokens to have a <a>representation</a>.
 
+	* Fixed minor bug in <a>check if two code points are a valid escape</a>--
+		a <code>\</code> followed by an EOF is now correctly reported as <em>not</em> a valid escape.
+
+	* If the very first rule in the sheet is a ''@charset'', dropped it during parsing.
+
 	The following editorial changes were made:
 
 	* The "Consume a string token" algorithm was changed to allow calling it without specifying an explicit ending token,
@@ -3430,17 +3435,14 @@ Changes from the 20 February 2014 Candidate Recommendation</h3>
 
 	* Minor editorial restructuring of algorithms.
 
-	* Added the [=CSS/parse=] API entry point.
+	* Added the [=CSS/parse=] and [=parse a comma-separated list of component values=] API entry points.
 
 	* Added the <<declaration-value>> and <<any-value>> productions.
 
 	* Removed the Selectors-specific tokens, per WG resolution.
 
 	* Removed "code point" and "surrogate code point" in favor of the identical definitions in the Infra Standard.
 
-	* Fixed minor bug in <a>check if two code points are a valid escape</a>--
-		a <code>\</code> followed by an EOF is now correctly reported as <em>not</em> a valid escape.
-
 
 <h3 id="changes-WD-20131105">
 Changes from the 5 November 2013 Last Call Working Draft</h3>