[w3c/browser-payment-api] Change "SHOULD NEVER" to "MUST NOT" (#356)

“Should never” is strong enough that if that is what we mean, then
we should use the corresponding RFC 2119 language.

If we mean less than MUST NOT, then let’s say “SHOULD NOT.”

In this edit I swap in MUST NOT for SHOULD NEVER because I think the
intention is the same.
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/browser-payment-api/pull/356

-- Commit Summary --

  * Merge branch 'w3c/gh-pages' into gh-pages
  * First draft of incognito mode guidance
  * Update example to use 'basic-card' and filter data
  * using theirs
  * Merge remote-tracking branch 'w3c/gh-pages' into gh-pages
  * Merge remote-tracking branch 'w3c/gh-pages' into gh-pages
  * Change "should never" to "must not"

-- File Changes --

    M index.html (2)

-- Patch Links --

https://github.com/w3c/browser-payment-api/pull/356.patch
https://github.com/w3c/browser-payment-api/pull/356.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/pull/356