--- a/docs/docs/01_tutorial/02_making-things-pretty.md	Mon Nov 14 02:55:02 2016 +0100
+++ b/docs/docs/01_tutorial/02_making-things-pretty.md	Mon Nov 14 02:54:40 2016 +0100
@@ -28,7 +28,7 @@
     templates/post.html
 
 All of those files have been copied into your website's directory -- and it will
-warn you if it was every going to overwrite some of your own files.
+warn you if it was ever going to overwrite some of your own files.
 
 There are a few files we'll be editing here:
 

--- a/docs/docs/03_content.md	Mon Nov 14 02:55:02 2016 +0100
+++ b/docs/docs/03_content.md	Mon Nov 14 02:54:40 2016 +0100
@@ -3,7 +3,7 @@
 ---
 
 This section of the documentation explains how to write, or otherwise create and
-us, content for PieCrust websites -- pages, layouts, assets, etc. If however you
+use, content for PieCrust websites -- pages, layouts, assets, etc. If however you
 want to *define* what *types* of content your website will have in the first
 place, you may want to read up on the [content model documentation][cm].
 

--- a/docs/docs/03_content/04_templating.md	Mon Nov 14 02:55:02 2016 +0100
+++ b/docs/docs/03_content/04_templating.md	Mon Nov 14 02:54:40 2016 +0100
@@ -5,7 +5,7 @@
 As explained in the documentation about [how PieCrust works][how], the page
 contents that you write go through a _templating_ phase, which is when a page
 can execute some logic, insert reusable bits of markup, or reference other
-pieces of content or metadata from elsewhere in you website.
+pieces of content or metadata from elsewhere in your website.
 
 PieCrust uses [Jinja][] for templating. There's too much data exposed to it to
 go over on this page, but check out the [templating data reference][dataref] for

--- a/docs/docs/03_content/05_content-segments.md	Mon Nov 14 02:55:02 2016 +0100
+++ b/docs/docs/03_content/05_content-segments.md	Mon Nov 14 02:54:40 2016 +0100
@@ -39,7 +39,7 @@
     ---sidebar---
     Sidebar goes here
 
-You can them use, the page's layout, both the `content` and `sidebar` segments
+You can then use, the page's layout, both the `content` and `sidebar` segments
 to put each piece of text in its appropriate place.
 
 You can also specify a [formatter][] for a given segment, by adding `:formatter`

--- a/docs/docs/05_asset-pipeline.md	Mon Nov 14 02:55:02 2016 +0100
+++ b/docs/docs/05_asset-pipeline.md	Mon Nov 14 02:54:40 2016 +0100
@@ -27,7 +27,7 @@
 * Process it, if it matches any of the active asset processors. The output of
   the processing phase will be put in the output directory.
 
-* Copy it as is, if not asset processor was found. Just like for processing, the
+* Copy it as is, if no asset processor was found. Just like for processing, the
   relative path of the asset is preserved in the output directory.
 
 
@@ -45,7 +45,7 @@
 processors match and the `copy` processor copies the result to the output(s)
 directory.
 
-So for instance, you if you have a LessCSS file, it will be processed like so:
+So for instance, if you have a LessCSS file, it will be processed like so:
 
     foo.less    ->    foo.css    ->    foo.min.css
 

--- a/docs/docs/06_themes.md	Mon Nov 14 02:55:02 2016 +0100
+++ b/docs/docs/06_themes.md	Mon Nov 14 02:54:40 2016 +0100
@@ -3,7 +3,7 @@
 ---
 
 Themes let you change your website's appearance easily by applying a new set of
-templates, layouts, and styles over you content. You're probably already
+templates, layouts, and styles over your content. You're probably already
 familiar with this concept if you're coming from some other CMS like WordPress.
 
 In PieCrust, themes work better if you don't have any templates -- otherwise,