diff --git a/CHANGELOG.md b/CHANGELOG.md
index 760c370d1..dd16f8756 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -82,7 +82,7 @@ The private parameter has removed, use a access
 
 ### Bug Fixes
 
-* [@see](https://github.com/see) tags incorrectly formatted in markdown ouput fixed [#1337](https://github.com/documentationjs/documentation/issues/1337) ([5d8d450](https://github.com/documentationjs/documentation/commit/5d8d4504d52a5bb0a0432bf399bbd82d9e5ea7fc))
+* [@see](https://github.com/see) tags incorrectly formatted in markdown output fixed [#1337](https://github.com/documentationjs/documentation/issues/1337) ([5d8d450](https://github.com/documentationjs/documentation/commit/5d8d4504d52a5bb0a0432bf399bbd82d9e5ea7fc))
 
 ### [13.2.1](https://github.com/documentationjs/documentation/compare/v13.2.0...v13.2.1) (2021-04-06)
 
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1938ba710..2169a477e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -39,6 +39,6 @@ Release process:
 
 * Confirm that `master` passes CI tests
 * Run `npm run release` or in case it's a prerelease you'd run i.e. `npm run release -- --prerelease alpha`
-  * It will automatically update teh version in package.json and make a git tag.
+  * It will automatically update the version in package.json and make a git tag.
 * Push commits
 * npm publish
diff --git a/docs/THEMING.md b/docs/THEMING.md
index cd9761c9f..a2d4a4b00 100644
--- a/docs/THEMING.md
+++ b/docs/THEMING.md
@@ -34,6 +34,7 @@ for some ideas.
 - You can now make changes that will show up when you generate your docs using your theme.   Example `package.json` `scripts` entry: `"documentation build index.js -f html -o docs --theme node_modules/docjs-theme"`
 
 #### Changes to Default Theme Via documentation.yml
+
 If a documentation.yml file is used to establish a table of contents for your documentation, small changes to the default style can be made via a <style> element in the documentation.yml file. 
   
 For example, if you have you have a section header and text to describe the section, you can put it at the same level of the text as shown below:
@@ -60,7 +61,7 @@ For example, if you have you have a section header and text to describe the sect
       ### Sub Section header
       Text that describes the section and sub-section here.
 ```
-Any changes to elements and classes that also exist in the standard theme will be overwridden by what is in the documentation.yml. This opens up the possiblitity of the same CSS being defined twice, which can be confusing and is not best practice. However, it is easy to change HTML style this way. Recommend only using classes defined this way that do not exist in the standard documentation.js theme.
+Any changes to elements and classes that also exist in the standard theme will be overwritten by what is in the documentation.yml. This opens up the possibility of the same CSS being defined twice, which can be confusing and is not best practice. However, it is easy to change HTML style this way. Recommend only using classes defined this way that do not exist in the standard documentation.js theme.
 
 ### Theming Markdown
 
diff --git a/src/output/markdown_ast.js b/src/output/markdown_ast.js
index 507942818..09ca97fe6 100644
--- a/src/output/markdown_ast.js
+++ b/src/output/markdown_ast.js
@@ -55,7 +55,7 @@ function buildMarkdownAST(comments, config) {
 
   /**
    * Generate an AST chunk for a comment at a given depth: this is
-   * split from the main function to handle hierarchially nested comments
+   * split from the main function to handle hierarchically nested comments
    *
    * @param {number} depth nesting of the comment, starting at 1
    * @param {Object} comment a single comment