This repository has been archived by the owner on Apr 24, 2020. It is now read-only.
[Docs] Uniformly apply inline code formatting in README #1070
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
All POWERLEVEL variables and directory paths should be formatted with backticks for inline code. If not marked as code, the ~ home directory can unintentionally apply strikethrough.
dritter
approved these changes
Nov 16, 2018
|
Thx @Wieschie for keeping an eye on the docs! |
|
Thanks for the clean-up, @Wieschie! PRs like this, while perhaps simple to fix, are just as important to the project as code. Thanks so much! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
All POWERLEVEL variables and directory paths should be formatted with backticks for inline code. If not marked as code, the ~ home directory can unintentionally apply strikethrough.