Thorough spell check of the docs.

Author: waylan

docs/authors.txt

@@ -9,15 +9,15 @@ Primary Authors
 
 [Yuri Takteyev](http://freewisdom.org/)
 
-: Yuri has written much of the current code while procrastingating his Ph.D.
+: Yuri has written much of the current code while procrastinating his Ph.D.
 
 [Waylan Limberg](http://achinghead.com/)
 
 : Waylan is the current maintainer of the code and has written much the current 
   code base, included a complete refactor of the core.  He started out by 
-  authoring mmany of the available extensions and later was asked to join Yuri, 
-  where he began fixing nummrious bugs, adding documentation and making general 
-  improvements to the existing codebase.
+  authoring many of the available extensions and later was asked to join Yuri, 
+  where he began fixing numerous bugs, adding documentation and making general 
+  improvements to the existing code base.
 
 Artem Yunusov
 
@@ -28,7 +28,7 @@ Artem Yunusov
 [Manfed Stienstra](http://www.dwerg.net/)
 
 : Manfed wrote the original version of the script and is responsible for 
-  various parts of the existing codebase.
+  various parts of the existing code base.
 
 David Wolever
 
@@ -40,7 +40,7 @@ Other Contributors
 
 The incomplete list of individuals below have provided patches or otherwise 
 contributed to the project in various ways. We would like to thank everyone 
-who has contributed to the progect in any way.
+who has contributed to the project in any way.
 
 * Eric Abrahamsen
 * Jeff Balogh

docs/change_log.txt

@@ -4,20 +4,20 @@ prev_url:   test_suite.html
 next_title: Release Notes for v2.6
 next_url:   release-2.6.html
 
-Python-Markdown Changelog
+Python-Markdown Change Log
 =========================
 
 ____________: Released version 2.6 ([Notes](release-2.6.html)).
 
-Nov 19, 2014: Released version 2.5.2 (a bugfix release).
+Nov 19, 2014: Released version 2.5.2 (a bug-fix release).
 
-Sept 26, 2014: Released version 2.5.1 (a bugfix release).
+Sept 26, 2014: Released version 2.5.1 (a bug-fix release).
 
 Sept 12, 2014: Released version 2.5.0 ([Notes](release-2.5.html)).
 
 Feb 16, 2014: Released version 2.4.0 ([Notes](release-2.4.html)).
 
-Mar 22, 2013: Released version 2.3.1 (a bugfix release).
+Mar 22, 2013: Released version 2.3.1 (a bug-fix release).
 
 Mar 14, 2013: Released version 2.3.0 ([Notes](release-2.3.html))
 
@@ -43,24 +43,24 @@ Feb 2009: Added support for multi-level lists to new Blockprocessors.
 
 Jan 2009: Added HTML 4 output as an option (thanks Eric Abrahamsen)
 
-Nov 2008: Added Definistion List ext. Replaced old core with BlockProcessors.
+Nov 2008: Added Definition List ext. Replaced old core with Blockprocessors.
 Broken up into multiple files.
 
 Oct 2008: Changed logging behavior to work better with other systems.
-Refactored tree tarversing. Added treap implementation, then replaced with
-OrderedDEict. Renamed various processors to better reflect what they actually
-do. Refactored footnote ext to match php Extra's output.
+Refactored tree traversing. Added `treap` implementation, then replaced with
+OrderedDict. Renamed various processors to better reflect what they actually
+do. Refactored footnote ext to match PHP Extra's output.
 
-Sept 2008: Moved prettifyTree to a Postprocessor, replaced wikilink ext
-with wikilinks (note the s) ext (uses bracketed links instead of CamelCase)
+Sept 2008: Moved `prettifyTree` to a Postprocessor, replaced WikiLink ext
+with WikiLinks (note the s) ext (uses bracketed links instead of CamelCase)
 and various bug fixes.
 
-August 18 2008: Reorganized directory structure. Added a 'docs' dir
+August 18 2008: Reorganized directory structure. Added a 'docs' directory
 and moved all extensions into a 'markdown-extensions' package.
 Added additional documentation and a few bug fixes. (v2.0-beta)
 
 August 4 2008: Updated included extensions to ElementTree. Added a
-seperate commanline script. (v2.0-alpha)
+separate command line script. (v2.0-alpha)
 
 July 2008: Switched from home-grown NanoDOM to ElementTree and
 various related bugs (thanks Artem Yunusov).
@@ -69,24 +69,24 @@ June 2008: Fixed issues with nested inline patterns and cleaned
 up testing framework (thanks Artem Yunusov).
 
 May 2008: Added a number of additional extensions to the
-distribution and other minor changes. Moved repo to git from svn.
+distribution and other minor changes. Moved repository to git from svn.
 
-Mar 2008: Refactored extension api to accept either an
+Mar 2008: Refactored extension API to accept either an
 extension name (as a string) or an instance of an extension
 (Thanks David Wolever). Fixed various bugs and added doc strings.
 
-Feb 2008: Various bugfixes mostly regarding extensions.
+Feb 2008: Various bug-fixes mostly regarding extensions.
 
 Feb 18, 2008: Version 1.7.
 
 Feb 13, 2008: A little code cleanup and better documentation
-and inheritance for pre/post proccessors.
+and inheritance for Preprocessors/Postprocessors.
 
-Feb 9, 2008: Doublequotes no longer html escaped and rawhtml
+Feb 9, 2008: Double-quotes no longer HTML escaped and raw HTML
 honors `<?foo>`, `<@foo>`, and `<%foo>` for those who run markdown on
 template syntax.
 
-Dec 12, 2007: Updated docs. Removed encoding arg from Markdown
+Dec 12, 2007: Updated docs. Removed encoding argument from Markdown
 and markdown as per list discussion. Clean up in prep for 1.7.
 
 Nov 29, 2007: Added support for images inside links. Also fixed
@@ -96,65 +96,65 @@ Nov 19, 2007: `message` now uses python's logging module. Also removed
 limit imposed by recursion in `_process_section()`. You can now parse as
 long of a document as your memory can handle.
 
-Nov 5, 2007: Moved safe_mode code to a textPostprocessor and added
+Nov 5, 2007: Moved `safe_mode` code to a `textPostprocessor` and added
 escaping option.
 
 Nov 3, 2007: Fixed convert method to accept empty strings.
 
-Oct 30, 2007: Fixed BOM removal (thanks Malcolm Tredinnick). Fixed
-infinite loop in bracket regex for inline links.
+Oct 30, 2007: Fixed `BOM` removal (thanks Malcolm Tredinnick). Fixed
+infinite loop in bracket regular expression for inline links.
 
-Oct 11, 2007: LineBreaks is now an inlinePattern. Fixed HR in
-blockquotes. Refactored _processSection method (see tracker #1793419).
+Oct 11, 2007: `LineBreaks` is now an `inlinePattern`. Fixed `HR` in
+blockquotes. Refactored `_processSection` method (see tracker #1793419).
 
-Oct 9, 2007: Added textPreprocessor (from 1.6b).
+Oct 9, 2007: Added `textPreprocessor` (from 1.6b).
 
 Oct 8, 2008: Fixed Lazy Blockquote. Fixed code block on first line.
 Fixed empty inline image link.
 
-Oct 7, 2007: Limit recursion on inlinePatterns. Added a 'safe' tag
-to htmlStash.
+Oct 7, 2007: Limit recursion on inline patterns. Added a 'safe' tag
+to `htmlStash`.
 
 March 18, 2007: Fixed or merged a bunch of minor bugs, including
 multi-line comments and markup inside links. (Tracker #s: 1683066,
 1671153, 1661751, 1627935, 1544371, 1458139.) -> v. 1.6b
 
 Oct 10, 2006: Fixed a bug that caused some text to be lost after
-comments.  Added "safe mode" (user's html tags are removed).
+comments.  Added "safe mode" (user's HTML tags are removed).
 
-Sept 6, 2006: Added exception for PHP tags when handling html blocks.
+Sept 6, 2006: Added exception for PHP tags when handling HTML blocks.
 
 August 7, 2006: Incorporated Sergej Chodarev's patch to fix a problem
-with ampersand normalization and html blocks.
+with ampersand normalization and HTML blocks.
 
-July 10, 2006: Switched to using optparse.  Added proper support for
-unicode.
+July 10, 2006: Switched to using `optparse`.  Added proper support for
+Unicode.
 
 July 9, 2006: Fixed the `<[email protected]>` problem (Tracker #1501354).
 
 May 18, 2006: Stopped catching unquoted titles in reference links.
 Stopped creating blank headers.
 
 May 15, 2006: A bug with lists, recursion on block-level elements,
-run-in headers, spaces before headers, unicode input (thanks to Aaron
+run-in headers, spaces before headers, Unicode input (thanks to Aaron
 Swartz). Sourceforge tracker #s: 1489313, 1489312, 1489311, 1488370,
 1485178, 1485176. (v. 1.5)
 
 Mar. 24, 2006: Switched to a not-so-recursive algorithm with
-_handleInline.  (Version 1.4)
+`_handleInline`.  (Version 1.4)
 
 Mar. 15, 2006: Replaced some instance variables with class variables
 (a patch from Stelios Xanthakis).  Chris Clark's new regexps that do
-not trigger midword underlining.
+not trigger mid-word underlining.
 
 Feb. 28, 2006: Clean-up and command-line handling by Stewart
 Midwinter. (Version 1.3)
 
 Feb. 24, 2006: Fixed a bug with the last line of the list appearing
-again as a separate paragraph.  Incorporated Chris Clark's "mailto"
+again as a separate paragraph.  Incorporated Chris Clark's "mail-to"
 patch.  Added support for `<br />` at the end of lines ending in two or
-more spaces.  Fixed a crashing bug when using ImageReferencePattern.
-Added several utility methods to Nanodom.  (Version 1.2)
+more spaces.  Fixed a crashing bug when using `ImageReferencePattern`.
+Added several utility methods to `Nanodom`.  (Version 1.2)
 
 Jan. 31, 2006: Added `hr` and `hr/` to BLOCK_LEVEL_ELEMENTS and
 changed `<hr/>` to `<hr />`.  (Thanks to Sergej Chodarev.)
@@ -165,14 +165,14 @@ getting wrapped in `<pre><code>`.  (v. 1.1)
 Nov. 19, 2005: Made `<!...`, `<?...`, etc. behave like block-level
 HTML tags.
 
-Nov. 14, 2005: Added entity code and email autolink fix by Tiago
+Nov. 14, 2005: Added entity code and email auto-link fix by Tiago
 Cogumbreiro.  Fixed some small issues with backticks to get 100%
 compliance with John's test suite.  (v. 1.0)
 
-Nov. 7, 2005: Added an unlink method for documents to aid with memory
+Nov. 7, 2005: Added an `unlink` method for documents to aid with memory
 collection (per Doug Sauder's suggestion).
 
-Oct. 29, 2005: Restricted a set of html tags that get treated as
+Oct. 29, 2005: Restricted a set of HTML tags that get treated as
 block-level elements.
 
 Sept. 18, 2005: Refactored the whole script to make it easier to
@@ -193,8 +193,8 @@ pretty-printing. (v. 0.7)
 Aug. 13, 2005: Fixed a number of small bugs in order to conform to the
 test suite.  (v. 0.6)
 
-Aug. 11, 2005: Added support for inline html and entities, inline
-images, autolinks, underscore emphasis. Cleaned up and refactored the
+Aug. 11, 2005: Added support for inline HTML and entities, inline
+images, auto-links, underscore emphasis. Cleaned up and refactored the
 code, added some more comments.
 
 Feb. 19, 2005: Rewrote the handling of high-level elements to allow
@@ -203,7 +203,7 @@ multi-line list items and all sorts of nesting.
 Feb. 3, 2005: Reference-style links, single-line lists, backticks,
 escape, emphasis in the beginning of the paragraph.
 
-Nov. 2004: Added links, blockquotes, html blocks to Manfred
+Nov. 2004: Added links, blockquotes, HTML blocks to Manfred
 Stienstra's code
 
 Apr. 2004: Manfred's version at <http://www.dwerg.net/projects/markdown/>

docs/cli.txt

@@ -23,18 +23,18 @@ following format:
 
     $ python -m markdown [options] [args]
 
-That will run the module as a script with the options and args provided. 
+That will run the module as a script with the options and arguments provided. 
 
 At its most basic usage, one would simply pass in a file name as the only argument:
 
     $ python -m markdown input_file.txt
 
-Piping input and output (on STDIN and STDOUT) is fully supported as well. 
+Piping input and output (on `STDIN` and `STDOUT`) is fully supported as well. 
 For example:
 
     $ echo "Some **Markdown** text." | python -m markdown > output.html
 
-Use the `--help` option for a list all available options and args:
+Use the `--help` option for a list all available options and arguments:
 
     $ python -m markdown --help
 
@@ -44,53 +44,53 @@ follow the instructions below to use a wrapper script:
 Setup
 -----
 
-Upon installation, the ``markdown_py`` script will have been copied to
+Upon installation, the `markdown_py` script will have been copied to
 your Python "Scripts" directory. Different systems require different methods to
 ensure that any files in the Python "Scripts" directory are on your system 
 path.
 
 * **Windows**:
 
     Assuming a default install of Python on Windows, your "Scripts" directory 
-    is most likely something like ``C:\\Python26\Scripts``. Verify the location
+    is most likely something like `C:\\Python26\Scripts`. Verify the location
     of your "Scripts" directory and add it to you system path.
 
-    Calling ``markdown_py`` from the command line will call the wrapper batch 
-    file ``markdown_py.bat`` in the "Scripts" directory created during install.
+    Calling `markdown_py` from the command line will call the wrapper batch 
+    file `markdown_py.bat` in the `"Scripts"` directory created during install.
 
 * __*nix__ (Linux, OSX, BSD, Unix, etc.):
 
     As each *nix distribution is different and we can't possibly document all 
     of them here, we'll provide a few helpful pointers:
 
     * Some systems will automatically install the script on your path. Try it 
-      and see if it works. Just run ``markdown_py`` from the command line.
+      and see if it works. Just run `markdown_py` from the command line.
 
     * Other systems may maintain a separate "Scripts" ("bin") directory which 
       you need to add to your path. Find it (check with your distribution) and
       either add it to your path or make a symbolic link to it from your path.
 
-    * If you are sure ``markdown_py`` is on your path, but it still isn't being
+    * If you are sure `markdown_py` is on your path, but it still is not being
       found, check the permissions of the file and make sure it is executable.
 
-    As an alternative, you could just ``cd`` into the directory which contains
+    As an alternative, you could just `cd` into the directory which contains
     the source distribution, and run it from there. However, remember that your
     markdown text files will not likely be in that directory, so it is much 
-    more convenient to have ``markdown_py`` on your path.
+    more convenient to have `markdown_py` on your path.
 
 !!!Note 
-    Python-Markdown uses "markdown_py" as a script name because
+    Python-Markdown uses `"markdown_py"` as a script name because
     the Perl implementation has already taken the more obvious name "markdown".
     Additionally, the default Python configuration on some systems would cause a 
-    script named "markdown.py" to fail by importing itself rather than the markdown
-    library. Therefore, the script has been named "markdown_py" as a compromise. If
+    script named `"markdown.py"` to fail by importing itself rather than the markdown
+    library. Therefore, the script has been named `"markdown_py"` as a compromise. If
     you prefer a different name for the script on your system, it is suggested that
     you create a symbolic link to `markdown_py` with your preferred name.
 
 Usage
 -----
 
-To use ``markdown_py`` from the command line, run it as 
+To use `markdown_py` from the command line, run it as 
 
     $ markdown_py input_file.txt
 
@@ -133,15 +133,15 @@ above example might look like this:
 		UNIQUE_IDS: True
 
 Note that while the `--extension_configs` option does specify the "markdown.extensions.footnotes" 
-extension, you still need to load the extension with the `-x` option, or the configs for that
+extension, you still need to load the extension with the `-x` option, or the configuration for that
 extension will be ignored.
 
-The `--extension_configs` option will only support YAML config files if [PyYaml] is
+The `--extension_configs` option will only support YAML configuration files if [PyYAML] is
 installed on your system. JSON should work with no additional dependencies. The format
-of your config file is automatically detected.
+of your configuration file is automatically detected.
 
 !!!warning
-	The previously documented method of appending the extension configs as a string to the 
+	The previously documented method of appending the extension configuration options as a string to the 
 	extension name will be deprecated in Python-Markdown version 2.6. The `--extension_configs` 
 	option should be used instead. See the [2.5 release notes] for more information.
 

docs/extensions/admonition.txt

@@ -26,7 +26,7 @@ Admonitions are created using the following syntax:
 
         This is the second paragraph.
 
-`type` will be used as the CSS classname and as default title. It must be a
+`type` will be used as the CSS class name and as default title. It must be a
 single word. So, for instance:
 
     !!! note