Remove all caps defined terms, update date#72
Merged
Conversation
dlemire60
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In the Language Spec the "component names" had been all-caps (e.g., ACTION). That was change in their issue 76; this PR aligns the HTTPS spec. This is a non-material change; the only place those terms appear in all caps is the naming conventions section (1.5.1).
This PR also updates the document date and the date for this version in the document history table, Annex D, to 27 March, when we anticipate posting WDs to instigate CSD/PRD ballots.