This repository has been archived by the owner on Sep 26, 2019. It is now read-only.
fix documentation formatting #1779
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
Double dashes have to be between backticks if you don't want them to be shown as a long dash. Code blocks increment needs to be done by two spaces at a time or it breaks.
MadelineMurray
approved these changes
Jul 30, 2019
MadelineMurray
pushed a commit
to MadelineMurray/pantheon
that referenced
this pull request
Jul 30, 2019
Double dashes have to be between backticks if you don't want them to be shown as a long dash. Code blocks increment needs to be done by two spaces at a time or it breaks.
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.
PR description
Double dashes have to be between backticks if you don't want them to be shown
as a long dash.
Code blocks increment needs to be done by two spaces at a time or it breaks.
Fixed Issue(s)
No issue created for this small fix