docs: Use backticks when referencing custom command annotations, fixes #5820 #5927
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.
The Issue
Most annotations are references using quotes, except the newest one where I was told to use backticks.
They should all use backticks - it looks silly with one being rendered differently.
How This PR Solves The Issue
Use backticks when referencing annotations for custom commands in the docs.
Remove annotations from the spelling words list, since anything in backticks is ignored for spelling checks.
Manual Testing Instructions
Take a look at custom commands page in the docs.
Automated Testing Overview
N/A
Related Issue Link(s)
Release/Deployment Notes
N/A