[css-cascade] Allow functional notation parse-time aliases as well. w3c#6193

Author: fantasai

css-cascade-4/Overview.bs

@@ -569,8 +569,8 @@ Declared Values</h3>
 <h4 id="value-aliasing">
 Value Aliasing</h4>
 
-	Some [=keyword=] property values have <dfn export for=CSS lt="legacy value alias">legacy value aliases</dfn>:
-	at parse time, the legacy [=keyword=] is converted into the new [=keyword=],
+	Some property values have <dfn export for=CSS lt="legacy value alias">legacy value aliases</dfn>:
+	at parse time, the legacy syntax is converted into the new syntax,
 	resulting in a [=declared value=] different from the parsed input.
 	These aliases are typically used for handling legacy compatibility requirements,
 	such as converting [=vendor-prefixed=] values to their standard equivalents.

css-cascade-5/Overview.bs

@@ -528,8 +528,8 @@ Declared Values</h3>
 <h4 id="value-aliasing">
 Value Aliasing</h4>
 
-	Some [=keyword=] property values have <dfn export for=CSS lt="legacy value alias">legacy value aliases</dfn>:
-	at parse time, the legacy [=keyword=] is converted into the new [=keyword=],
+	Some property values have <dfn export for=CSS lt="legacy value alias">legacy value aliases</dfn>:
+	at parse time, the legacy syntax is converted into the new syntax,
 	resulting in a [=declared value=] different from the parsed input.
 	These aliases are typically used for handling legacy compatibility requirements,
 	such as converting [=vendor-prefixed=] values to their standard equivalents.