summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorMarcel Ribeiro Dantas <ribeirodantasdm@gmail.com>2022-11-11 10:54:17 -0300
committerGitHub <noreply@github.com>2022-11-11 10:54:17 -0300
commit2ddfedb512c7b95473a5609df470896b2350f147 (patch)
tree03f69b2a425d20cc058efa2a43c0be20ef736b35
parentb8a66e77be6eec952a93cb8bb2c96a86a527b468 (diff)
parent873314f253a37932f836354b482fcda03f0bf505 (diff)
Merge pull request #4539 from nbehrnd/markdown_en
[markdown/en] add link to markdownlint
-rw-r--r--markdown.html.markdown13
1 files changed, 7 insertions, 6 deletions
diff --git a/markdown.html.markdown b/markdown.html.markdown
index a6000910..cfc0ddf3 100644
--- a/markdown.html.markdown
+++ b/markdown.html.markdown
@@ -40,9 +40,9 @@ specific to a certain parser.
Markdown is a superset of HTML, so any HTML file is valid Markdown.
```md
-<!--This means we can use HTML elements in Markdown, such as the comment
-element, and they won't be affected by a markdown parser. However, if you
-create an HTML element in your markdown file, you cannot use markdown syntax
+<!--This means we can use HTML elements in Markdown, such as the comment
+element, and they won't be affected by a markdown parser. However, if you
+create an HTML element in your markdown file, you cannot use markdown syntax
within that element's contents.-->
```
@@ -370,9 +370,10 @@ Ugh this is so ugly | make it | stop
## Markdownlint
In order to simplify work with Markdown and to unify its coding style,
-`Markdownlint` has been created. This tool is available also as a plugin for
-some IDEs and can be used as an utility to ensure validity and readability of
-Markdown.
+`Markdownlint` has been created. Available as a
+[separate tool](https://github.com/markdownlint/markdownlint)
+as well as a plugin for some IDEs, it can be used to ensure validity and
+readability of Markdown.
---