Copyedit and update the page (#10024)

- Minor updates.
- Added a link to permalinks for more info.
- Copyedit the content.
- Formatted the notes.

content/en/docs/contribute/style/content-organization.md

@@ -22,7 +22,7 @@ This site uses Hugo. In Hugo, [content organization](https://gohugo.io/content-m
 
 ### Page Order
 
-The documentation side menu, the documentation page browser etc. are listed using Hugo's default sort order, which sorts by weight (from 1), date (newest first) and finally by the link title.
+The documentation side menu, the documentation page browser etc. are listed using Hugo's default sort order, which sorts by weight (from 1), date (newest first), and finally by the link title.
 
 Given that, if you want to move a page or a section up, set a weight in the page's front matter:
 
@@ -33,7 +33,7 @@ weight: 10
 
 
 {{% note %}}
-For page weights, it can be smart not to use 1, 2, 3 ..., but some other interval, say 10, 20, 30... This allows you to insert pages where you want later.
+**Note:** For page weights, it can be smart not to use 1, 2, 3 ..., but some other interval, say 10, 20, 30... This allows you to insert pages where you want later.
 {{% /note %}}
 
 
@@ -57,7 +57,7 @@ linkTitle: Title used in links
 
 
 {{% note %}}
-The above needs to be done per language. If you don't see your section in the menu, it is probably because it is not identified as a section by Hugo. Create a `_index.md` content file in the section folder.
+**Note:** The above needs to be done per language. If you don't see your section in the menu, it is probably because it is not identified as a section by Hugo. Create a `_index.md` content file in the section folder.
 {{% /note %}}
 
 ### Documentation Side Menu
@@ -66,20 +66,19 @@ The documentation side-bar menu is built from the _current section tree_ startin
 
 It will show all sections and their pages.
 
-If you want a section or page to not be listed, set the `toc_hide` flag in front matter:
-
+If you don't want to list a section or page, set the `toc_hide` flag to `true` in front matter:
 
 ```yaml
 toc_hide: true
 ```
 
-When you navigate to a section, the page shown is the section page (e.g. `_index.md`) if it has content, else the first page inside that section.
+When you navigate to a section that has content, the specific section or page (e.g. `_index.md`) is shown. Else, the first page inside that section is shown.
 
 ### Documentation Browser
 
-The page browser on the documentation home page is built from all sections and pages directly below the `docs section`.
+The page browser on the documentation home page is built using all the sections and pages that are directly below the `docs section`.
 
-If you want a section or page to not be listed, set the `toc_hide` flag in front matter:
+If you don't want to list a section or page, set the `toc_hide` flag to `true` in front matter:
 
 ```yaml
 toc_hide: true
@@ -94,7 +93,7 @@ The site links in the top-right menu -- and also in the footer -- are built by p
 
 In addition to standalone content pages (Markdown files), Hugo supports [Page Bundles](https://gohugo.io/content-management/page-bundles/).
 
-One example is [Custom Hugo Shortcodes](/docs/contribute/style/hugo-shortcodes/). It is a socalled `leaf bundle`. Everything below the directory with the `index.md` will be part of the bundle, with page-relative links, images can be processed etc.:
+One example is [Custom Hugo Shortcodes](/docs/contribute/style/hugo-shortcodes/). It is considered a `leaf bundle`. Everything below the directory, including the `index.md`, will be part of the bundle. This also includes page-relative links, images that can be processed etc.:
 
 ```bash
 en/docs/home/contribute/includes
@@ -104,7 +103,7 @@ en/docs/home/contribute/includes
 └── podtemplate.json
 ```
 
-Another example used widely is the `includes` bundle. It has `headless: true` set in front matter, which means that it does not get its own URL. It is only used in other pages.
+Another widely used example is the `includes` bundle. It sets `headless: true` in front matter, which means that it does not get its own URL. It is only used in other pages.
 
 ```bash
 en/includes
@@ -123,7 +122,7 @@ Some important notes to the files in the bundles:
 
 * For translated bundles, any missing non-content files will be inherited from languages above. This avoids duplication.
 * All the files in a bundle are what Hugo calls `Resources` and you can provide metadata per language, such as parameters and title, even if it does not supports front matter (YAML files etc.). See [Page Resources Metadata](https://gohugo.io/content-management/page-resources/#page-resources-metadata).
-* The value you get from `.RelPermalink` from a `Resource` is page-relative.
+* The value you get from `.RelPermalink` of a `Resource` is page-relative. See [Permalinks](https://gohugo.io/content-management/urls/#permalinks).
 
 
 ## Styles