Use lowercase when referring to front matter (#2132)

content/en/content-management/build-options.md

@@ -13,7 +13,7 @@ weight: 70
 aliases: [/content/build-options/]
 ---
 
-They are stored in a reserved Front Matter object named `_build` with the following defaults:
+They are stored in a reserved front matter object named `_build` with the following defaults:
 
 {{< code-toggle >}}
 _build:
@@ -67,7 +67,7 @@ Any page, regardless of their build options, will always be available using the
 
 #### Not publishing a page
 
-Project needs a "Who We Are" content file for Front Matter and body to be used by the homepage but nowhere else.
+Project needs a "Who We Are" content file for front matter and body to be used by the homepage but nowhere else.
 
 {{< code-toggle file="content/who-we-are.md" fm=true copy=false >}}
 title: Who we are

content/en/content-management/front-matter.md

@@ -151,7 +151,7 @@ show_comments: false
 
 ## Front Matter Cascade
 
-Any node or section can pass down to descendants a set of Front Matter values as long as defined underneath the reserved `cascade` Front Matter key.
+Any node or section can pass down to descendants a set of front matter values as long as defined underneath the reserved `cascade` front matter key.
 
 ### Target Specific Pages
 

content/en/content-management/page-bundles.md

@@ -125,7 +125,7 @@ Explanation of the above example:
 
 ---
 
-A leaf bundle can be made headless by adding below in the Front Matter
+A leaf bundle can be made headless by adding below in the front matter
 (in the `index.md`):
 
 {{< code-toggle file="content/headless/index.md" fm=true copy=false >}}

content/en/content-management/related.md

@@ -12,7 +12,7 @@ weight: 110
 aliases: [/content/related/,/related/]
 ---
 
-Hugo uses a set of factors to identify a page's related content based on Front Matter parameters. This can be tuned to the desired set of indices and parameters or left to Hugo's default [Related Content configuration](#configure-related-content).
+Hugo uses a set of factors to identify a page's related content based on front matter parameters. This can be tuned to the desired set of indices and parameters or left to Hugo's default [Related Content configuration](#configure-related-content).
 
 ## List Related Content
 

content/en/tools/migrations.md

@@ -47,7 +47,7 @@ Alternatively, you can use the new [Jekyll import command](/commands/hugo_import
 
 ## Medium
 
-- [medium2md](https://github.com/gautamdhameja/medium-2-md) - A simple Medium to Hugo exporter able to import stories in one command, including Front Matter.
+- [medium2md](https://github.com/gautamdhameja/medium-2-md) - A simple Medium to Hugo exporter able to import stories in one command, including front matter.
 - [medium-to-hugo](https://github.com/bgadrian/medium-to-hugo) - CLI tool written in Go to export medium posts into a Hugo compatible Markdown format. Tags and images are included. All images will be downloaded locally and linked appropriately.
 
 ## Tumblr

content/en/troubleshooting/faq.md

@@ -28,7 +28,7 @@ Yes you can! See [Configure with Environment Variables](/getting-started/configu
 
 ## How do I schedule posts?
 
-1. Set `publishDate` in the page [Front Matter](/content-management/front-matter/) to a datetime in the future. If you want the creation and publication datetime to be the same, it's also sufficient to only set `date`[^date-hierarchy].
+1. Set `publishDate` in the page [front matter](/content-management/front-matter/) to a datetime in the future. If you want the creation and publication datetime to be the same, it's also sufficient to only set `date`[^date-hierarchy].
 2. Build and publish at intervals.
 
 How to automate the "publish at intervals" part depends on your situation: