Skip to content

Commit 8e0336a

Browse files
committed
[css-highlights-api] Avoid use of RFC2119 keywords in non-normative text
1 parent 24e966e commit 8e0336a

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

css-highlight-api-1/Overview.bs

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -229,16 +229,16 @@ Registering Custom Highlights</h3>
229229
The <dfn>custom highlight name</dfn> assigned to a [=custom highlight=] when it is [=registered=]
230230
is used to identify the highlight during styling (see [[#styling-highlights]]).
231231

232-
Note: When registering a [=custom highlight=], authors are recommended to use a
232+
Note: When registering a [=custom highlight=], authors are advised to use a
233233
[=custom highlight name=] that is a valid CSS [=identifier=]. Using a name that is not a valid
234234
identifier can make the highlight hard, and in some cases impossible, to style via CSS.
235235

236236
Note: It is possible to [=register=] a [=custom highlight=] with more than one [=custom highlight name=].
237237
However, using more than one name to style a highlight will assign the highlight multiple different sets
238238
of styles, without a way to control the stacking order of conflicting styles within these sets
239-
during [[#painting|painting]]. This may be limiting for authors and may cause confusing painting behavior
239+
during [[#painting|painting]]. This could be limiting for authors and could cause confusing painting behavior
240240
(see the <a href="#styling-problems-with-multiple-names-per-highlight">example</a> below for more context). Therefore,
241-
<b>it is recommended that authors only use one name per highlight during styling</b>.
241+
<b>authors are advised to only use one name per highlight during styling</b>.
242242
<div class=example id=styling-problems-with-multiple-names-per-highlight>
243243
<xmp highlight=html>
244244
<style>
@@ -261,7 +261,7 @@ Registering Custom Highlights</h3>
261261
</script>
262262
</xmp>
263263
In the example above, the same [=custom highlight=] object is [=registered=] under the names 'foo' and 'bar'.
264-
Since each of the [=style rules=] target the same highlight and have the same [=specificity=], authors may
264+
Since each of the [=style rules=] target the same highlight and have the same [=specificity=], authors might
265265
expect the last rule to win in cascading order and the highlighted content to be green. However, each highlight
266266
name gets an independent set of highlight styles, and the highlight will be painted once per name. In
267267
this case, because 'foo' was registered before 'bar', the highlight will be first painted with 'foo''s

0 commit comments

Comments
 (0)