diff options
author | Bastian Venthur <mail@venthur.de> | 2022-06-17 14:46:44 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-06-17 08:46:44 -0400 |
commit | 77fb7f1b51076becff488a9b42ef2883153262a0 (patch) | |
tree | db17ffcd000d75c0a255987773f37e627dd419f6 | |
parent | 97359a4a93c0158e39f80ba82e8c99db1ffea4d9 (diff) | |
download | python-markdown-77fb7f1b51076becff488a9b42ef2883153262a0.tar.gz |
fixed some spelling mistakes
-rw-r--r-- | README.md | 2 | ||||
-rw-r--r-- | docs/change_log/release-3.4.md | 2 | ||||
-rw-r--r-- | markdown/extensions/codehilite.py | 4 | ||||
-rw-r--r-- | tests/basic/markdown-documentation-basics.html | 4 | ||||
-rw-r--r-- | tests/basic/markdown-documentation-basics.txt | 4 |
5 files changed, 8 insertions, 8 deletions
@@ -60,5 +60,5 @@ You may report bugs, ask for help, and discuss various other issues on the [bug Code of Conduct --------------- -Everyone interacting in the Python-Markdown project's codebases, issue trackers, +Everyone interacting in the Python-Markdown project's code bases, issue trackers, and mailing lists is expected to follow the [Code of Conduct]. diff --git a/docs/change_log/release-3.4.md b/docs/change_log/release-3.4.md index ade0ff8..9d1cd17 100644 --- a/docs/change_log/release-3.4.md +++ b/docs/change_log/release-3.4.md @@ -34,7 +34,7 @@ In addition, tests were moved to the modern test environment. Various objects were deprecated in version 3.0 and began raising deprecation warnings (see the [version 3.0 release notes] for details). Any of those object -which remained in version 3.3 have been removed from the codebase in version 3.4 +which remained in version 3.3 have been removed from the code base in version 3.4 and will now raise errors. A summary of the objects are provided below. [version 3.0 release notes]: release-3.0.md diff --git a/markdown/extensions/codehilite.py b/markdown/extensions/codehilite.py index 4721c59..a54ba21 100644 --- a/markdown/extensions/codehilite.py +++ b/markdown/extensions/codehilite.py @@ -148,7 +148,7 @@ class CodeHilite: except ValueError: # pragma: no cover lexer = get_lexer_by_name('text', **self.options) if not self.lang: - # Use the guessed lexer's langauge instead + # Use the guessed lexer's language instead self.lang = lexer.aliases[0] lang_str = f'{self.lang_prefix}{self.lang}' if isinstance(self.pygments_formatter, str): @@ -299,7 +299,7 @@ class CodeHiliteExtension(Extension): 'Prefix prepended to the language when use_pygments is false. Default: "language-"' ], 'pygments_formatter': ['html', - 'Use a specific formatter for Pygments hilighting.' + 'Use a specific formatter for Pygments highlighting.' 'Default: "html"', ], } diff --git a/tests/basic/markdown-documentation-basics.html b/tests/basic/markdown-documentation-basics.html index 97c1e31..fd2e687 100644 --- a/tests/basic/markdown-documentation-basics.html +++ b/tests/basic/markdown-documentation-basics.html @@ -211,7 +211,7 @@ it easy to use Markdown to write about HTML example code:</p> <pre><code>I strongly recommend against using any `<blink>` tags. I wish SmartyPants used named entities like `&mdash;` -instead of decimal-encoded entites like `&#8212;`. +instead of decimal-encoded entities like `&#8212;`. </code></pre> <p>Output:</p> <pre><code><p>I strongly recommend against using any @@ -219,7 +219,7 @@ instead of decimal-encoded entites like `&#8212;`. <p>I wish SmartyPants used named entities like <code>&amp;mdash;</code> instead of decimal-encoded -entites like <code>&amp;#8212;</code>.</p> +entities like <code>&amp;#8212;</code>.</p> </code></pre> <p>To specify an entire block of pre-formatted code, indent every line of the block by 4 spaces or 1 tab. Just like with code spans, <code>&</code>, <code><</code>, diff --git a/tests/basic/markdown-documentation-basics.txt b/tests/basic/markdown-documentation-basics.txt index 6de671a..b0932f3 100644 --- a/tests/basic/markdown-documentation-basics.txt +++ b/tests/basic/markdown-documentation-basics.txt @@ -270,7 +270,7 @@ it easy to use Markdown to write about HTML example code: I strongly recommend against using any `<blink>` tags. I wish SmartyPants used named entities like `—` - instead of decimal-encoded entites like `—`. + instead of decimal-encoded entities like `—`. Output: @@ -279,7 +279,7 @@ Output: <p>I wish SmartyPants used named entities like <code>&mdash;</code> instead of decimal-encoded - entites like <code>&#8212;</code>.</p> + entities like <code>&#8212;</code>.</p> To specify an entire block of pre-formatted code, indent every line of |