Conversation
✅ Deploy Preview for graphql-spec-draft ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
benjie
commented
Dec 15, 2022
mjmahone
approved these changes
Jan 5, 2023
Contributor
mjmahone
left a comment
There was a problem hiding this comment.
One nit but the actual changes look good.
mjmahone
approved these changes
Jan 5, 2023
rivantsov
reviewed
Jan 5, 2023
Member
Author
|
I looked into using vale.sh but that looks like it's going to be a fair amount of setup (not least because it's a native binary, so getting it running everywhere is a bit more complex than an |
Member
Author
|
Two TSC approvals, editorial only, based on last night's discussion I'm going to go ahead and merge it 👍 |
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.
@rivantsov pointed out in #981 that there is inconsistent capitalization in the spec.
I've done some research and have concluded that our style seems to most-closely match the AP style guide, so I have worked my way through every heading in the document and applied this style to them. I've also outlined the very basics of this in a style guide document.
You can see some of my analysis in this comment:
#981 (comment)
After that I expanded to looking at all headings in the document. I include below the before/after for the document headings, sorted alphabetically, using
grep -hEr '(^#|^\*\*.*\*\*$)' . | sort -ubefore
after
Closes #981