nit

Author: devalog

fern/products/docs/pages/navigation/overview.mdx

@@ -12,6 +12,7 @@ Every Fern Docs website has a special configuration file called `docs.yml`. Use
 Here's a complete example of a `docs.yml` file:
 
 <CodeBlock title="An example docs.yml">
+
 ```yaml
 # yaml-language-server: $schema=https://schema.buildwithfern.dev/docs-yml.json
 navigation:
@@ -21,7 +22,7 @@ navigation:
         path: ./intro.mdx
       - page: Authentication
         path: ./auth.mdx
-  - api: API reference
+  - api: API Reference
 navbar-links:
   - type: secondary
     text: Contact support
@@ -47,7 +48,7 @@ navigation:
     contents:
       - page: My page
         path: ./pages/my-page.mdx
-  - api: API reference
+  - api: API Reference
 ```
 {/* <!-- vale on --> */}
 If you want to add another page to an existing section, create an `.md` or `.mdx` file. Then in `docs.yml`, create a new `page` in the `contents` list for that section, providing the path to the `.md` or `.mdx` file you created. Example:
@@ -60,7 +61,7 @@ navigation:
         path: ./pages/my-page.mdx
       - page: Another page
         path: ./pages/another-page.mdx
-  - api: API reference
+  - api: API Reference
 ```
 
 To add another section, add another `section` to the `navigation`. Example:
@@ -71,7 +72,7 @@ navigation:
     contents:
       - page: My page
         path: ./pages/my-page.mdx
-  - api: API reference
+  - api: API Reference
   - section: Help center
     contents:
       - page: Contact us
@@ -209,7 +210,7 @@ navigation:
       - page: My page
         icon: fa-regular fa-file
         path: ./pages/my-page.mdx
-  - api: API reference
+  - api: API Reference
     icon: fa-regular fa-puzzle
 ```
 {/* <!-- vale on --> */}
@@ -244,7 +245,7 @@ Within the navigation, you can add `tabs`. Tabs are used to group sections toget
 ```yaml
 tabs: 
   api: 
-    display-name: API reference
+    display-name: API Reference
     icon: puzzle
   help:
     display-name: Help center
@@ -294,7 +295,7 @@ If you have multiple versions of your documentation, you can introduce a dropdow
 
 ## Product switching
 
-If you have multiple products in your documentation, you can introduce a [dropdown product selector](/learn/docs/configuration/products) by creating separate product configuration files. Each product can contain its own distinct versions, tabs, sections, pages, and API references, though products can also share content.
+If you have multiple products in your documentation, you can introduce a [dropdown product selector](/learn/docs/configuration/products) by creating separate product configuration files. Each product can contain its own distinct versions, tabs, sections, pages, and API References, though products can also share content.
 
 <CodeBlock title="docs.yml">
 ```yaml {2-3, 7-8}