-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Markdownlint final fixes #532
Conversation
In unsafe-code.md
Reverting to draft status. @jskeet This one caused an exception in the word converter. I'll do some investigation to figure out why. |
The word converter errors were because of typos while working on this warning. We should be good now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll admit I haven't carefully checked every line insertion, but it looks fine with the exception of one rogue deletion which I'm expecting was a mistake.
Great catch @jskeet I fixed that, and then gave the diffs one more proofread. I didn't find any other changes. I'll |
This fixes all the warnings for MD030 (code fenced sections should be surrounded by blank lines.
There's one commit per file. The diffs are somewhat large, but should be trivial to examine visually. This was the lint warning our spec generated the most. 😓 But now, I think we're in a good place. 😀