SHOULD over RECOMMENDED

[leebyron]

Noticed this in the latest spec text, ideally we use "SHOULD" instead of "RECOMMENDED" to simplify the prose alongside where "MUST" is used.

That would be more internally consistent since we use "SHOULD" elsewhere in the text, reducing the set of terms we use

(note: RECOMMENDED is a synonym for SHOULD https://datatracker.ietf.org/doc/html/rfc2119)

[leebyron]

cc @graphql/tsc

[martinbonnin]

FWIW, the "RECOMMENDED" wording grew on me. I know those are synonyms in the RFC but I find it to be a tiny bit softer. Especially since a lot of this spec is about allowing users to use different status codes for observability, I like that "RECOMMENDED" makes it clear that alternatives are possible.

But it might very well be that I have looked at this spec for too long so definitely welcome other people feedbacks.