[css-syntax] Wording tweaks.

Author: tabatkins

css-syntax/Overview.html

@@ -4465,42 +4465,43 @@ <h2 class="heading settled heading" data-level=9 id=serialization><span class=se
 	In particular, the serialization of comments an whitespace is not defined.
 
 <p>	The only requirement for serialization is that it must "round-trip" with parsing,
-	ie. parsing again the serialized output must result in identical tokens or other structures,
-	except for consecutive <a class="production css-code" data-link-type=type href=#typedef-whitespace-token title="<whitespace-token>">&lt;whitespace-token&gt;</a>s
-	that may be collapsed into a single token.
+	that is, parsing the stylesheet must produce the same data structures as
+	parsing, serializing, and parsing again,
+	except for consecutive <a class="production css-code" data-link-type=type href=#typedef-whitespace-token title="<whitespace-token>">&lt;whitespace-token&gt;</a>s,
+	which may be collapsed into a single token.
 
 <p class=note>	Note: This exception can exist because
 	CSS grammars always interpret any amount of whitespace as identical to a single space.
 
-	<div class=note id=serialization-tables><style scoped>
-			#serialization-tables table { margin: 1em 0 }
-			#serialization-tables table { border-collapse: collapse }
-			#serialization-tables tr:nth-child(even) { background: rgba(0, 0, 0, .1) }
-			#serialization-tables th { padding: .2em .5em; line-height: 1.1; font-size: 90% }
-			#serialization-tables th, td { text-align: center }
-		</style>
-
-		<a class=self-link href=#serialization-tables></a>
+	<div class=note id=serialization-tables><a class=self-link href=#serialization-tables></a>
 		Note: In order to satisfy this requirement:
 
 <p>		<ul>
 			<li>
-				A <a class="production css-code" data-link-type=type href=#typedef-delim-token title="<delim-token>">&lt;delim-token&gt;</a> containing U+005C REVERSE SOLIDUS (\)
-				must be followed when serialized by a <a data-link-type=dfn href=#newline title=newline>newline</a>.
+				A <a class="production css-code" data-link-type=type href=#typedef-delim-token title="<delim-token>">&lt;delim-token&gt;</a> containing U+005C REVERSE SOLIDUS (\)\
+				must be serialized as U+005C REVERSE SOLIDUS
+				followed by a <a data-link-type=dfn href=#newline title=newline>newline</a>.
 				(The tokenizer only ever emits such a token followed by a <a class="production css-code" data-link-type=type href=#typedef-whitespace-token title="<whitespace-token>">&lt;whitespace-token&gt;</a>
 				that starts with a newline.)
 			<li>
-				Consecutive pairs of tokens that have a ✓ in either of the two tables below
-				must be serialized with a comment in-between.
-				If no comment was preserved from tokenization,
-				an empty comment <code>/**/</code> should be inserted.
-				Rows and columns represent a token and its following token, respectively.
-				Single character represent a <a class="production css-code" data-link-type=type href=#typedef-delim-token title="<delim-token>">&lt;delim-token&gt;</a> with that value,
-				except for "<code>(</code>" that
-				represents a <a href=#tokendef-open-paren>(-token</a>.
+
+<p>				For any consecutive pair of tokens,
+				if the first token shows up in the row headings of either of the following two tables,
+				and the second token shows up in the column headings,
+				and there’s a ✓ in the cell denoted by the intersection of the chosen row and column,
+				the pair of tokens must be serialized with a comment between them.
+
+<p>				If the tokenizer preserves comments,
+				the preserved comment should be used;
+				otherwise, an empty comment (<code>/**/</code>) must be inserted.
+				(Preserved comments may be reinserted even if the following tables don’t require a comment between two tokens.)
+
+<p>				Single characters in the row and column headings represent a <a class="production css-code" data-link-type=type href=#typedef-delim-token title="<delim-token>">&lt;delim-token&gt;</a> with that value,
+				except for "<code>(</code>",
+				which represents a <a href=#tokendef-open-paren>(-token</a>.
 		</ul>
 
