diff --git a/index.html b/index.html
index 8f6ae63..71a7ba3 100644
--- a/index.html
+++ b/index.html
@@ -237,7 +237,7 @@
                       
                       - Start by moving repeatedly used code into a function
                       - When your function (or a group of functions related to the same theme) get big enough, move them into another file and expose them using `module.exports`. You can load this using a relative require
-                      - If you have some code that can be used across multiple projects give it it's own readme, tests and `package.json` and publish it to github and npm. There are too many awesome benefits to this specific approach to list here!
+                      - If you have some code that can be used across multiple projects give it its own readme, tests and `package.json` and publish it to github and npm. There are too many awesome benefits to this specific approach to list here!
                       - A good module is small and focuses on one problem
                       - Individual files in a module should not be longer than around 150 lines of JavaScript
                       - A module shouldn't have more than one level of nested folders full of JavaScript files. If it does, it is probably doing too many things