Fix README format #344
Merged
Fix README format #344
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
iopred
pushed a commit
that referenced
this pull request
Mar 28, 2017
|
Thanks @Jawnnypoo |
|
No problem! 😄 |
|
This looks still funny to me: |
|
@tsdtsdtsd Yeah, that is kinda odd, but I didn't remove it since I wasn't sure what exactly it was supposed to be |
Merged
|
It should create a headline, but that syntax is wonky sometimes |
ErikMcClure
pushed a commit
to ErikMcClure/discordgo
that referenced
this pull request
Aug 4, 2020
ErikMcClure
pushed a commit
to ErikMcClure/discordgo
that referenced
this pull request
Aug 4, 2020
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.
Weirdly enough, the README was getting out of wack, probably due to the minor GitHub markdown changes that happened recently:
https://github.com/blog/2333-a-formal-spec-for-github-flavored-markdown
Anyhow, this is how it was looking before on the web:
And adding that single line break seems to fix it. 😛