fix(docs): Fix mod-morph terms from keycodes to bindings #2393
Conversation
This file contains 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
caksoylar
force-pushed
the
docs/fix-mod-morph-terms
branch
from
7053f18
to
df7783c
Compare
caksoylar
force-pushed
the
docs/fix-mod-morph-terms
branch
from
df7783c
to
6d49389
Compare
Nick-Munnich
approved these changes
Aug 13, 2024
Co-authored-by: Nicolas Munnich <[email protected]>
caksoylar
force-pushed
the
docs/fix-mod-morph-terms
branch
from
4277a1f
to
046541b
Compare
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.
Added more precision to docs, where we don't want to conflate keycodes vs behavior bindings. Also elaborated on the grave escape behavior just in case it isn't clear from the definition.
As an aside, I want to do a pass on all the behavior pages to make them more consistent. Currently the header levels, overall organization, examples etc. are different across many of them.