[css-syntax] Fix some typos in the changes section.

Author: tabatkins

css-syntax/Overview.html

@@ -2931,8 +2931,8 @@ <h2 class="heading settled heading" data-level=10 id=changes><span class=secno>1
 			Any U+0000 NULL <a href=#code-point>code point</a> in the CSS source is replaced with U+FFFD REPLACEMENT CHARACTER.
 
 		<li>
-			Any hexadecimal escape sequence such as <span class=css data-link-type=maybe>\0</span> that evaluate to zero
-			produce U+FFFD REPLACEMENT r rather than U+0000 NULL.
+			Any hexadecimal escape sequence such as <span class=css data-link-type=maybe>\0</span> that evaluates to zero
+			produce U+FFFD REPLACEMENT CHARACTER rather than U+0000 NULL.
 			<!--
 				This covers a security issue:
 				https://bugzilla.mozilla.org/show_bug.cgi?id=228856
@@ -2947,13 +2947,14 @@ <h2 class="heading settled heading" data-level=10 id=changes><span class=secno>1
 
 		<li>
 			Tokenization does not emit COMMENT or BAD_COMMENT tokens anymore.
-			BAD_COMMENT is now considered the same as normal token (not an error.)
+			BAD_COMMENT is now considered the same as a normal token (not an error).
 			<a href=#serialization>Serialization</a> is responsible
 			for inserting comments as necessary between tokens that need to be separated,
 			e.g. two consecutive <a class=css-code data-link-type=token href=#tokendef-ident>〈ident〉</a>s.
 
 		<li>
-			The <a class=css-code data-link-type=token href=#tokendef-unicode-range>〈unicode-range〉</a> token is now more restrictive.
+			The <a class=css-code data-link-type=token href=#tokendef-unicode-range>〈unicode-range〉</a> token is now more restrictive,
+			and doesn’t include non-sensical patterns that the 2.1 definition allowed.
 
 		<li>
 			Apply the <a href=http://www.w3.org/TR/CSS21/syndata.html#unexpected-eof>EOF error handling rule</a> in the tokenizer

css-syntax/Overview.src.html

@@ -2819,8 +2819,8 @@ <h2 id="changes">
 			Any U+0000 NULL <a>code point</a> in the CSS source is replaced with U+FFFD REPLACEMENT CHARACTER.
 
 		<li>
-			Any hexadecimal escape sequence such as ''\0'' that evaluate to zero
-			produce U+FFFD REPLACEMENT r rather than U+0000 NULL.
+			Any hexadecimal escape sequence such as ''\0'' that evaluates to zero
+			produce U+FFFD REPLACEMENT CHARACTER rather than U+0000 NULL.
 			<!--
 				This covers a security issue:
 				https://bugzilla.mozilla.org/show_bug.cgi?id=228856
@@ -2835,13 +2835,14 @@ <h2 id="changes">
 
 		<li>
 			Tokenization does not emit COMMENT or BAD_COMMENT tokens anymore.
-			BAD_COMMENT is now considered the same as normal token (not an error.)
+			BAD_COMMENT is now considered the same as a normal token (not an error).
 			<a href="#serialization">Serialization</a> is responsible
 			for inserting comments as necessary between tokens that need to be separated,
 			e.g. two consecutive <<<ident>>>s.
 
 		<li>
-			The <<<unicode-range>>> token is now more restrictive.
+			The <<<unicode-range>>> token is now more restrictive,
+			and doesn't include non-sensical patterns that the 2.1 definition allowed.
 
 		<li>
 			Apply the <a href="http://www.w3.org/TR/CSS21/syndata.html#unexpected-eof">EOF error handling rule</a> in the tokenizer