The phrase "Instead of set field on all pages, you can set field on required pages only." seems to be grammatically incorrect.
I have changed it to: "Instead of setting a field on all pages, you can set that field on required pages only."
* Mentioning a range is equivelant to foreach
I’m new to Go and really struggled to find this. I added this sentence so it would be searchable for other people to find. At the moment, searching for a foreach doesn’t return range and IMHO it should.
* Fixed a spelling error for equivalent
The link "[wherefunction]" was not defined, so the square brackets where visible on the rendered page.
It seems that this link would have just gone back to the top of the page, so I removed it instead of fixing it.
### Changes
added a slash '/', so that link is referenced from root of the domain and not current page
### Previously
```
**Note** that this method is more powerful than the similar [markdownify](functions/markdownify/) function as it also supports [Render Hooks](/getting-started/configuration-markup/#markdown-render-hooks) and it has options to render other markup formats.
```
### Now
```
**Note** that this method is more powerful than the similar [markdownify](/functions/markdownify/) function as it also supports [Render Hooks](/getting-started/configuration-markup/#markdown-render-hooks) and it has options to render other markup formats.
```
This commit also
* revises the change detection for templates used by content files in server mode.
* Adds a Page.RenderString method
Fixes#6545Fixes#4663Closes#6043
This commit adds the fast and CommonMark compliant Goldmark as the new default markdown handler in Hugo.
If you want to continue using BlackFriday as the default for md/markdown extensions, you can use this configuration:
```toml
[markup]
defaultMarkdownHandler="blackfriday"
```
Fixes#5963Fixes#1778Fixes#6355
* Correct typo "RFC339" to "RFC1123Z"
Per discussion in PR #887, I added a link to the Go time package documentation that lists constants that can serve as further examples.
While Hugo does not care if the section is named "post" or "posts",
this commit normalizes the whole Hugo documentation to use "posts"
when used as an example for a section name to prevent user confusion.
Fixes https://github.com/gohugoio/hugoDocs/issues/720.
Also highlight the use of `site.Params.mainSections`.
