Fixes formatting for Visual Studio Packaging docs #1012
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
Unfortunately, three tildes works as "cross-out" in GFM, and not as "code-sample". As a result, this was breaking the formatting and layout of the bottom of the page. To fix this I have simplified the NuGet Package Manager code sample to use the standard GFM "code" convention.
PHeonix25
changed the title
|
Thanks! |
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.
Unfortunately, three tildes works as ~~~strike-through~~~ in GFM, and not as "code-sample".
As a result, this was breaking the formatting and layout of the bottom of the page.
To fix this I have simplified the NuGet Package Manager code sample to use the standard GFM "code" convention.
NOTE: using the GitHub online editor to make this small change meant that the windows new-lines (^M) got replaced with /r/n - I've left those changes in, but I'm happy to remove it if required.