[ZT] Fix sidenav casing (#17332)

Author: maxvp

src/content/docs/cloudflare-one/applications/non-http/short-lived-certificates-legacy.mdx

@@ -14,8 +14,10 @@ import { Render } from "~/components";
 Cloudflare recommends configuring short-lived certificates through our new [Access for Infrastructure](/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access/) workflow. Access for Infrastructure supports differing SSH aliases out-of-the-box, removes the need for client SSH configuration, and allows for more granular security policies.
 :::
 
-<Render file="access/short-lived-certs-intro" params={{ intro: "Cloudflare Access can replace" }} />
-
+<Render
+	file="access/short-lived-certs-intro"
+	params={{ intro: "Cloudflare Access can replace" }}
+/>
 
 ## 1. Secure the server behind Cloudflare Access
 
@@ -38,7 +40,7 @@ Cloudflare Access will take the identity from a token and, using short-lived cer
 
 ## 3. Generate a short-lived certificate public key
 
-1. In Zero Trust, go to **Access** > **Service Auth** > **SSH**.
+1. In Zero Trust, go to **Access** > **Service auth** > **SSH**.
 
 2. In the **Application** dropdown, choose the Access application that represents your SSH server.
 

src/content/docs/cloudflare-one/connections/connect-devices/agentless/dns/dns-over-tls.mdx

@@ -3,7 +3,6 @@ pcx_content_type: how-to
 title: DNS over TLS (DoT)
 sidebar:
   order: 2
-
 ---
 
 By default, DNS is sent over a plaintext connection. DNS over TLS (DoT) is a standard for encrypting DNS queries to keep them secure and private. DoT uses the same security protocol, TLS, that HTTPS websites use to encrypt and authenticate communications.
@@ -14,7 +13,7 @@ Cloudflare supports DoT on standard port `853` and is compliant with [RFC7858](h
 
 Each Gateway DNS location has a unique DoT hostname. DNS locations and corresponding DoT hostnames have policies associated with them.
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **DNS Locations**.
+1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **DNS locations**.
 2. If you have more than one location set up, you will see a list of all your locations.
 3. Expand the location card for the location whose DoT hostname you'd like to retrieve.
 4. Get the **DoT hostname** for the location.

src/content/docs/cloudflare-one/connections/connect-devices/agentless/dns/locations/dns-resolver-ips.mdx

@@ -9,7 +9,7 @@ When you create a DNS location, Gateway assigns IPv4/IPv6 addresses and DoT/DoH
 
 To view the resolver endpoint IP addresses and hostnames for a DNS location:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **DNS Locations**.
+1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **DNS locations**.
 2. Locate the DNS location, then select **Configure**.
 3. Go to **Setup instructions**. The addresses and hostnames will appear in **Your configuration**.
 

src/content/docs/cloudflare-one/connections/connect-devices/agentless/pac-files.mdx

@@ -36,7 +36,7 @@ All devices you add to the proxy endpoint will be able to access your Cloudflare
 
 <TabItem label="Dashboard">
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Proxy Endpoints**.
+1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Proxy endpoints**.
 
 2. Select **Create endpoint**.
 

src/content/docs/cloudflare-one/faq/troubleshooting.mdx

@@ -67,7 +67,7 @@ For more troubleshooting information, refer to [Support](/support/troubleshootin
 
 You may not see analytics on the Overview page for the following reasons:
 
-- **You are not sending DNS queries to Gateway**. Verify that the destination IP addresses you are sending DNS queries to are correct. You can check the destination IP addresses for your DNS location by going to **Gateway** > **DNS Locations** and then expanding the location.
+- **You are not sending DNS queries to Gateway**. Verify that the destination IP addresses you are sending DNS queries to are correct. You can check the destination IP addresses for your DNS location by going to **Gateway** > **DNS locations** and then expanding the location.
 - **You are using other DNS resolvers**. If you have other DNS resolvers in your DNS settings, your device could be using IP addresses for resolvers that are not part of Gateway. Make sure to remove all other IP addresses from your DNS settings and only include Gateway's DNS resolver IP addresses.
 - **The source IPv4 address for your DNS location is incorrect**. If you are using IPv4, check the source IPv4 address that you entered for the DNS location matches with the network's source IPv4 address.
 - **Analytics is not available yet**. It takes some time to generate the analytics for Cloudflare Gateway. If you are not seeing anything even after 5 minutes, file a support ticket.

src/content/docs/cloudflare-one/identity/devices/access-integrations/mutual-tls-authentication.mdx

@@ -30,7 +30,7 @@ mTLS is checked on a per host basis. Access sets a flag for when a client certif
 
 To enforce mTLS authentication from [Zero Trust](https://one.dash.cloudflare.com):
 
-1. Go to **Access** > **Service Auth** > **Mutual TLS**.
+1. Go to **Access** > **Service auth** > **Mutual TLS**.
 
 2. Select **Add mTLS Certificate**.
 

src/content/docs/cloudflare-one/identity/service-tokens.mdx

@@ -62,7 +62,7 @@ Service tokens expire according to the token duration you selected when you crea
 
 To renew the service token:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Service Auth** > **Service Tokens**.
+1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Service auth** > **Service Tokens**.
 2. Locate the token you want to renew.
 3. To extend the token's lifetime by one year, select **Refresh**.
 4. To extend the token's lifetime by more than a year:
@@ -74,7 +74,7 @@ To renew the service token:
 
 If you need to revoke access before the token expires, simply delete the token.
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Service Auth** > **Service Tokens**.
+1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Service auth** > **Service Tokens**.
 2. **Delete** the token you need to revoke.
 
 Services that rely on a deleted service token can no longer reach your application.

src/content/docs/cloudflare-one/policies/browser-isolation/setup/index.mdx

@@ -24,7 +24,7 @@ Setup instructions vary depending on how you want to connect your devices to Clo
 
 To configure Browser Isolation policies:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Gateway** > **Firewall Policies** > **HTTP**.
+1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Gateway** > **Firewall policies** > **HTTP**.
 2. Select **Add a policy** and enter a name for the policy.
 3. Use the HTTP policy [selectors](/cloudflare-one/policies/gateway/http-policies/#selectors) and [operators](/cloudflare-one/policies/gateway/http-policies/#comparison-operators) to specify the websites or content you want to isolate.
 4. For **Action**, choose either [_Isolate_](/cloudflare-one/policies/browser-isolation/isolation-policies/#isolate) or [_Do not Isolate_](/cloudflare-one/policies/browser-isolation/isolation-policies/#do-not-isolate).

src/content/docs/cloudflare-one/policies/data-loss-prevention/dlp-policies/index.mdx

@@ -27,7 +27,7 @@ DLP scans will not start until you [create a DLP policy](#2-create-a-dlp-policy)
 
 DLP Profiles may be used alongside other Zero Trust rules in a [Gateway HTTP policy](/cloudflare-one/policies/gateway/http-policies/). To start logging or blocking traffic, create a policy for DLP:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Gateway** > **Firewall Policies**. Select **HTTP**.
+1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Gateway** > **Firewall policies**. Select **HTTP**.
 
 2. Select **Add a policy**.
 

src/content/docs/cloudflare-one/policies/data-loss-prevention/dlp-policies/payload-logging.mdx

@@ -3,7 +3,6 @@ pcx_content_type: how-to
 title: Log the payload of matched rules
 sidebar:
   order: 2
-
 ---
 
 Data Loss Prevention allows you to log the data that triggered a specific DLP policy. This data is stored in the portion of the HTTP request known as the payload. Payload logging is especially useful when diagnosing the behavior of DLP rules. Since the values that triggered a rule may contain sensitive data, they are encrypted with a customer-provided public key so that only you can examine them later. The stored data will include a redacted version of the match, plus 20 bytes of additional context on both sides of the match.
@@ -22,14 +21,14 @@ Follow [these instructions](/waf/managed-rules/payload-logging/command-line/gene
 
 :::note
 
-The matching private key is required to view logs. If you lose your private key, you will need to [generate](#1-generate-a-key-pair) and [upload](#2-upload-the-public-key-to-cloudflare) a new public key. The payload of new requests will be encrypted with the new public key. 
+The matching private key is required to view logs. If you lose your private key, you will need to [generate](#1-generate-a-key-pair) and [upload](#2-upload-the-public-key-to-cloudflare) a new public key. The payload of new requests will be encrypted with the new public key.
 :::
 
 ## 3. Enable payload logging for a DLP policy
 
 You can enable payload logging for any Allow or Block HTTP policy that uses the [DLP Profile](/cloudflare-one/policies/gateway/http-policies/#dlp-profile) selector.
 
-1. Go to **Gateway** > **Firewall Policies** > **HTTP**.
+1. Go to **Gateway** > **Firewall policies** > **HTTP**.
 
 2. Edit an existing Allow or Block DLP policy, or [create a new policy](/cloudflare-one/policies/data-loss-prevention/dlp-policies/#2-create-a-dlp-policy).
 
@@ -53,15 +52,15 @@ You will see the [ID of the matched DLP Profile](/api/operations/dlp-profiles-li
 
 :::note
 
-Neither the key nor the decrypted payload will be stored by Cloudflare. 
+Neither the key nor the decrypted payload will be stored by Cloudflare.
 :::
 
 ## Data privacy
 
-* All Cloudflare logs are encrypted at rest. Encrypting the payload content adds a second layer of encryption for the matched values that triggered a DLP rule.
+- All Cloudflare logs are encrypted at rest. Encrypting the payload content adds a second layer of encryption for the matched values that triggered a DLP rule.
 
-* Cloudflare cannot decrypt encrypted payloads, since this operation requires your private key. Cloudflare staff will never ask for the private key.
+- Cloudflare cannot decrypt encrypted payloads, since this operation requires your private key. Cloudflare staff will never ask for the private key.
 
-* DLP will redact all predefined alphanumeric characters in the log. For example, `123-45-6789` will become `XXX-XX-XXXX`.
+- DLP will redact all predefined alphanumeric characters in the log. For example, `123-45-6789` will become `XXX-XX-XXXX`.
 
-  * You can define sensitive data with [Exact Data Match (EDM)](/cloudflare-one/policies/data-loss-prevention/datasets/#exact-data-match). EDM match logs will redact your defined strings.
+  - You can define sensitive data with [Exact Data Match (EDM)](/cloudflare-one/policies/data-loss-prevention/datasets/#exact-data-match). EDM match logs will redact your defined strings.