Clarify partials folder subfolders

A couple of edits to clarify that the layout/partials folder can contain arbitrarily-named subfolders, since I found the examples using ``{{ partial "post/tag/list" . }}`` confusing. Some folders are named specifically to work a certain way with hugo, but although the examples use key functional section and taxonomy names like post and tag, it does not matter what they are called. Hopefully this will help other newbs.

diff --git a/docs/content/templates/partials.md b/docs/content/templates/partials.md
index 911f6c9c6e830b10a5bd72244591061491a82bee..be81058acc49b5c0587e0851dc869e4caf3ae656 100644 (file)
--- a/docs/content/templates/partials.md
+++ b/docs/content/templates/partials.md
@@ -13,7 +13,7 @@ weight: 80
 
 In practice, it's very convenient to split out common template portions into a
 partial template that can be included anywhere. As you create the rest of your
-templates, you will include templates from the /layout/partials directory.
+templates, you will include templates from the /layout/partials directory, or from arbitrary subdirectories like /layout/partials/post/tag.
 
 Partials are especially important for themes as it gives users an opportunity
 to overwrite just a small part of your theme, while maintaining future compatibility.
@@ -99,5 +99,11 @@ This footer template is used for [spf13.com](http://spf13.com/):
     </body>
     </html>
 
-**For examples of referencing these templates, see [single content
+To reference a partial template stored in a subfolder, e.g. `/layout/partials/post/tag/list.html`, call it this way: 
+
+     {{ partial "post/tag/list" . }}
+
+Note that the subdirectories you create under /layout/partials can be named whatever you like. 
+
+**For more examples of referencing these templates, see [single content
 templates](/templates/content/), [list templates](/templates/list/) and [homepage templates](/templates/homepage/).**