Add section lookup order change for v0.20

content/about-hugo/_index.md

@@ -1,7 +1,7 @@
 ---
 title: About Hugo
 linktitle: Overview
-description: Hugo's features, roadmap, and license, as well as the motivation behind creating Hugo.
+description: Hugo's features, roadmap, license, and motivation.
 date: 2017-02-01
 publishdate: 2017-02-01
 lastmod: 2017-02-01

content/about-hugo/benefits.md

@@ -12,23 +12,23 @@ aliases: []
 toc: false
 ---
 
-Website generators render content into HTML files. Most are "dynamic site generators." That means the HTTP server (i.e., the program that communicates with your end user's browser) runs the generator to create a new HTML file every time an end user requests a page.
+The purpose of website generators is to render content into HTML files. Most are "dynamic site generators." That means the HTTP server---i.e., the program that files to the browser to be viewed---runs the generator to create a new HTML file every time an end user requests a page.
 
 Creating the page dynamically requires the HTTP server to have enough memory and CPU to effectively run the generator nonstop. If not, your end user will wait in a queue for the page to be generated.
 
-To prevent unnecessary delays in delivering pages to end users, dynamic site generators were programmed to cache their HTML files. A cached page is a copy that is temporarily stored on the computer. Sending a cached copy is faster than generating a new page at the time of request because the majority of the work is already done.
+Over time, dynamic site generators were programmed to cache their HTML files to prevent unnecessary delays in delivering pages to end users. A cached page is a static version of a web page that is temporarily stored on a server for. Sending a cached copy of a web page is faster than generating a new page at the time of request because the majority of the work is already done.
 
-Hugo and other static site generators take caching a step further. All HTML files are rendered on your computer. You can review the files before you copy them to the computer hosting the HTTP server. Since the HTML files aren't generated dynamically, we say that Hugo is a "static site generator."
+Hugo is in a family of generators that take caching a step further. All HTML files are rendered on your computer. You can review the files locally before copying them to the computer hosting the HTTP server. Since the HTML files aren't generated dynamically, we say that Hugo is a *static site generator*.
 
-Not running a website generator on your HTTP server has many benefits. The most noticeable is performance---HTTP servers are very good at sending files. So good that you can effectively serve the same number of pages with a fraction of the memory and CPU needed for a dynamic site.
+Not running a website generator on your HTTP server has many benefits. The most noticeable is performance. HTTP servers are *very* good at sending files---so good, in fact, that you can effectively serve the same number of pages with a fraction of the memory and CPU needed for a dynamic site.
 
-## More Information on the Benefits of Static Site Generators
+## More on Static Site Generators
 
 * ["An Introduction to Static Site Generators", David Walsh][]
+* ["Hugo vs. Wordpress page load speed comparison: Hugo leaves WordPress in its dust", GettingThingsTech][hugovwordpress]
 * ["Static Site Generators", O-Reilly][]
 * [StaticGen: Top Open-Source Static Site Generators (GitHub Stars)][]
 * ["Top 10 Static Website Generators", Netlify blog][]
-* ["Hugo vs. Wordpress page load speed comparison: Hugo leaves WordPress in its dust", GettingThingsTech][hugovwordpress]
 * ["The Resurgence of Static", dotCMS][dotcms]
 
 

content/about-hugo/features.md

@@ -15,10 +15,10 @@ notesforauthors:
 ## General
 
 * [Extremely fast][] build times (< .7 ms per page)
-* Completely cross platform, with easy installation on [Mac OSX][], [Linux][], [Windows][], and more
+* Completely cross platform, with [easy installation][install] on Mac OSX, Linux, Windows, and more
 * Renders changes on the fly with [LiveReload][] as you develop
 * [Powerful theming][]
-* [Host your site anywhere][]
+* [Host your site anywhere][hostanywhere]
 
 ## Organization
 
@@ -66,11 +66,10 @@ See what's coming next in the [Hugo roadmap][].
 [Golang]: http://golang.org/pkg/html/template/
 [Google Analytics]: https://google-analytics.com/
 [homepage]: /templates/homepage/
-[Host your site anywhere]: /hosting-and-deployment/
+[hostanywhere]: /hosting-and-deployment/
 [Hugo roadmap]: /about-hugo/roadmap
-[Linux]: /getting-started/install-on-mac/
+[install]: /getting-started/installing/
 [LiveReload]: /getting-started/using-hugo/
-[Mac OSX]: /getting-started/install-of-pc/
 [organization for your projects]: /getting-started/directory-structure/
 [pagevars]: /variables/page-variables/
 [Permalink]: /content-management/urls/#permalinks
@@ -84,5 +83,4 @@ See what's coming next in the [Hugo roadmap][].
 [Syntax highlighting]: /developer-tools/syntax-highlighting/
 [table of contents]: /content-management/toc/
 [taxonomies]: /content-management/taxonomies/
-[URLs]: /content-management/urls/
-[Windows]: /getting-started/install-on-linux/
+[URLs]: /content-management/urls/

content/about-hugo/license.md

@@ -1,7 +1,7 @@
 ---
 title: Apache License
 linktitle: License
-description: Hugo v0.15 and later are released under the Apache 2.0 license. Earlier versions of Hugo were released under the Simple Public License.
+description: Hugo v0.15 and later are released under the Apache 2.0 license.
 date: 2016-02-01
 publishdate: 2016-02-01
 lastmod: 2016-02-01

content/templates/section-templates.md

@@ -25,9 +25,11 @@ To effectively leverage section page templates, you should first understand the
 The [lookup order][lookup] for section pages is as follows:
 
 1. `/layouts/section/<SECTION>.html`
+2. `/layouts/<SECTION>/list.html`
 2. `/layouts/_default/section.html`
 3. `/layouts/_default/list.html`
 4. `/themes/<THEME>/layouts/section/<SECTION>.html`
+5. `/themes/<THEME>/layouts/<SECTION>/list.html`
 5. `/themes/<THEME>/layouts/_default/section.html`
 6. `/themes/<THEME>/layouts/_default/list.html`