fixed some spelling mistakes

README.md

@@ -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].

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

markdown/extensions/codehilite.py

@@ -148,7 +148,7 @@ def hilite(self, shebang=True):
                 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 @@ def __init__(self, **kwargs):
                 '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"',
                                    ],
             }

tests/basic/markdown-documentation-basics.html

@@ -211,15 +211,15 @@ <h3>Code</h3>
 <pre><code>I strongly recommend against using any `&lt;blink&gt;` tags.
 
 I wish SmartyPants used named entities like `&amp;mdash;`
-instead of decimal-encoded entites like `&amp;#8212;`.
+instead of decimal-encoded entities like `&amp;#8212;`.
 </code></pre>
 <p>Output:</p>
 <pre><code>&lt;p&gt;I strongly recommend against using any
 &lt;code&gt;&amp;lt;blink&amp;gt;&lt;/code&gt; tags.&lt;/p&gt;
 
 &lt;p&gt;I wish SmartyPants used named entities like
 &lt;code&gt;&amp;amp;mdash;&lt;/code&gt; instead of decimal-encoded
-entites like &lt;code&gt;&amp;amp;#8212;&lt;/code&gt;.&lt;/p&gt;
+entities like &lt;code&gt;&amp;amp;#8212;&lt;/code&gt;.&lt;/p&gt;
 </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>&amp;</code>, <code>&lt;</code>,

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 `&mdash;`
-    instead of decimal-encoded entites like `&#8212;`.
+    instead of decimal-encoded entities like `&#8212;`.
 
 Output:
 
@@ -279,7 +279,7 @@ Output:
 
     <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>
 
 
 To specify an entire block of pre-formatted code, indent every line of