From 5b6be317dc5efc9fb60355f424f2e29f0fe10408 Mon Sep 17 00:00:00 2001 From: Andrew Paseltiner Date: Thu, 19 Dec 2024 14:15:40 -0500 Subject: [PATCH] Lowercase RFC 2119 keywords (#1490) Per https://wicg.github.io/attribution-reporting-api/#w3c-conventions "these words do not appear in all uppercase letters in this specification". --- index.bs | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/index.bs b/index.bs index 1aec5fe138..74875eff62 100644 --- a/index.bs +++ b/index.bs @@ -426,7 +426,7 @@ a [=set=] of [=strings=] |allowedKeys|: value |value|, and the parameters |params| to |entries|. 1. Return a [=structured header/dictionary=] containing |entries|. -Note: The user agent MAY "[=structured header/define new structured fields|grease=]" the +Note: The user agent may "[=structured header/define new structured fields|grease=]" the dictionary structured headers according to the preceding algorithm to help ensure that recipients use a proper structured header parser, rather than naive string equality or `contains` operations, which makes it easier to introduce backwards-compatible @@ -1339,7 +1339,7 @@ However attribution data is inherently cross-site, and operations on storage wou An internal ID is an integer. To get the next internal ID, return an [=internal ID=] strictly -greater than any previously returned by this algorithm. The user agent MAY reset +greater than any previously returned by this algorithm. The user agent may reset this sequence when no [=attribution cache=] entry contains an [=internal ID=]. # Constants # {#constants} @@ -2156,7 +2156,7 @@ To process an attribution eligible response given a [=suitable |contextOrigin|, an [=eligibility=] |eligibility|, a [=boolean=] |fenced|, and a [=response=] |response|: -1. The user-agent MAY ignore the response; if so, return. +1. The user-agent may ignore the response; if so, return. Note: The user-agent may prevent attribution for a number of reasons, such as user opt-out. In these cases, it is preferred to abort the API flow at response time rather than at request time so this @@ -4658,7 +4658,7 @@ Issue: Specify this in terms of