Be more specific about .Params content

I'm not sure whether this is *always* the case, but it's definitely have been my experience so far. :)
This commit is contained in:
Jakub Turski authored and spf13 committed 2014-08-28 13:04:00 -04:00
1 parent 7de320920c
commit d3646aaac0
1 file changed
+1 -1
+1 -1
View File
@@ -68,7 +68,7 @@ Supported formats: <br>
There are a few predefined variables that Hugo is aware of and utilizes. The user can also create There are a few predefined variables that Hugo is aware of and utilizes. The user can also create
any variable they want to. These will be placed into the `.Params` variable available to the templates. any variable they want to. These will be placed into the `.Params` variable available to the templates.
**Field names are case insensitive.** Field names are always normalized to lowercase (eg. `camelCase: true` is available as `.Params.camelcase`).
### Required ### Required