-		<table>
+		<table class=data>
 			<tr>
 				<td>
 				<th>ident
@@ -4549,7 +4550,7 @@ <h2 class="heading settled heading" data-level=9 id=serialization><span class=se
 				<td><td><td><td><td><td>✓<td>✓<td>✓<td><td><td>
 		</table>
 
-		<table>
+		<table class=data>
 			<tr>
 				<td>
 				<th>=<th>|<th>*

css-syntax/Overview.src.html

@@ -2969,42 +2969,43 @@ <h2 id="serialization">
 	In particular, the serialization of comments an whitespace is not defined.
 
 	The only requirement for serialization is that it must "round-trip" with parsing,
-	ie. parsing again the serialized output must result in identical tokens or other structures,
-	except for consecutive <<whitespace-token>>s
-	that may be collapsed into a single token.
+	that is, parsing the stylesheet must produce the same data structures as
+	parsing, serializing, and parsing again,
+	except for consecutive <<whitespace-token>>s,
+	which may be collapsed into a single token.
 
 	Note: This exception can exist because
 	CSS grammars always interpret any amount of whitespace as identical to a single space.
 
-	<div class=note id=serialization-tables>
+	<div class=note id='serialization-tables'>
 		Note: In order to satisfy this requirement:
 
 		<ul>
 			<li>
-				A <<delim-token>> containing U+005C REVERSE SOLIDUS (\)
-				must be followed when serialized by a <a>newline</a>.
+				A <<delim-token>> containing U+005C REVERSE SOLIDUS (\)\
+				must be serialized as U+005C REVERSE SOLIDUS
+				followed by a <a>newline</a>.
 				(The tokenizer only ever emits such a token followed by a <<whitespace-token>>
 				that starts with a newline.)
 			<li>
-				Consecutive pairs of tokens that have a ✓ in either of the two tables below
-				must be serialized with a comment in-between.
-				If no comment was preserved from tokenization,
-				an empty comment <code>/**/</code> should be inserted.
-				Rows and columns represent a token and its following token, respectively.
-				Single character represent a <<delim-token>> with that value,
-				except for "<code>(</code>" that
-				represents a <a href=#tokendef-open-paren>(-token</a>.
-		</ul>
 
-		<style>
-			#serialization-tables table { margin: 1em 0 }
-			#serialization-tables table { border-collapse: collapse }
-			#serialization-tables tr:nth-child(even) { background: rgba(0, 0, 0, .1) }
-			#serialization-tables th { padding: .2em .5em; line-height: 1.1; font-size: 90% }
-			#serialization-tables th, td { text-align: center }
-		</style>
+				For any consecutive pair of tokens,
+				if the first token shows up in the row headings of either of the following two tables,
+				and the second token shows up in the column headings,
+				and there's a ✓ in the cell denoted by the intersection of the chosen row and column,
+				the pair of tokens must be serialized with a comment between them.
+
+				If the tokenizer preserves comments,
+				the preserved comment should be used;
+				otherwise, an empty comment (<code>/**/</code>) must be inserted.
+				(Preserved comments may be reinserted even if the following tables don't require a comment between two tokens.)
+
+				Single characters in the row and column headings represent a <<delim-token>> with that value,
+				except for "<code>(</code>",
+				which represents a <a href=#tokendef-open-paren>(-token</a>.
+		</ul>
 
-		<table>
+		<table class='data'>
 			<tr>
 				<td>
 				<th>ident
@@ -3053,7 +3054,7 @@ <h2 id="serialization">
 				<td><td><td><td><td><td>✓<td>✓<td>✓<td><td><td>
 		</table>
 
-		<table>
+		<table class='data'>
 			<tr>
 				<td>
 				<th>=<th>|<th>*