Trivial: Split Keyword Behaviors in to better subsections #622
Conversation
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
This does not change any text at all. The initial part of the Keyword Behaviors section is too long. Put some of the existing paragraphs into subsections on keyword interactions, and on default behaviors, which are very distinct topics. This left the paragraph on extension keywords orphaned, so I moved it up. The topic of extension keywords will be revisited in detail with the vocabulary changes, so it's best not to worry too much about exactly where this paragraph goes right now.
dlax
approved these changes
Jun 22, 2018
gregsdennis
added
clarification
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 does not change any text at all. The initial part of
the Keyword Behaviors section is too long. Put some of the
existing paragraphs into subsections on keyword interactions,
and on default behaviors, which are very distinct topics.
This left the paragraph on extension keywords orphaned, so
I moved it up. The topic of extension keywords will be
revisited in detail with the vocabulary changes, so it's best
not to worry too much about exactly where this paragraph goes
right now.
As this is purely a formatting / clarity change, it will not sit
up for the full 2 weeks (per longstanding policy).