Minor fixes and making style consistent in Markdown files #99
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
Daniel-Worrall
added
the
documentation
I used Prettier and markdownlint to (mostly) automatically make the formatting and style used consistent. I also fixed a few relatively minor things like an incorrect link and a couple of improperly formatted dates in the changelog.
PanisSupraOmnia
force-pushed
the
chore/markdown-style-and-minor-fixes
branch
from
fb7b850
to
0f57d97
Compare
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.
Summary
I had noticed that there was a lot of inconsistency of style in our Markdown files. Not a big deal, but I also wanted to fix a few small issues I'd noticed, so it was easy to just wrap all the changes up together.
If y'all think my moving the README badges from the top to just under the h1 is dumb, I'll yeet that commit and re-push.
Fixed