4 files changed, 3 insertions, 5 deletions
diff --git a/docs/plugins/README.md b/docs/plugins/README.md
index 4df62b8..cbcf826 100644
--- a/docs/plugins/README.md
+++ b/docs/plugins/README.md
@@ -1,6 +1,6 @@
 # Plugins
 
-Plugins are the best way to extend GitBook functionalities (ebook and website). There exist plugins to do a lot of things: bring math formulas display support, track visits using Google Analytic, etc.
+Plugins are the best way to extend GitBook functionalities (ebook and website). There exist plugins to do a lot of things: bring math formulas display support, track visits using Google Analytics, etc.
 
 ### How to find plugins?
 
diff --git a/docs/plugins/filters.md b/docs/plugins/filters.md
index 9ee9493..53eca9a 100644
--- a/docs/plugins/filters.md
+++ b/docs/plugins/filters.md
@@ -54,4 +54,4 @@ module.exports = {
         }
     }
 };
-```
-\ No newline at end of file
+```
diff --git a/docs/plugins/hooks.md b/docs/plugins/hooks.md
index 7d81b1d..5eb0e2f 100644
--- a/docs/plugins/hooks.md
+++ b/docs/plugins/hooks.md
@@ -71,7 +71,6 @@ In the `page` hook, `page.content` is the HTML generated from the markdown/ascii
 }
 ```
 
-
 ### Asynchronous Operations
 
 Hooks callbacks can be asynchronous and return promises.
diff --git a/docs/plugins/testing.md b/docs/plugins/testing.md
index 9562b26..4cd2c69 100644
--- a/docs/plugins/testing.md
+++ b/docs/plugins/testing.md
@@ -2,7 +2,7 @@
 
 ### Testing your plugin locally
 
-Testing your plugin on your book before plushing it is possible using [npm link](https://docs.npmjs.com/cli/link).
+Testing your plugin on your book before publishing it is possible using [npm link](https://docs.npmjs.com/cli/link).
 
 In the plugin's folder, run:
 
@@ -19,4 +19,3 @@ $ npm link gitbook-plugin-<plugin's name>
 ### Unit testing on Travis
 
 [gitbook-tester](https://github.com/todvora/gitbook-tester) makes it easy to write **Node.js/Mocha** unit tests for your plugins. Using [Travis.org](https://travis.org), tests can be run on each commits/tags.
-