@@ -255,7 +255,7 @@ Error Handling</h3>
255255Tokenizing and Parsing CSS</h2>
256256
257257 User agents must use the parsing rules described in this specification
258- to generate the CSSOM trees from text/css resources.
258+ to generate the [[ CSSOM]] trees from text/css resources.
259259 Together, these rules define what is referred to as the CSS parser.
260260
261261 This specification defines the parsing rules for CSS documents,
@@ -2021,7 +2021,7 @@ Parse something according to a CSS grammar</h4>
20212021 Note: This algorithm,
20222022 and [=parse a comma-separated list according to a CSS grammar=] ,
20232023 are <em> usually</em> the only parsing algorithms other specs will want to call.
2024- The remaining parsing algorithms are meant mostly for CSSOM
2024+ The remaining parsing algorithms are meant mostly for [[ CSSOM]]
20252025 and related "explicitly constructing CSS structures" cases.
20262026 Consult the CSSWG for guidance first
20272027 if you think you need to use one of the other algorithms.
@@ -3391,7 +3391,7 @@ Serialization</h2>
33913391 If they do, this preserved information must have no effect on the parsing step.
33923392
33933393 This specification does not define how to serialize CSS in general,
3394- leaving that task to the CSSOM and individual feature specifications.
3394+ leaving that task to the [[ CSSOM]] and individual feature specifications.
33953395 In particular, the serialization of comments and whitespace is not defined.
33963396
33973397 The only requirement for serialization is that it must "round-trip" with parsing,
0 commit comments