[Docs] Copyediting

* Add meta author, description and generator tags
 * Add Hugo version beside the logo and in the footer
 * Suggest the user to run `go get -u -v` to update dependencies
 * Requires Go 1.3+ rather than Go 1.1+
 * Improve rendering/formatting in some places
 * Add trailing slash to URLs where appropriate
 * GitHub redirects all http requests to https, update accordingly

docs/content/themes/creation.md

@@ -21,7 +21,7 @@ to Go, the [Go template primer](/layout/go-templates/) will help you get started
 ## Theme Components
 
 A theme consists of templates and static assets such as javascript and css
-files. Themes can also optionally provide [archetypes](/content/archetypes)
+files. Themes can also optionally provide [archetypes](/content/archetypes/)
 which are archetypal content types used by the `hugo new` command.
 
 ### Layouts
@@ -43,7 +43,7 @@ The default list file layout is located at `layouts/_default/list.html`.
 
 ### Partial Templates
 
-Theme creators should liberally use [partial templates](/templates/partials)
+Theme creators should liberally use [partial templates](/templates/partials/)
 throughout their theme files. Not only is a good DRY practice to include shared
 code, but partials are a special template type that enables the themes end user
 to be able to overwrite just a small piece of a file or inject code into the
@@ -66,7 +66,7 @@ The actual structure is entirely up to you, the theme creator, on how you would
 
 ### Archetypes
 
-If your theme makes use of specific keys in the front matter it is a good idea
+If your theme makes use of specific keys in the front matter, it is a good idea
 to provide an archetype for each content type you have. Archetypes follow the
-[guidelines provided](/content/archetypes).
+[guidelines provided](/content/archetypes/).
 

docs/content/themes/customizing.md

@@ -26,12 +26,12 @@ in the same relative path `/static/js/jquery.min.js`.
 Anytime Hugo looks for a matching template, it will first check the
 working directory before looking in the theme directory. If you would
 like to modify a template, simply create that template in your local
-`layouts` directory. In the [template documentation](/templates/overview)
+`layouts` directory. In the [template documentation](/templates/overview/)
 each different template type explains the rules it uses to determine
 which template to use.
 
 This is especially helpful when the theme creator used [partial
-templates](/templates/partials). These partial templates are perfect for easy
+templates](/templates/partials/). These partial templates are perfect for easy
 injection into the theme with minimal maintenance to ensure future
 compatibility.
 

docs/content/themes/installing.md

@@ -10,7 +10,7 @@ weight: 20
 ---
 
 Hugo themes are located in a centralized GitHub repository. The [Hugo Themes
-Repo](http://github.com/spf13/hugoThemes) itself is really a meta
+Repo](https://github.com/spf13/hugoThemes) itself is really a meta
 repository which contains pointers to set of contributed themes.
 
 ## Installing all themes

docs/content/themes/overview.md

@@ -18,7 +18,7 @@ site.
 Hugo themes have been designed to be the perfect balance between
 simplicity and functionality. Hugo themes are powered by the excellent
 Go template library. If you are new to Go templates, see our [primer on
-Go templates](/templates/go-templates).
+Go templates](/templates/go-templates/).
 
 Hugo themes support all modern features you come to expect. They are
 structured in such a way to eliminate code duplication. Themes are also

docs/content/themes/usage.md

@@ -19,4 +19,4 @@ To use a theme for a site:
 The *ThemeName* must match the name of the directory inside `/themes`.
 
 Hugo will then apply the theme first, then apply anything that is in the local
-directory. To learn more, go to [customizing themes](/themes/customizing).
+directory. To learn more, go to [customizing themes](/themes/customizing/).