ref: aa9b9d596efae9b6cd534022bb24d408ae153563
parent: 8ce4bc7ab8ab5cf8347bcdcc2088877c92aab3cc
author: Kyle Mahan <[email protected]>
date: Sun Sep 29 15:37:29 EDT 2013
minor documentation cleanup. - changed it's -> its where appropriate. - added post/ parent directory above happy/ to the organization examples Signed-off-by: Noah Campbell <[email protected]>
--- a/docs/content/content/front-matter.md
+++ b/docs/content/content/front-matter.md
@@ -4,7 +4,7 @@
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.
--- a/docs/content/content/organization.md
+++ b/docs/content/content/organization.md
@@ -19,7 +19,7 @@
├── 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 @@
├── 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
--- a/docs/content/content/types.md
+++ b/docs/content/content/types.md
@@ -3,7 +3,7 @@
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.
--- a/docs/content/extras/shortcodes.md
+++ b/docs/content/extras/shortcodes.md
@@ -4,7 +4,7 @@
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
--- a/docs/content/layout/go-templates.md
+++ b/docs/content/layout/go-templates.md
@@ -3,7 +3,7 @@
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.
--- a/docs/content/layout/index.md
+++ b/docs/content/layout/index.md
@@ -7,7 +7,7 @@
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).
--- a/docs/content/layout/templates.md
+++ b/docs/content/layout/templates.md
@@ -4,7 +4,7 @@
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