[docs] fix formatting on install guide #1245
Open
+3
−3
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
I don't really know why, but it seems like using HTML and code (`` ` ``) on the same line in a list item isn't working. See: [before](https://i.imgur.com/6hvQKKO.png) But, if you simply change `` ` `` to `<code>` (which is what it expands to currently anyways), it'll render as expected. Of course this could mess things up if `` ` `` ever expanded to something other than `<code>`, but the current setup doesn't work either so might as well.
|
@facebook-github-bot has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
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 don't really know why, but it seems like using HTML and code (
`) on the same line in a list item isn't working.See: before (first two unordered list items under "System Requirements")
If we change
`to<code>(which is what it expands to currently anyways), it'll render as expected.Of course this could mess things up if
`ever expanded to something other than<code>, but the current setup doesn't work either so might as well.