minor documentation cleanup.

- changed it's -> its where appropriate.
- added post/ parent directory above happy/ to the organization examples

Signed-off-by: Noah Campbell <noahcampbell@gmail.com>

docs/content/content/front-matter.md

@@ -4,7 +4,7 @@ date = "2013-07-01"
 aliases = ["/doc/front-matter/"]
 +++
 
-The front matter is one of the features that gives Hugo it's strength. It enables
+The front matter is one of the features that gives Hugo its strength. It enables
 you to include the meta data of the content right with it. Hugo supports a few
 different formats each with their own identifying tokens.
 

docs/content/content/organization.md

@@ -19,7 +19,7 @@ content nested at any level. The top level is special in Hugo and is used as the
         ├── post
         |   ├── firstpost.md       // <- http://site.com/post/firstpost/
         |   ├── happy
-        |   |   └── happiness.md   // <- http://site.com/happy/happiness/
+        |   |   └── happiness.md   // <- http://site.com/post/happy/happiness/
         |   └── secondpost.md      // <- http://site.com/post/secondpost/
         └── quote
             ├── first.md           // <- http://site.com/quote/first/
@@ -32,7 +32,7 @@ content nested at any level. The top level is special in Hugo and is used as the
         ├── post
         |   ├── firstpost.md       // <- http://site.com/post/firstpost.html
         |   ├── happy
-        |   |   └── happiness.md   // <- http://site.com/happy/happiness.html
+        |   |   └── happiness.md   // <- http://site.com/post/happy/happiness.html
         |   └── secondpost.md      // <- http://site.com/post/secondpost.html
         └── quote
             ├── first.md           // <- http://site.com/quote/first.html

docs/content/content/types.md

@@ -3,7 +3,7 @@ title: "Content Types"
 date: "2013-07-01"
 ---
 
-Hugo has full support for multiple content types each with it's own set
+Hugo has full support for multiple content types each with its own set
 of meta data and template. A good example of when multiple types are
 needed is to look a tumblr. A piece of content could be a photo, quote
 or post, each with different meta data and rendered differently.

docs/content/extras/shortcodes.md

@@ -4,7 +4,7 @@ date: "2013-07-01"
 aliases: ["/doc/shortcodes/"]
 ---
 
-Because Hugo uses markdown for it's content format, it was clear that there's a lot of things that 
+Because Hugo uses markdown for its content format, it was clear that there's a lot of things that 
 markdown doesn't support well. This is good, the simple nature of markdown is exactly why we chose it.
 
 However we cannot accept being constrained by our simple format. Also unacceptable is writing raw

docs/content/layout/go-templates.md

@@ -3,7 +3,7 @@ title: "Go Templates"
 date: "2013-07-01"
 ---
 
-Hugo uses the excellent golang html/template library for it's template engine.
+Hugo uses the excellent golang html/template library for its template engine.
 It is an extremely lightweight engine that provides a very small amount of
 logic. In our experience that it is just the right amount of logic to be able to
 create a good static website.

docs/content/layout/index.md

@@ -7,7 +7,7 @@ An index template is any template that will be used to render multiple pieces of
 content (with the exception of the [homepage](/layout/homepage) which has a
 dedicated template).
 
-We are using the term index in it's truest sense, a sequential arrangement of
+We are using the term index in its truest sense, a sequential arrangement of
 material, especially in alphabetical or numerical order. In the case of Hugo
 each index will render the content in newest first order based on the date
 provided in the [front matter](/content/front-matter).

docs/content/layout/templates.md

@@ -4,7 +4,7 @@ date: "2013-07-01"
 aliases: ["/doc/templates/"]
 ---
 
-Hugo uses the excellent golang html/template library for it's template engine.
+Hugo uses the excellent golang html/template library for its template engine.
 It is an extremely lightweight engine that provides a very small amount of
 logic. In our experience that it is just the right amount of logic to be able
 to create a good static website