Editorial: modernize/consistify string and "current token" style#12128
Merged
Editorial: modernize/consistify string and "current token" style#12128
Conversation
This replaces 'the string "foo"' and similar with just "foo" and adds "current" where it was missing in reference to current token. This only changes the parsing section, because this spec is huge!
Member
Author
|
This takes out a few changes from #12118 and does them consistently for the syntax section. It doesn't change the style around U+NNNN code points, because that would be a lot... |
zcorpan
approved these changes
Feb 5, 2026
Member
|
Removed the PR template as it's not needed for purely editorial changes. |
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
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.
This replaces 'the string "foo"' and similar with just "foo" and adds
"current" where it was missing in reference to current token.
This only changes the parsing section, because this spec is huge!
/parsing.html ( diff )