docs: Fix keyboard shortcut for strikethrough #4984
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
Simple PR to fix the keyboard shortcut for strikethrough text formatting.
✅ Deploy Preview for tiptap-embed ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
cmayoracurzio
changed the title
cmayoracurzio
changed the title
janthurau
approved these changes
Mar 20, 2024
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.
Please describe your changes
Simple PR to fix docs, with regards to the keyboard shortcut for strikethrough text formatting.
How did you accomplish your changes
Simple markdown editing of
keyboard-shortcuts.md.How have you tested your changes
Tested manually with Tiptap editor in React and Next.js projects.
How can we verify your changes
Check the keyboard shortcuts that are defined in strike extension source code.
Checklist