networkException/.profile
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

README: Update non experimental key words from RFC 2119 to RFC 8174

Browse source 
While both RFC 2119 and RFC 8174 are considered best current practise
by BCP 14, this document is compliant with the more strict RFC 8174
already.
This commit is contained in:
networkException 2022-07-19 14:50:40 +02:00
parent c02cd7f62e
commit 65ccb4bc16
Signed by: networkException
GPG key ID: E3877443AE684391
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -1,6 +1,6 @@
# Hi I'm networkException
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT" "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119](https://www.rfc-editor.org/rfc/rfc2119.html).
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [BCP 14](https://www.rfc-editor.org/bcp/bcp14) [[RFC2119]](https://www.rfc-editor.org/rfc/rfc2119) [[RFC8174]](https://www.rfc-editor.org/rfc/rfc8174) when, and only when, they appear in all capitals, as shown here.
> The key words "MUST (BUT WE KNOW YOU WON'T)", "SHOULD CONSIDER", "REALLY SHOULD NOT", "OUGHT TO", "WOULD PROBABLY", "MAY WISH TO", "COULD", "POSSIBLE", and "MIGHT" in this document are to be interpreted as described in [RFC 6919](https://www.rfc-editor.org/rfc/rfc6919.html).