Criterias to requirements #454
Open
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
Same. We switched from “criterias” to “requirements” which is an important change, yet wasn't done in the content.
|
I need more context around why this seems important to consider it. |
|
As to keep it coherent (since I think that was a typo that was forgotten with the change) and not use different words for meaning the same thing. |
|
Another note: reason why I bring it up is because it brought confusion for two clients during a training since meaning of requirement isn't the same as criteria, in its inherent meaning. |
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.
Same. We switched from “criterias” to “requirements” which is an important change, yet wasn't done in the content.