[CAIP-10] Editorial: minor wordsmithing in ## Canonicalization section #310
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
obstropolos
approved these changes
Aug 14, 2024
|
Approved, but I want @pedrouid to give this a quick glance as well. |
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.
Minor and non-normative.
This is just to draw more attention to the changes being made in namespaces#122, following implementer feedback that the checksum-case/lowercase difference wasn't explicit enough.
If this feels like too much to change on a "Final"-status CAIP, even though it's non-normative and purely editorial, we could go the #288 route and just publish an informational CAIP as a "BCP"-style update. Feels a little overkill to do that just to make the wording clearer, though.