docs: fix wording in "How it works" page #236
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I think it's better to replace 'SHOULD' by 'MUST'. In the context of guidelines, recommendations, or requirements, "must" and "should" have distinct levels of obligation or expectation: - **Must** indicates a requirement, obligation, or something that is mandatory. It's used when there's no room for discretion or deviation from the directive. In legal or formal contexts, "must" signifies an absolute requirement. - **Should** suggests a recommendation or advice that is strongly encouraged but not mandatory. It implies that there are reasons or benefits to follow the guidance, but it's not an absolute requirement. There may be acceptable reasons or circumstances to deviate from a "should" directive. So, when you see "must," think of it as a non-negotiable rule, whereas "should" is more of a strong suggestion that allows for some exceptions under certain conditions.
|
|
✅ Deploy Preview for casbin ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
hsluoyz
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think it's better to replace 'SHOULD' by 'MUST'.
In the context of guidelines, recommendations, or requirements, "must" and "should" have distinct levels of obligation or expectation:
Must indicates a requirement, obligation, or something that is mandatory. It's used when there's no room for discretion or deviation from the directive. In legal or formal contexts, "must" signifies an absolute requirement.
Should suggests a recommendation or advice that is strongly encouraged but not mandatory. It implies that there are reasons or benefits to follow the guidance, but it's not an absolute requirement. There may be acceptable reasons or circumstances to deviate from a "should" directive.
So, when you see "must," think of it as a non-negotiable rule, whereas "should" is more of a strong suggestion that allows for some exceptions under certain conditions.