fixing typos across documentation in gh-pages

README.md

@@ -1,7 +1,7 @@
 [![MEAN.JS Logo](http://meanjs.org/img/logo-small.png)](http://meanjs.org/)
 
 # The Website
-This branch of the repository is for the http://meanjs.org/ website which inludes the documentation for the [MEAN.JS Project](https://github.com/meanjs/mean). 
+This branch of the repository is for the http://meanjs.org/ website which includes the documentation for the [MEAN.JS Project](https://github.com/meanjs/mean). 
 
 # Testing / Contributing
 This website uses [Jekyll!](http://jekyllrb.com/) to serve web pages, which means you need to install jekyll on your computer to test it! 

_includes/docs/0.3.x/angularjsmodules.html

@@ -52,7 +52,7 @@ <h1>AngularJS Modules</h1>
 index.html
 </pre>
       <p>
-        Reorganizing the project this way helped us create bigger projects that are more maintainable in the long term. For a while we had fun using this but lately we found out that wasn’t enough. Now instead of bloating a single JavaScript file, we had pretty big folders containing ~20 controllers, and even more views in the partials folder.
+        Reorganizing the project this way helped us create bigger projects that are more maintainable in the long term. For a while we had fun using this but lately we found out that wasn't enough. Now instead of bloating a single JavaScript file, we had pretty big folders containing ~20 controllers, and even more views in the partials folder.
       </p>
       <p>
         Luckily, when the original MEAN.IO boilerplate gained some traction, we got a chance to talk to some great AngularJS developers writing blogs and working on some popular libraries. One of the greatest topics in our conversations was Angular’s modularity.
@@ -165,7 +165,7 @@ <h4>Vertical Modules Are Better</h4>
 
       <h4>New Folder Structure</h4>
       <p>
-        Using vertical modules only solves half the problem because we still use horizontal approach in our folder structure. This means that all your application controllers will reside in the same folder, as are all the services, directives, filters, and views. In this case you wouldn’t be able to associate a file with its module until you open it.
+        Using vertical modules only solves half the problem because we still use horizontal approach in our folder structure. This means that all your application controllers will reside in the same folder, as are all the services, directives, filters, and views. In this case you wouldn't be able to associate a file with its module until you open it.
       </p>
       <p>
         So we converted our application structure to a vertical structure to fit the vertical modular approach:
@@ -207,10 +207,10 @@ <h4>New Folder Structure</h4>
         This structure allow clear separation of functionality and concerns, so just by looking at the folder structure you can start asking questions about your modules, for example why does the users module have no tests? (hint: Its our fault and we plan to add those :)).
       </p>
       <p>
-        But we didn’t want to stop at this point!
+        But we didn't want to stop at this point!
       </p>
       <p>
-        Because we are building a full-stack solution, won’t it be great if module files could be automatically included in the backend view HTML, eliminating common import mistakes? We do two things to help with this issue:
+        Because we are building a full-stack solution, won't it be great if module files could be automatically included in the backend view HTML, eliminating common import mistakes? We do two things to help with this issue:
       </p>
       <ol>
         <li>
@@ -256,7 +256,7 @@ <h4>New Folder Structure</h4>
       </ol>
       <h4>ApplicationConfiguration</h4>
       <p>
-        While the angular module system is quite robust it lacks a few options, mainly the abiliy to add dependencies to the main module after it was already created. Because of that we use the <b>ApplicationConfiguration</b> object to maintain a list of modules, which the main module will use as depenedencies. If it weren't for the <b>ApplicationConfiguration</b>, you would have to register your module in two place:
+        While the angular module system is quite robust it lacks a few options, mainly the ability to add dependencies to the main module after it was already created. Because of that we use the <b>ApplicationConfiguration</b> object to maintain a list of modules, which the main module will use as dependencies. If it weren't for the <b>ApplicationConfiguration</b>, you would have to register your module in two place:
       </p>
       <ol>
         <li>
@@ -268,7 +268,7 @@ <h4>ApplicationConfiguration</h4>
         </li>
       </ol>
       <p>
-        This can become an annoying pitfull, so we added the <b>ApplicationConfiguration</b> that is loaded before all the modules file. The <b>ApplicationConfiguration</b> global object expose a method named <b>registerModule</b>, this method will create the new angular module and add it to list of dependencies of the main application module.
+        This can become an annoying pitfall, so we added the <b>ApplicationConfiguration</b> that is loaded before all the modules file. The <b>ApplicationConfiguration</b> global object expose a method named <b>registerModule</b>, this method will create the new angular module and add it to list of dependencies of the main application module.
       </p>
       <p>
         We recommend that you take a look at the code that is placed inside the <b>/public/config.js</b> file.
@@ -279,7 +279,7 @@ <h4>Module Structure</h4>
       </p>
       <p>
 
-        To add a new module, you’ll have to create a new folder in the <b>public/modules</b> folder. The directory structure should look something like this:
+        To add a new module, you'll have to create a new folder in the <b>public/modules</b> folder. The directory structure should look something like this:
       </p>
       <pre>
 |-module 
@@ -303,7 +303,7 @@ <h4>Module Structure</h4>
       <pre>
 'use strict';
 
-// Use Applicaion configuration module to register a new module
+// Use Application configuration module to register a new module
 ApplicationConfiguration.registerModule('moduleName');
 </pre>
 
@@ -316,7 +316,7 @@ <h4>Module Tests</h4>
         Adding Karma tests is a simple task, and you can follow the <a href="#article-example">Article Example</a> to learn all about it.
       </p>
       <p>
-        But here is another neat feature: loading your module tests is also done automatically! Karam config file will iterate through the module folder and add your new module tests as well. Don't worry! if you haven't written any tests karma will skip your module and just run the tests you already have.
+        But here is another neat feature: loading your module tests is also done automatically! Karma config file will iterate through the module folder and add your new module tests as well. Don't worry! if you haven't written any tests karma will skip your module and just run the tests you already have.
       </p>
       <p class="alert alert-danger">
         <b>Notice:</b> Your test files should be placed in the <b>module/tests</b> folder or else MEAN won't ignore them and add them in the HTML as script files.

_includes/docs/0.3.x/configuration.html

@@ -83,23 +83,23 @@ <h2>Assets Configuration</h2>
         </dd>
         <dt>config.assets.js</dt>
         <dd>
-          A list of glob patterns idicating the project JavaScript project files.
+          A list of glob patterns indicating the project JavaScript project files.
         </dd>
         <dt>config.assets.tests</dt>
         <dd>
-          A list of glob patterns idicating the project <b>Jasmine</b> test files.
+          A list of glob patterns indicating the project <b>Jasmine</b> test files.
         </dd>
         <dt>config.assets.lib</dt>
         <dd>
-          <p>A list of glob patterns idicating the project packages files. We seperate those from other files so you could use CDN assets in your production configuration.</p>
+          <p>A list of glob patterns indicating the project packages files. We separate those from other files so you could use CDN assets in your production configuration.</p>
           <dl>
             <dt>config.assets.lib.css</dt>
             <dd>
-              A list of glob patterns idicating the project packages CSS files.
+              A list of glob patterns indicating the project packages CSS files.
             </dd>
             <dt>config.assets.lib.js</dt>
             <dd>
-              A list of glob patterns idicating the project packages JavaScript files.
+              A list of glob patterns indicating the project packages JavaScript files.
             </dd>
           </dl>
         </dd>
@@ -115,7 +115,7 @@ <h2>Social Configuration Properties</h2>
         MEAN.JS currently supports five social platforms: Facebook, Twitter, Google, Linkedin, and Github. You can also add other platforms using a passport-provider package and duplicating the samples logic.
       </p>
       <p>
-        To configure your social application oauth keys there's a property object for each platform:
+        To configure your social application OAuth keys there's a property object for each platform:
       </p>
       <dl>
         <dt>config.app.{OAuth Provider}.clientID</dt>

_includes/docs/0.3.x/folderstructure.html

@@ -80,7 +80,7 @@ <h3>env</h3>
         <li>
           <h3>strategies</h3>
           <a href="#autoload" class="label label-danger">Autoloaded</a> 
-          <br>The <b>strategies</b> folder contains the startegies configuration files loaded by the <b>passport.js</b> file.
+          <br>The <b>strategies</b> folder contains the strategies configuration files loaded by the <b>passport.js</b> file.
           <p class="alert alert-info">
             <b>When to use:</b>
             Whenever you want to add, change, or remove a <a target="_blank" href="http://passportjs.org/guide/providers/">Passport Strategy</a>.
@@ -100,7 +100,7 @@ <h3>express.js</h3>
         </li>
         <li>
           <h3>init.js</h3>
-          The initialization file that set up a few project related configuraiton.
+          The initialization file that set up a few project related configuration.
         </li>
         <li>
           <h3>passport.js</h3>
@@ -141,7 +141,7 @@ <h3>config.js</h3>
             <dd>
               This method is used to register a module as a new module and add it to the main module dependencies.
               <p class="alert alert-danger">
-                Although you don't have to, it is highly recommended that you use <b>registerModule</b> method to reigster your module as a dependency for the main application module. To understand this better please visit the <a href="#angularjs-modules">AngularJS Modules</a> section.
+                Although you don't have to, it is highly recommended that you use <b>registerModule</b> method to register your module as a dependency for the main application module. To understand this better please visit the <a href="#angularjs-modules">AngularJS Modules</a> section.
               </p>
             </dd>
           </dl>

changelog.html

@@ -68,7 +68,7 @@ <h2>Major Release Changes</h2>
   <li>Added CSS Linting and created grunt lint task.</li>
   <li>Added <b>CSSMin</b> and <b>Uglify</b> tasks wrapped in a grunt build task for production support.</li>
   <li>Created environmental assets management.</li>
-  <li>Introduced new <b>Menus</b> service that offers better menus managment.</li>
+  <li>Introduced new <b>Menus</b> service that offers better menus management.</li>
   <li>Added roles to the User model.</li>
   <li>Updated the Yo Generator to support new structure and features.</li>
 </ul>
@@ -150,7 +150,7 @@ <h2>Design Changes</h2>
     <b>Bootstrap 3.0.3</b> support.
   </li>
   <li>
-    Views redesigned to support reponsive behaviour.
+    Views redesigned to support responsive behavior.
   </li>
 </ul>
 <h2>AngularJS Module Changes</h2>

generator.html

@@ -119,7 +119,7 @@ <h1>CRUD Module Sub-Generator</h1>
       <p>The CRUD module sub-generator will help you create a new CRUD module, similar to the article sample provided with the project. To create a new CRUD module you will need to use <i>yo</i> again:</p><br>
       <pre>$ yo meanjs:crud-module &lt;module-name&gt;</pre><br>
       <p>This will create both AngularJS and Express files supporting full CRUD functionality, and add the Karma and Mocha tests.</p>
-      <p class="alert alert-info"><b>Note:</b> Don’t forget to use your module name as an argument when calling the CRUD module sub-generator.</p>
+      <p class="alert alert-info"><b>Note:</b> don't forget to use your module name as an argument when calling the CRUD module sub-generator.</p>
     </section>
     <div class="inner-link-anchor" id="angular-module"></div>
     <section class="page-header">
@@ -135,7 +135,7 @@ <h1>AngularJS Module Sub-Generator</h1>
       <h1>AngularJS Route Sub-Generator</h1>
     </section>
     <section>
-      <p>To construct your module you will often need to create a new route. The AngularJS route sub-generator will help you create a view, controller and a proper route in your module <b>routes.js</b> file. If it can’t find the module routes file the sub-generator will create one for you. Creating a new AngularJS route will involve executing this command:</p> <br>
+      <p>To construct your module you will often need to create a new route. The AngularJS route sub-generator will help you create a view, controller and a proper route in your module <b>routes.js</b> file. If it can't find the module routes file the sub-generator will create one for you. Creating a new AngularJS route will involve executing this command:</p> <br>
       <pre>$ yo meanjs:angular-route &lt;route-name&gt;</pre><br>
       <p>The sub-generator will ask for more information about your controller, view and routing URL, and will generate the appropriate files for you.</p>
     </section>
@@ -147,16 +147,16 @@ <h1>AngularJS Controller Sub-Generator</h1>
       <p>The AngularJS Controller sub-generator will create a new AngularJS controller in the specified module's <b>controllers</b> folder. To create a new AngularJS controller run <i>yo</i> again by using this command:</p><br>
       <pre>$ yo meanjs:angular-controller &lt;controller-name&gt;</pre><br>
       <p>The sub-generator will ask you for the module name under which you would like to create your new controller, and will create a new AngularJS controller file in that module <b>controllers</b> folder and a controller test in the module <b>tests</b> folder.</p>
-      <p class="alert alert-info"><b>Don’t forget!</b> This time you pass the controller name as an argument. </p>
+      <p class="alert alert-info"><b>Don't forget!</b> This time you pass the controller name as an argument. </p>
     </section>
     <div class="inner-link-anchor" id="angular-view"></div>
     <section class="page-header">
       <h1>AngularJS View Sub-Generator</h1>
     </section>
     <section>
-      <p>Once you have your controller file ready, you may want to add a view that makes use of this controller. The AngularJS view sub-generator will create a new AngularJS view in thr specified module's <b>views</b> folder, and will allow you to add a route definition for it. To create a new AngularJS view you will need to execute this command:</p><br>
+      <p>Once you have your controller file ready, you may want to add a view that makes use of this controller. The AngularJS view sub-generator will create a new AngularJS view in the specified module's <b>views</b> folder, and will allow you to add a route definition for it. To create a new AngularJS view you will need to execute this command:</p><br>
       <pre>$ yo meanjs:angular-view &lt;view-name&gt;</pre><br>
-      <p>The sub-generator will ask you for the module name under which you would like to create your new view, and some additional routing information. It will then create a new view file in that module's <b>views</b> folder and add a routing state to the module <b>routes.js</b> file. If it can’t find the module routes file it will create one for you.</p>
+      <p>The sub-generator will ask you for the module name under which you would like to create your new view, and some additional routing information. It will then create a new view file in that module's <b>views</b> folder and add a routing state to the module <b>routes.js</b> file. If it can't find the module routes file it will create one for you.</p>
     </section>
     <div class="inner-link-anchor" id="angular-service"></div>
     <section class="page-header">
@@ -199,10 +199,10 @@ <h1>AngularJS Config Sub-Generator</h1>
       <h1>AngularJS Test Sub-Generator</h1>
     </section>
     <section>
-      <p>Your MEAN application comes pre-bundled with the Karma test runner and Jasmine testing framework. To test your AngularJS controllers you’ll need to create a test file, which Karma will later use to run the tests. For this purpose we provided you with the AngularJS test sub-generator. Creating a new AngularJS test is effortless, just execute this command:</p><br>
+      <p>Your MEAN application comes pre-bundled with the Karma test runner and Jasmine testing framework. To test your AngularJS controllers you'll need to create a test file, which Karma will later use to run the tests. For this purpose we provided you with the AngularJS test sub-generator. Creating a new AngularJS test is effortless, just execute this command:</p><br>
       <pre>$ yo meanjs:angular-test &lt;controller-name&gt;</pre><br>
-      <p>This will create a test file for your controller, and if the sub-generator doesn’t find the specified controller file, it will create one for you.</p>
-      <p class="alert alert-info"><b>Don’t forget!</b> You're suppose to pass the controller name as an argument. </p>
+      <p>This will create a test file for your controller, and if the sub-generator doesn't find the specified controller file, it will create one for you.</p>
+      <p class="alert alert-info"><b>Don't forget!</b> You're suppose to pass the controller name as an argument. </p>
     </section>
     <div class="inner-link-anchor" id="express-model"></div>
     <section class="page-header">
@@ -237,10 +237,10 @@ <h1>Express Routes Sub-Generator</h1>
       <h1>Express Test Sub-Generator</h1>
     </section>
     <section>
-      <p>Your MEAN application comes pre-bundled with the Mocha testing framework. To test your Express models you’ll need to create a new test file, which Mocha will use while running tests. For this purpose we provided you with the Express test sub-generator. Creating a new Express test is easy, just execute this command:</p><br>
+      <p>Your MEAN application comes pre-bundled with the Mocha testing framework. To test your Express models you'll need to create a new test file, which Mocha will use while running tests. For this purpose we provided you with the Express test sub-generator. Creating a new Express test is easy, just execute this command:</p><br>
       <pre>$ yo meanjs:express-test &lt;model-name&gt;</pre><br>
-      <p>This will create a test file for your Express model, and if the sub-generator doesn’t find the specified model, it will create one for you.</p>
-      <p class="alert alert-info"><b>Don’t forget!</b> You're suppose to pass the model name as an argument. </p>
+      <p>This will create a test file for your Express model, and if the sub-generator doesn't find the specified model, it will create one for you.</p>
+      <p class="alert alert-info"><b>Don't forget!</b> You're suppose to pass the model name as an argument. </p>
     </section>
   </section>
 </section>