correcting headings style guide recommendation

nate-double-u · nate-double-u · commit f3ba85a033d7 · 2024-11-18T11:26:33.000-08:00
Signed-off-by: Nate W &lt;natew@cncf.io&gt;
diff --git a/content/en/docs/contribute/style/style-guide.md b/content/en/docs/contribute/style/style-guide.md
@@ -511,7 +511,7 @@ Use pound or hash signs (`#`) for non-blog post content. | Use underlines (`---`
 Use sentence case for headings in the page body. For example, **Extend kubectl with plugins** | Use title case for headings in the page body. For example, **Extend Kubectl With Plugins**
 Use title case for the page title in the front matter. For example, `title: Kubernetes API Server Bypass Risks` | Use sentence case for page titles in the front matter. For example, don't use `title: Kubernetes API server bypass risks`
 Place relevant links in the body copy. | Include hyperlinks (`<a href=""></a>`) in headings.
-Use proper heading markers (`---` or `===`) to indicate headings. | Use **bold** text or other indicators to split paragraphs.
+Use pound or hash signs (`#`) to indicate headings. | Use **bold** text or other indicators to split paragraphs.
 {{< /table >}}
 
 ### Paragraphs
@@ -701,4 +701,4 @@ the rest of the project. To view the file, refer to
 * Learn about [writing a new topic](/docs/contribute/style/write-new-topic/).
 * Learn about [using page templates](/docs/contribute/style/page-content-types/).
 * Learn about [custom hugo shortcodes](/docs/contribute/style/hugo-shortcodes/).
-* Learn about [creating a pull request](/docs/contribute/new-content/open-a-pr/).
+* Learn about [creating a pull request](/docs/contribute/new-content/open-a-pr/).
