Fix markdown typos in Contributing docs page #846
Merged
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
While this fixes the backtick-on-backtick problem by using a zero-width space, it's still confusing to see `erb` in the source code while referencing `html` in the copy.
|
This pull request is automatically deployed with Now. |
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.
I found a few markdown typos in the Getting Started/Contributing docs page, that were ultimately generating glitches in the output text.
PS: I haven't checked how the markdown file renders in the final template — I just validated the markdown syntax with GitHub's preview mode (which was catching the same problems found on the Primer website)