Gregsdennis/consistency scan#1654
Merged
jdesrosiers merged 10 commits intomainfrom Jan 7, 2026
Merged
Conversation
jdesrosiers
requested changes
Dec 22, 2025
Member
jdesrosiers
left a comment
There was a problem hiding this comment.
🎉
Looks like part of it was a bad merge at one point. Glad you caught all these things. I didn't check the footnote numbering changes. I'm just going to trust that it makes sense. I want to replace footnotes with something a little more friendly anyway, so it wouldn't be the end of the world if something broke there.
Co-authored-by: Jason Desrosiers <jdesrosi@gmail.com>
jdesrosiers
approved these changes
Dec 23, 2025
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.
What kind of change does this PR introduce?
edit
Issue & Discussion References
Relates to #1612
Summary
I had Copilot do a quick consistency scan of the specs. It found a few language issues, so I fixed them.
Does this PR introduce a breaking change?
No