-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
editorial: Use "content navigable" instead of "nested navigable" #1750
editorial: Use "content navigable" instead of "nested navigable" #1750
Conversation
d9d74cc
to
10153af
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW, I'm not part of the WG and was hoping this PR could be marked as non-substantive. If not, I can talk to my AC rep and join, but these things always take a while. |
jgraham marked as non substantive for IPR from ash-nazg. |
The term was renamed in the HTML spec in whatwg/html#8712 so the current reference was broken as mentioned in w3c#1735. While here, use ReSpec's shorthand syntax to refer to these sub concepts directly and avoid having to specifically link to them in the index at the end of the document.
10153af
to
7679754
Compare
I've force-pushed to my branch to trigger a new CI run and everything looks fine now that the PR has been marked non-substantive. |
Thanks @rakuco! |
SHA: e64e2c8 Reason: push, by whimboo Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
The term was renamed in the HTML spec in whatwg/html#8712 so the current reference was broken as mentioned in #1735.
While here, use ReSpec's shorthand syntax to refer to these sub concepts directly and avoid having to specifically link to them in the index at the end of the document.
Preview | Diff