DavidAnson · October 15, 2025 18:30 · Mar 7, 2024 · Aug 27, 2022 · Nov 24, 2015 · May 12, 2015
diff --git a/common-markdown-mistakes.md b/common-markdown-mistakes.md
@@ -8,6 +8,9 @@ GitHub's parser handles some of these cases; other parsers do not.
 
 To catch these problems automatically:
 
-* [markdownlint](https://github.com/mivok/markdownlint/) for Ruby, includes CLI
-* [markdownlint](https://github.com/DavidAnson/markdownlint) for Node.js/io.js, [interactive demo](//dlaa.me/markdownlint/)
-* [markdownlint](https://marketplace.visualstudio.com/items/DavidAnson.vscode-markdownlint) for Visual Studio Code
+* [markdownlint](https://github.com/mivok/markdownlint) for Ruby, includes CLI
+* [markdownlint](https://github.com/DavidAnson/markdownlint) library for Node.js, [interactive web demo](https://dlaa.me/markdownlint/)
+* [markdownlint-cli](https://github.com/igorshubovych/markdownlint-cli) command-line interface for Node.js
+* [markdownlint-cli2](https://github.com/DavidAnson/markdownlint-cli2) command-line interface for Node.js
+* [markdownlint-cli2-action](https://github.com/marketplace/actions/markdownlint-cli2-action) Action for GitHub
+* [vscode-markdownlint](https://marketplace.visualstudio.com/items/DavidAnson.vscode-markdownlint) extension for Visual Studio Code
diff --git a/common-markdown-mistakes.md b/common-markdown-mistakes.md
@@ -4,6 +4,8 @@ Click the `Raw` button to see the source text and understand the author's intent
 
 GitHub's parser handles some of these cases; other parsers do not.
 
+
+
 To catch these problems automatically:
 
 * [markdownlint](https://github.com/mivok/markdownlint/) for Ruby, includes CLI

diff --git a/common-markdown-mistakes.md b/common-markdown-mistakes.md
@@ -1,4 +1,4 @@
-The following snippets show some common [Markdown](http://en.wikipedia.org/wiki/Markdown) mistakes.
+The following snippets show some common [Markdown](https://en.wikipedia.org/wiki/Markdown) mistakes.
 
 Click the `Raw` button to see the source text and understand the author's intent.
 
@@ -7,4 +7,5 @@ GitHub's parser handles some of these cases; other parsers do not.
 To catch these problems automatically:
 
 * [markdownlint](https://github.com/mivok/markdownlint/) for Ruby, includes CLI
-* [markdownlint](https://github.com/DavidAnson/markdownlint) for Node.js/io.js, [interactive demo](//dlaa.me/markdownlint/)
+* [markdownlint](https://github.com/DavidAnson/markdownlint) for Node.js/io.js, [interactive demo](//dlaa.me/markdownlint/)
+* [markdownlint](https://marketplace.visualstudio.com/items/DavidAnson.vscode-markdownlint) for Visual Studio Code
diff --git a/common-markdown-mistakes.md b/common-markdown-mistakes.md
@@ -7,4 +7,4 @@ GitHub's parser handles some of these cases; other parsers do not.
 To catch these problems automatically:
 
 * [markdownlint](https://github.com/mivok/markdownlint/) for Ruby, includes CLI
-* [markdownlint](https://github.com/DavidAnson/markdownlint) for Node.js/io.js
+* [markdownlint](https://github.com/DavidAnson/markdownlint) for Node.js/io.js, [interactive demo](//dlaa.me/markdownlint/)
diff --git a/common-markdown-mistakes.md b/common-markdown-mistakes.md
@@ -2,4 +2,9 @@ The following snippets show some common [Markdown](http://en.wikipedia.org/wiki/
 
 Click the `Raw` button to see the source text and understand the author's intent.
 
-GitHub's parser handles some of these cases; other parsers do not.
+GitHub's parser handles some of these cases; other parsers do not.
+
+To catch these problems automatically:
+
+* [markdownlint](https://github.com/mivok/markdownlint/) for Ruby, includes CLI
+* [markdownlint](https://github.com/DavidAnson/markdownlint) for Node.js/io.js
diff --git a/inconsistent-header-style.md b/inconsistent-header-style.md
@@ -1,14 +1,14 @@
 A
 
-# foolish consistency 
+## foolish consistency 
 
 is the
 
-# hobgoblin #
+## hobgoblin ##
 
 of
 
 little minds
-============
+------------
 
 *Ralph Waldo Emerson*
diff --git a/no-blank-line-before-fence.md b/no-blank-line-before-fence.md
@@ -1,4 +1,5 @@
-Here is some code:
+A haiku of code
 ```
-Without a blank line before it
-```
+Without blank lines around it
+```
+(GitHub gets it right)
diff --git a/no-language-for-code-fence.md b/no-language-for-code-fence.md
@@ -0,0 +1,9 @@
+```
+// Comment and "var" highlighting is only for JavaScript
+var i = 5;
+```
+
+```js
+// Much better here
+var j = 5;
+```
diff --git a/reversed-link.md b/reversed-link.md
@@ -0,0 +1 @@
+A (reversed)[link] goes nowhere
diff --git a/inconsistent-header-style.md b/inconsistent-header-style.md
@@ -9,6 +9,6 @@ is the
 of
 
 little minds
-------------
+============
 
 *Ralph Waldo Emerson*
diff --git a/inconsistent-header-style.md b/inconsistent-header-style.md
@@ -0,0 +1,14 @@
+A
+
+# foolish consistency 
+
+is the
+
+# hobgoblin #
+
+of
+
+little minds
+------------
+
+*Ralph Waldo Emerson*
diff --git a/common-markdown-mistakes.md b/common-markdown-mistakes.md
@@ -1,4 +1,4 @@
-The following snippets show some common [Markdown](http://en.wikipedia.org/wiki/Markdown) errors.
+The following snippets show some common [Markdown](http://en.wikipedia.org/wiki/Markdown) mistakes.
 
 Click the `Raw` button to see the source text and understand the author's intent.
 

diff --git a/-introduction.md → common-markdown-mistakes.md b/-introduction.md → common-markdown-mistakes.md
diff --git a/-introduction.md b/-introduction.md
@@ -1,5 +1,5 @@
 The following snippets show some common [Markdown](http://en.wikipedia.org/wiki/Markdown) errors.
 
-Click the `Raw` button to see what the source text looks like.
+Click the `Raw` button to see the source text and understand the author's intent.
 
 GitHub's parser handles some of these cases; other parsers do not.
diff --git a/ordered-list-numbering.md b/ordered-list-numbering.md
@@ -1,4 +1,4 @@
-1. Counting
+1. Numbering
 2. is
 4. hard.
 8. Let's go shopping.
diff --git a/ordered-list-numbering.md b/ordered-list-numbering.md
@@ -0,0 +1,4 @@
+1. Counting
+2. is
+4. hard.
+8. Let's go shopping.
diff --git a/-introduction.md b/-introduction.md
@@ -0,0 +1,5 @@
+The following snippets show some common [Markdown](http://en.wikipedia.org/wiki/Markdown) errors.
+
+Click the `Raw` button to see what the source text looks like.
+
+GitHub's parser handles some of these cases; other parsers do not.
diff --git a/no-blank-line-after-list.md b/no-blank-line-after-list.md
@@ -1,4 +1,3 @@
 * This is a list
-* followed by
-* some text
+* followed by text
 But there is no blank line
diff --git a/inline-html.md b/inline-html.md
@@ -1 +1 @@
-My favorite HTML tag is the <p> tag.
+A popular HTML tag is the <p> tag.
diff --git a/no-blank-line-before-list.md b/no-blank-line-before-list.md
@@ -1,4 +0,0 @@
-This is text followed by a list:
-* But the two are not
-* separated by a blank
-* line

diff --git a/no-blank-line-after-list.md b/no-blank-line-after-list.md
@@ -0,0 +1,4 @@
+* This is a list
+* followed by
+* some text
+But there is no blank line
diff --git a/no-blank-line-before-fence.md b/no-blank-line-before-fence.md
@@ -0,0 +1,4 @@
+Here is some code:
+```
+Without a blank line before it
+```
diff --git a/inline-html.md b/inline-html.md
@@ -0,0 +1 @@
+My favorite HTML tag is the <p> tag.
diff --git a/no-blank-line-before-list.md b/no-blank-line-before-list.md
@@ -0,0 +1,4 @@
+This is text followed by a list:
+* But the two are not
+* separated by a blank
+* line
Original file line number	Diff line number	Diff line change
		@@ -1 +1 @@
		My favorite HTML tag is the <p> tag.
		A popular HTML tag is the <p> tag.