Update 'exec' editor.md to include link to editor tools documentation #8208
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
Added a blockquote section to guide towards the editor tools documentation. This needs to be obvious to someone reading the documentation. Probably all of those tools should even be listed under the exec page as well. Please include obvious links to relevant documentation. Especially with something that absolutely requires knowing specific strings from another documentation page.
garrettHensley
requested review from
NikoPenev21,
nelito987 and
martintabakov
as code owners
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 a blockquote section to guide towards the editor tools documentation. This needs to be obvious to someone reading the documentation. Probably all of those tools should even be listed under the exec page as well.
Please include obvious links to relevant documentation. Especially with something that absolutely requires knowing specific strings from another documentation page.
Note to external contributors - make sure to sign our Contribution License Agreement (CLA) first:
https://docs.google.com/forms/d/e/1FAIpQLSduN9hHUJpnjr_KOGsmSM_yGO-KKKggCJhiaOlEOLig6_Wkbg/viewform