Tweak line wrappings in content-organization.md

windsonsea · windsonsea · commit 1ec7fe8e63b6 · 2023-06-01T21:49:31.000+08:00
diff --git a/content/en/docs/contribute/style/content-guide.md b/content/en/docs/contribute/style/content-guide.md
@@ -17,8 +17,6 @@ You can register for Kubernetes Slack at https://slack.k8s.io/.
 For information on creating new content for the Kubernetes
 docs, follow the [style guide](/docs/contribute/style/style-guide).
 
-
-
 <!-- body -->
 
 ## Overview
@@ -40,15 +38,19 @@ Kubernetes docs allow content for third-party projects only when:
 
 ### Third party content
 
-Kubernetes documentation includes applied examples of projects in the Kubernetes project&mdash;projects that live in the [kubernetes](https://github.com/kubernetes) and
+Kubernetes documentation includes applied examples of projects in the Kubernetes
+project&mdash;projects that live in the [kubernetes](https://github.com/kubernetes) and
 [kubernetes-sigs](https://github.com/kubernetes-sigs) GitHub organizations.
 
 Links to active content in the Kubernetes project are always allowed.
 
 Kubernetes requires some third party content to function. Examples include container runtimes (containerd, CRI-O, Docker),
-[networking policy](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/) (CNI plugins), [Ingress controllers](/docs/concepts/services-networking/ingress-controllers/), and [logging](/docs/concepts/cluster-administration/logging/).
+[networking policy](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/) (CNI plugins),
+[Ingress controllers](/docs/concepts/services-networking/ingress-controllers/),
+and [logging](/docs/concepts/cluster-administration/logging/).
 
-Docs can link to third-party open source software (OSS) outside the Kubernetes project only if it's necessary for Kubernetes to function.
+Docs can link to third-party open source software (OSS) outside the Kubernetes
+project only if it's necessary for Kubernetes to function.
 
 ### Dual sourced content
 
@@ -59,19 +61,14 @@ Dual-sourced content requires double the effort (or more!) to maintain
 and grows stale more quickly.
 
 {{< note >}}
-
 If you're a maintainer for a Kubernetes project and need help hosting your own docs,
 ask for help in [#sig-docs on Kubernetes Slack](https://kubernetes.slack.com/messages/C1J0BPD2M/).
-
 {{< /note >}}
 
 ### More information
 
 If you have questions about allowed content, join the [Kubernetes Slack](https://slack.k8s.io/) #sig-docs channel and ask!
 
-
-
 ## {{% heading "whatsnext" %}}
 
-
 * Read the [Style guide](/docs/contribute/style/style-guide).
diff --git a/content/en/docs/contribute/style/content-organization.md b/content/en/docs/contribute/style/content-organization.md
@@ -4,13 +4,10 @@ content_type: concept
 weight: 90
 ---
 
-
 <!-- overview -->
 
 This site uses Hugo. In Hugo, [content organization](https://gohugo.io/content-management/organization/) is a core concept.
 
-
-
 <!-- body -->
 
 {{% note %}}
@@ -21,7 +18,9 @@ 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:
 
@@ -30,34 +29,36 @@ title: My Page
 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.
-Additionally, each weight within the same directory (section) should not be overlapped with the other weights. This makes sure that content is always organized correctly, especially in localized content. 
+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.
+Additionally, each weight within the same directory (section) should not be
+overlapped with the other weights. This makes sure that content is always
+organized correctly, especially in localized content.
 {{% /note %}}
 
-
 ### Documentation Main Menu
 
-The `Documentation` main menu is built from the sections below `docs/` with the `main_menu` flag set in front matter of the `_index.md` section content file:
+The `Documentation` main menu is built from the sections below `docs/` with
+the `main_menu` flag set in front matter of the `_index.md` section content file:
 
 ```yaml
 main_menu: true
 ```
 
-
-Note that the link title is fetched from the page's `linkTitle`, so if you want it to be something different than the title, change it in the content file:
-
+Note that the link title is fetched from the page's `linkTitle`, so if you want
+it to be something different than the title, change it in the content file:
 
 ```yaml
 main_menu: true
 title: Page Title
 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.
+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
@@ -72,11 +73,13 @@ If you don't want to list a section or page, set the `toc_hide` flag to `true` i
 toc_hide: true
 ```
 
-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.
+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 using all the sections and pages that are 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 don't want to list a section or page, set the `toc_hide` flag to `true` in front matter:
 
@@ -86,14 +89,18 @@ toc_hide: true
 
 ### The Main Menu
 
-The site links in the top-right menu -- and also in the footer -- are built by page-lookups. This is to make sure that the page actually exists. So, if the `case-studies` section does not exist in a site (language), it will not be linked to.
-
+The site links in the top-right menu -- and also in the footer -- are built by
+page-lookups. This is to make sure that the page actually exists. So, if the
+`case-studies` section does not exist in a site (language), it will not be linked to.
 
 ## Page Bundles
 
-In addition to standalone content pages (Markdown files), Hugo supports [Page Bundles](https://gohugo.io/content-management/page-bundles/).
+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 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.:
+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
@@ -103,7 +110,8 @@ en/docs/home/contribute/includes
 └── podtemplate.json
 ```
 
-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.
+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
@@ -118,22 +126,22 @@ en/includes
 
 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` of a `Resource` is page-relative. See [Permalinks](https://gohugo.io/content-management/urls/#permalinks).
-
+* 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` of a `Resource` is page-relative.
+  See [Permalinks](https://gohugo.io/content-management/urls/#permalinks).
 
 ## Styles
 
-The [SASS](https://sass-lang.com/) source of the stylesheets for this site is stored in `assets/sass` and is automatically built by Hugo.
-
-
+The [SASS](https://sass-lang.com/) source of the stylesheets for this site is
+stored in `assets/sass` and is automatically built by Hugo.
 
 ## {{% heading "whatsnext" %}}
 
-
 * Learn about [custom Hugo shortcodes](/docs/contribute/style/hugo-shortcodes/)
 * Learn about the [Style guide](/docs/contribute/style/style-guide)
 * Learn about the [Content guide](/docs/contribute/style/content-guide)
-
-
diff --git a/content/en/docs/contribute/style/style-guide.md b/content/en/docs/contribute/style/style-guide.md
