fix(docs): typos

_app/_posts/note/2014-01-01-github-pages-setup.md

@@ -18,7 +18,7 @@ Unfortunately this project doesn't work with GitHub Pages or GitHub Pages for pr
 I know this can be tricky and more verbose than uploading your Jekyll site directly to your repository. However GitHub Pages support static HTML pages, a workaround solution for using Almace Scaffolding on GitHub Pages is treating your Jekyll site as static pages:
 
 - Build your site locally (`grunt build`).
-- Upload Jekyll generateed static files to your `username.github.io` repository.
+- Upload Jekyll generated static files to your `username.github.io` repository.
 
 If you'd like to keep all things under Git control, you can try the following file structure:
 

_app/_posts/note/2014-02-01-external-link-post.md

@@ -6,7 +6,7 @@ link: http://sparanoid.com/
 tags: curtana
 ---
 
-This is an example of Tumblr-like external link post. You can simply add the folloing setting to your post [front-matter field](http://jekyllrb.com/docs/frontmatter/):
+This is an example of Tumblr-like external link post. You can simply add the following setting to your post [front-matter field](http://jekyllrb.com/docs/frontmatter/):
 
 ```
 link: http://sparanoid.com/

_app/_posts/note/2014-02-01-svg-post-title.md

@@ -13,15 +13,15 @@ scheme-code: "#ffe000"
 scheme-bg: "#ff9610"
 ---
 
-This is an example of custom post title using SVG image. You can simply add the folloing setting to your post [front-matter field](http://jekyllrb.com/docs/frontmatter/):
+This is an example of custom post title using SVG image. You can simply add the following setting to your post [front-matter field](http://jekyllrb.com/docs/frontmatter/):
 
 ```
 svg-headline: svg/kai.svg
 svg-headline-width: 400
 svg-headline-height: 86
 ```
 
-Image defined for `svg-headline` should be stored at `_app/assets/svg/kai.svg`, you can simply keep these title images under Git control, they will be smooshed into the HTML pages using Grunt.js in production builds. The `svg-headline-width` and `svg-headline-height` are optional if you have correct dimensions for your images.
+Image defined for `svg-headline` should be stored at `_app/assets/svg/kai.svg`, you can simply keep these title images under Git control, they will be inlined into the HTML pages using Grunt.js in production builds. The `svg-headline-width` and `svg-headline-height` are optional if you have correct dimensions for your images.
 
 There's also an option for common raster images, but please note that these files should be stored at where you define `site.file`.
 

_app/_posts/note/2014-05-01-custom-color-scheme.md

@@ -10,7 +10,7 @@ scheme-code: "#ad00ff"
 scheme-bg: "#00ebff"
 ---
 
-This is an example how to change your post color scheme for specific posts. You can simply add the folloing variables to your post [front-matter field](http://jekyllrb.com/docs/frontmatter/):
+This is an example how to change your post color scheme for specific posts. You can simply add the following variables to your post [front-matter field](http://jekyllrb.com/docs/frontmatter/):
 
 ```
 scheme-text: "#0029ff"

_app/_posts/note/2014-06-01-custom-html-markups.md

@@ -78,7 +78,7 @@ A simple library by [Tim Holman](https://github.com/tholman) to view large image
 
 ### Usage
 
-Add the folloing setting to your post [front-matter field](http://jekyllrb.com/docs/frontmatter/):
+Add the following setting to your post [front-matter field](http://jekyllrb.com/docs/frontmatter/):
 
 ```
 plugin: intense

_app/_posts/note/2014-06-09-creating-themes.md

@@ -232,7 +232,7 @@ languages:
   - en-us
 ```
 
-Please note that only the first item defined in `languages` array will be used in final `lang` ouput, the additional languages will be available in JSON feed output:
+Please note that only the first item defined in `languages` array will be used in final `lang` output, the additional languages will be available in JSON feed output:
 
 ```json
 {
@@ -246,13 +246,13 @@ Please note that only the first item defined in `languages` array will be used i
 
 For better performance, Almace Scaffolding will find all the CSS, script links and images in compiled HTML, and outputs a version with all the CSS, scripts and images (Base64) written inline. Sounds cool? but it needs theme support. Here's how:
 
-You can simply add the query string `?assets-inline` at the end of the file you'd like to be smooshed in production site:
+You can simply add the query string `?assets-inline` at the end of the file you'd like to be inlined in production site:
 
 ```html
-<!-- This CSS will be smooshed into HTML -->
+<!-- This CSS will be inlined into HTML -->
 <link rel="stylesheet" href="{% raw %}{{ '/css/app.css?assets-inline' | prepend: amsf_theme_assets }}{% endraw %}">
 
-<!-- This script will be smooshed into HTML -->
+<!-- This script will be inlined into HTML -->
 <script src="{% raw %}{{ '/js/app.js?assets-inline' | prepend: amsf_theme_assets }}{% endraw %}"></script>
 ```
 

_app/_posts/note/2014-06-11-configuration.md

@@ -16,6 +16,6 @@ tags: getting-started
 
 ## Tips
 
-- Not familer with [Markdown](http://daringfireball.net/projects/markdown/)? Try [Markdown Cheatsheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet).
+- Not familiar with [Markdown](http://daringfireball.net/projects/markdown/)? Try [Markdown Cheatsheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet).
 - You can use Jekyll's [built-in syntax highlighting](http://jekyllrb.com/docs/templates/#code-snippet-highlighting), I've included a default theme for this project.
-- [Tables](https://help.github.com/articles/github-flavored-markdown#tables) and [footnotes](https://github.com/vmg/redcarpet#and-its-like-really-simple-to-use) are also avaiables to use.
+- [Tables](https://help.github.com/articles/github-flavored-markdown#tables) and [footnotes](https://github.com/vmg/redcarpet#and-its-like-really-simple-to-use) are also available to use.

_app/_posts/note/2014-06-12-getting-started.md

@@ -35,7 +35,7 @@ You can simply copy all posts from your old Jekyll setup into `_app/_posts`, you
 
 ## Upgrading
 
-Upgrading templates is hard, it will be easy if you are're a casual blogger and keep every core and template file untouched. You can use the following command to update Almace Scaffolding core files:
+It will be easy if you're a casual blogger and keep every core and template file untouched. You can use the following command to update Almace Scaffolding core files:
 
 ```sh
 $ grunt amsf-update

_app/_posts/note/2014-06-13-welcome.md

@@ -17,7 +17,7 @@ Go to the [GitHub](https://github.com/sparanoid/almace-scaffolding) page for dow
 
 - Theme switching, you can switch themes with just one command
 - A basic, fully configured Jekyll setup with well-defined [Atom feed](https://github.com/sparanoid/almace-scaffolding/blob/master/_app/feed-atom.xml) and [sitemap](https://github.com/sparanoid/almace-scaffolding/blob/master/_app/sitemap.xml)
-- **Almace Scaffolding** ships a sleek responsive theme [Curtana](http://github.com/amsf/amsf-curtana), a variant of [sparanoid.com](http://sparanoid.com/), looking great on any mordern browsers
+- **Almace Scaffolding** ships a sleek responsive theme [Curtana](http://github.com/amsf/amsf-curtana), a variant of [sparanoid.com](http://sparanoid.com/), looking great on any modern browsers
 - Every minified page generates only one HTTP request [^1]
 - [Tons of configurable settings](https://github.com/sparanoid/almace-scaffolding/blob/master/_config.init.yml) for your posts and site customization
 - Built with Grunt.js for easy development