[css-syntax-3][editorial] Fix bikeshed errors.

Author: tabatkins

css-syntax-3/Overview.bs

@@ -14,7 +14,7 @@ Previous Version: https://www.w3.org/TR/2013/WD-css-syntax-3-20130919/
 Editor: Tab Atkins Jr., Google, http://xanthir.com/contact/, w3cid 42199
 Editor: Simon Sapin, Mozilla, http://exyr.org/about/, w3cid 58001
 Abstract: This module describes, in general terms, the basic structure and syntax of CSS stylesheets. It defines, in detail, the syntax and parsing of CSS - how to turn a stream of bytes into a meaningful stylesheet.
-Ignored Terms: <keyframes-name>, <keyframe-rule>, <keyframe-selector>, <translation-value>, <media-query-list>, <unicode-range-token>
+Ignored Terms: <keyframes-name>, <keyframe-rule>, <keyframe-selector>, <translation-value>, <media-query-list>
 Ignored Vars: +b, -b, foo
 </pre>
 
@@ -23,7 +23,6 @@ spec:css-cascade-5; type:dfn; text:property
 spec:css-color-4; type:property; text:color
 spec:css-text-decor-3; type:property; text:text-decoration
 spec:css-transforms-1; type:function; text:translatex()
-spec:encoding-1; type:dfn; text:get an encoding
 spec:html; type:element;
 	text:a
 	text:style
@@ -1919,7 +1918,7 @@ CSS Parsing Results</h3>
 	(or lists of these):
 
 	<dl export dfn-for=CSS>
-		: [=stylesheet=]
+		: <dfn>stylesheet</dfn>
 		:: A stylesheet has a list of [=rules=].
 
 		: <dfn>rule</dfn>
@@ -3744,11 +3743,14 @@ Serializing <var>&lt;an+b></var></h3>
 	</div>
 
 
-<h2 id="priv-sec">
-Privacy and Security Considerations</h2>
+<h2 id="privacy">
+Privacy Considerations</h2>
 
 	This specification introduces no new privacy concerns.
 
+<h2 id=security>
+Security Considerations</h2>
+
 	This specification improves security, in that CSS parsing is now unambiguously defined for all inputs.
 
 	Insofar as old parsers, such as whitelists/filters, parse differently from this specification,
@@ -3952,7 +3954,7 @@ Changes from CSS 2.1 and Selectors Level 3</h3>
 
 		<li>
 			The definition of <a>non-ASCII ident code point</a> was changed
-			to be consistent with HTML's [=valid custom elements names=].
+			to be consistent with HTML's [=valid custom element names=].
 
 		<li>
 			Tokenization does not emit COMMENT or BAD_COMMENT tokens anymore.