Some tweaks to the introduction sections.

Author: tabatkins

css3-syntax/parsing.html

@@ -57,9 +57,6 @@ <h3>
 	<p class='note'>
 		The requirement to strip a U+FEFF BYTE ORDER MARK character regardless of whether that character was used to determine the byte order is a willful violation of Unicode, motivated by a desire to increase the resilience of user agents in the face of naïve transcoders.
 
-	<p>
-		Any occurrences of any characters in the ranges U+0001 to U+0008, U+000E to U+001F, U+007F to U+009F, U+FDD0 to U+FDEF, and characters U+000B, U+FFFE, U+FFFF, U+1FFFE, U+1FFFF, U+2FFFE, U+2FFFF, U+3FFFE, U+3FFFF, U+4FFFE, U+4FFFF, U+5FFFE, U+5FFFF, U+6FFFE, U+6FFFF, U+7FFFE, U+7FFFF, U+8FFFE, U+8FFFF, U+9FFFE, U+9FFFF, U+AFFFE, U+AFFFF, U+BFFFE, U+BFFFF, U+CFFFE, U+CFFFF, U+DFFFE, U+DFFFF, U+EFFFE, U+EFFFF, U+FFFFE, U+FFFFF, U+10FFFE, and U+10FFFF are parse errors. These are all control characters or permanently undefined Unicode characters (noncharacters).
-
 	<p>
 		U+000D CARRIAGE RETURN (CR) characters and U+000A LINE FEED (LF) characters are treated specially. All CR characters must be converted to LF characters, and any LF characters that immediately follow a CR character must be ignored. Thus, newlines in HTML DOMs are represented by LF characters, and there are never any CR characters in the input to the tokenization stage.
 
@@ -75,6 +72,9 @@ <h3>
 <h3>
 Parse State</h3>
 
+	<p>
+		...
+
 <h3>
 Tokenization</h3>
 
@@ -129,7 +129,8 @@ <h4>
 
 		<dt><dfn>non-printable character</dfn>
 		<dd>
-			A character between U+0000 NULL and U+001F INFORMATION SEPARATOR ONE
+			A character between U+0000 NULL and U+0008 BACKSPACE
+			or a character between U+000E SHIFT OUT and U+001F INFORMATION SEPARATOR ONE
 			or a character between U+007F DELETE and U+009F APPLICATION PROGRAM COMMAND.
 
 		<dt><dfn>newline</dfn>