Fix typos and add explanation on configuration.md

content/functions/adddate.md

@@ -51,7 +51,3 @@ Let's assume you want to grab Tweets from the last two years and present them in
 {{ end }}
 ```
 {{% /code %}}
-
-<!-- Look to example in docs site here: https://github.com/spf13/hugo/blob/master/docs/layouts/index.html--e.g., can be paired with now and where -->
-
-

content/functions/dict.md

@@ -41,7 +41,7 @@ Important {{.important}}
 {{.content}}
 ```
 
-`dict` also allows you to create a map on the fly to pass into your [partial templates][partials]
+`dict` also allows you to create a map on the fly to pass into your [partial templates][partials]:
 
 {{% code file="dict-create-map.html" %}}
 ```golang

content/getting-started/configuration.md

@@ -17,13 +17,17 @@ aliases: [/overview/source-directory/,/overview/configuration/]
 toc: true
 ---
 
-The [directory structure][dirs] of a Hugo website—or more precisely, the source organization of files containing the website's content and templates—provides most of the configuration information that Hugo needs in order to statically generate a finished website.
+The [directory structure][] of a Hugo website—or more precisely, the source organization of files containing the website's content and templates—provides most of the configuration information that Hugo needs in order to statically generate a finished website.
 
 Because of Hugo's preference for sane defaults, many websites may not need a configuration file. Hugo is designed to recognize certain typical usage patterns (and even expects them by default).
 
 ## Configuration Lookup Order
 
-Hugo searches for a configuration file in the root of your website's source directory as a default behavior. First, it looks for a `./config.toml` file. If that's not present, it will seek a `./config.yaml` file, followed by a `./config.json` file.
+Similar to the template [lookup order][], Hugo has a default set of rules for searching for a configuration file in the root of your website's source directory as a default behavior:
+
+1. `./config.toml`
+2. `./config.yaml`
+3. `./config.json`
 
 In your `config` file, you can direct Hugo as to how you want your website rendered, control your website's menus, and arbitrarily define site-wide parameters specific to your project.
 
@@ -383,8 +387,9 @@ blackfriday:
 * [JSON Spec][json]
 
 [`.Site.Params`]: /variables/site/
-[dirs]: /getting-started/directory-structure
+[directory structure]: /getting-started/directory-structure
 [json]: /documents/ecma-404-json-spec.pdf
+[lookup order]: /templates/lookup-order/
 [templates]: /templates/
 [toml]: https://github.com/toml-lang/toml
 [yaml]: http://yaml.org/spec/

content/getting-started/directory-structure.md

@@ -61,7 +61,7 @@ used by Hugo when generating your website. You can write these files in YAML, JS
 : stores all the static content for your future website: images, CSS, JavaScript, etc. When Hugo builds your site, all assets inside your static directory are copied over as-is. A good example of using the `static` folder is for [verifying site ownership on Google Search Console][searchconsole], where you want Hugo to copy over a complete HTML file without modifying its content.
 
 {{% note %}}
-Hugo does not currently ship with an asset pipeline ([#3207](https://github.com/spf13/hugo/issues/3207)). You can solicit support from the community in the [Hugo forums](https://discuss.gohugo.io) or check out a few of the [Hugo starter kits](/tools/starter-kits/) for examples of how Hugo developers are managing these assets.
+Hugo does not currently ship with an asset pipeline ([#3207](https://github.com/spf13/hugo/issues/3207)). You can solicit support from the community in the [Hugo forums](https://discuss.gohugo.io) or check out a few of the [Hugo starter kits](/tools/starter-kits/) for examples of how Hugo developers are managing static assets.
 {{% /note %}}
 
 

content/news/release-notes.md

@@ -15,7 +15,6 @@ weight: 30	#rem
 draft: false
 aliases: [/meta/release-notes/]
 toc: true
-notesforauthors:
 ---
 
 ## **0.19** February 27th 2017

content/readfiles/bfconfig.md

@@ -52,4 +52,4 @@
 : default: **`[]`** <br>
     Blackfriday flag: **`EXTENSION_*`** <br>
     Purpose: Enable one or more of Blackfriday's Markdown extensions (if they aren't Hugo defaults). <br>
-    Example: Include `autoHeaderIds` in the list of disable Blackfriday's `EXTENSION_AUTO_HEADER_IDS`.
+    Example: Include `autoHeaderIds` as `false` in the list to disable Blackfriday's `EXTENSION_AUTO_HEADER_IDS`.