Miscellaneous edits

Co-authored-by: Salim B <git@salim.space>

content/en/hugo-modules/use-modules.md

@@ -148,7 +148,7 @@ use .
 use ../gohugoioTheme
 ```
 
-Using the `use` directive, list all the modules you want to work on, pointing to its relative location. As in the example above, it's recommended to always include the main project (the ".") in the list.
+Using the `use` directive, list all the modules you want to work on, pointing to its relative location. As in the example above, it's recommended to always include the main project (the `.`) in the list.
 
 With that you can start the Hugo server with that workspace enabled:
 

content/en/methods/page/Ancestors.md

@@ -16,7 +16,7 @@ action:
   signatures: [PAGE.Ancestors]
 ---
 
-{{% include "methods/page/_common/definition-of-section.md" %}}
+{{% glossary-term section %}}
 
 With this content structure:
 

content/en/methods/page/CurrentSection.md

@@ -16,7 +16,7 @@ action:
   signatures: [PAGE.CurrentSection]
 ---
 
-{{% include "methods/page/_common/definition-of-section.md" %}}
+{{% glossary-term section %}}
 
 {{% note %}}
 The current section of a [section page](g), [taxonomy page](g), [term page](g), or the home page, is itself.

content/en/methods/page/FirstSection.md

@@ -16,7 +16,7 @@ action:
   signatures: [PAGE.FirstSection]
 ---
 
-{{% include "methods/page/_common/definition-of-section.md" %}}
+{{% glossary-term section %}}
 
 {{% note %}}
 When called on the home page, the `FirstSection` method returns the `Page` object of the home page itself.

content/en/methods/page/InSection.md

@@ -19,7 +19,7 @@ toc: true
 
 The `InSection` method on a `Page` object reports whether the given page is in the given section. Note that the method returns `true` when comparing a page to a sibling.
 
-{{% include "methods/page/_common/definition-of-section.md" %}}
+{{% glossary-term section %}}
 
 With this content structure:
 

content/en/methods/page/IsAncestor.md

@@ -17,7 +17,7 @@ action:
 toc: true
 ---
 
-{{% include "methods/page/_common/definition-of-section.md" %}}
+{{% glossary-term section %}}
 
 With this content structure:
 

content/en/methods/page/IsDescendant.md

@@ -16,7 +16,7 @@ action:
   signatures: [PAGE1.IsDescendant PAGE2]
 ---
 
-{{% include "methods/page/_common/definition-of-section.md" %}}
+{{% glossary-term section %}}
 
 With this content structure:
 

content/en/methods/page/Parent.md

@@ -16,7 +16,7 @@ action:
   signatures: [PAGE.Parent]
 ---
 
-{{% include "methods/page/_common/definition-of-section.md" %}}
+{{% glossary-term section %}}
 
 {{% note %}}
 The parent section of a regular page is the [current section].

content/en/methods/page/Sections.md

@@ -16,7 +16,7 @@ action:
   signatures: [PAGE.Sections]
 ---
 
-{{% include "methods/page/_common/definition-of-section.md" %}}
+{{% glossary-term section %}}
 
 With this content structure:
 

content/en/methods/page/_common/definition-of-section.md

@@ -1,5 +0,0 @@
----
-_comment: Do not remove front matter.
----
-
-A _section_ is a top-level content directory, or any content directory with an `_index.md` file.

content/en/quick-reference/glossary/context.md

@@ -3,4 +3,4 @@ title: context
 reference: /templates/introduction/#context
 ---
 
-Represented by a dot "." within a [_template action_](g), _context_ is the current location in a data structure. For example, while iterating over a [_collection_](g) of pages, the context within each iteration is the page's data structure. The context received by each template depends on template type and/or how it was called.
+Represented by a dot (`.`) within a [_template action_](g), _context_ is the current location in a data structure. For example, while iterating over a [_collection_](g) of pages, the context within each iteration is the page's data structure. The context received by each template depends on template type and/or how it was called.

content/en/quick-reference/glossary/headless-bundle.md

@@ -3,4 +3,4 @@ title: headless bundle
 reference: /content-management/build-options/
 ---
 
-A _headless bundle_ is an unpublished leaf or branch bundle whose content and resources you can include in other pages.
+A _headless bundle_ is an unpublished [_leaf bundle_](g) or an unpublished [_branch bundle_](g) whose content and resources you can include in other pages.

content/en/quick-reference/glossary/leaf-bundle.md

@@ -3,4 +3,4 @@ title: leaf bundle
 reference: /content-management/page-bundles/
 ---
 
-A _leaf bundle_ is a directory that contains an `index.md` file and zero or more [_resources_](g). Analogous to a physical leaf, a leaf bundle is at the end of a branch. It has no descendants.
+A _leaf bundle_ is a directory that contains an `index.md` file and zero or more [_resources_](g). Analogous to a physical leaf, a leaf bundle is at the end of a [_branch bundle_](g). It has no descendants.

content/en/quick-reference/glossary/section.md

@@ -2,4 +2,4 @@
 title: section
 ---
 
-A _section_ is a top-level content directory or any content directory containing an `_index.md` file. A section is also known as a [_branch bundle_](g).
+A _section_ is a top-level content directory or any content directory containing an `_index.md` file.