Updates navigation (#26762)

Author: angelampcosta

src/content/docs/speed/optimization/protocol/enhanced-http2-prioritization.mdx

@@ -29,7 +29,7 @@ To enable **Enhanced HTTP/2 Prioritization** in the Cloudflare dashboard:
 
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com).
 2. Select your account and zone.
-3. Go to **Speed** > **Optimization**.
+3. Go to **Speed** > **Settings**.
 4. Go to **Protocol Optimization**.
 5. For **Enhanced HTTP/2 Prioritization**, switch the toggle to **On**.
 

src/content/docs/speed/optimization/protocol/http2.mdx

@@ -33,7 +33,7 @@ To disable **HTTP/2** in the dashboard:
 
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com).
 2. Select your account and zone.
-3. Go to **Speed** > **Optimization**.
+3. Go to **Speed** > **Settings**.
 4. Go to **Protocol Optimization**.
 5. For **HTTP/2**, switch the toggle to **Off**.
 

src/content/docs/speed/optimization/protocol/http3.mdx

@@ -35,7 +35,7 @@ To enable **HTTP/3** in the dashboard:
 
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com).
 2. Select your account and zone.
-3. Go to **Speed** > **Optimization**.
+3. Go to **Speed** > **Settings**.
 4. Go to **Protocol Optimization**.
 5. For **HTTP/3**, switch the toggle to **On**.
 

src/content/docs/support/third-party-software/content-management-system-cms/speed-up-wordpress-and-improve-performance.mdx

@@ -15,7 +15,7 @@ Cloudflare's "[Bypass Cache on Cookie](/cache/how-to/cache-rules/examples/bypass
 
 ### Optimise Images
 
-Images can be incredibly costly to page load times; fortunately, Cloudflare can dramatically help improve image load times. You can find these features in the Cloudflare dashboard by going to **Speed** > **Optimization** > **Image Optimization**.
+Images can be incredibly costly to page load times; fortunately, Cloudflare can dramatically help improve image load times. You can find these features in the Cloudflare dashboard by going to **Speed** > **Settings** > **Image Optimization**.
 
 After enabling [**Polish**](/images/polish/), you can dramatically improve image and web page load times by compressing images and stripping metadata. Lossless will strip most metadata (`EXIF` data, for example) but doesn't change the image detail. Lossy will strip most metadata and compresses images by approximately 48 percent.
 

src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520.mdx

@@ -36,7 +36,7 @@ As a temporary workaround, you can set the affected DNS record to [DNS-only](/dn
 
 - Contact your hosting provider or site administrator and share the necessary [error details](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#required-error-details-for-hosting-provider) to assist with troubleshooting. Request a review of your origin web server error logs for crashes and check for [common causes](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/#common-causes) mentioned in the previous section.
 
-- If HTTP/2 is enabled at your origin server, ensure it is correctly set up. Cloudflare connects to servers who announce support of HTTP/2 connections via [ALPN](https://blog.cloudflare.com/introducing-http2). If the origin web server accepts the HTTP/2 connection but then does not respect or support the protocol, an HTTP `520` error will be returned. You can disable the [HTTP/2 to Origin](/speed/optimization/protocol/http2-to-origin/#disable-http2-to-origin) in **Speed** > **Optimization** > **Protocol Optimization** on the Cloudflare dashboard.
+- If HTTP/2 is enabled at your origin server, ensure it is correctly set up. Cloudflare connects to servers who announce support of HTTP/2 connections via [ALPN](https://blog.cloudflare.com/introducing-http2). If the origin web server accepts the HTTP/2 connection but then does not respect or support the protocol, an HTTP `520` error will be returned. You can disable the [HTTP/2 to Origin](/speed/optimization/protocol/http2-to-origin/#disable-http2-to-origin) in **Speed** > **Settings** > **Protocol Optimization** on the Cloudflare dashboard.
 
 - If `520` errors continue after contacting your hosting provider or site administrator, provide the following information to [Cloudflare Support](/support/contacting-cloudflare-support/):
   - Full URL(s) of the resource requested when the error occurred.

src/content/docs/workers/reference/protocols.mdx

@@ -14,5 +14,5 @@ Cloudflare Workers support the following protocols and interfaces:
 | **Direct TCP sockets** | Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/)                                                                                                                                                                             | Create outbound TCP connections using the [`connect()` API](/workers/runtime-apis/tcp-sockets/)              |
 | **WebSockets**         | Accept incoming WebSocket connections using the [`WebSocket` API](/workers/runtime-apis/websockets/), or with [MQTT over WebSockets (Pub/Sub)](/pub-sub/learning/websockets-browsers/)                                                                                                                           | [MQTT over WebSockets (Pub/Sub)](/pub-sub/learning/websockets-browsers/)                                     |
 | **MQTT**               | Handle incoming messages to an MQTT broker with [Pub Sub](/pub-sub/learning/integrate-workers/)                                                                                                                                                                                                                  | Support for publishing MQTT messages to an MQTT topic is [coming soon](/pub-sub/learning/integrate-workers/) |
-| **HTTP/3 (QUIC)**      | Accept inbound requests over [HTTP/3](https://www.cloudflare.com/learning/performance/what-is-http3/) by enabling it on your [zone](/fundamentals/concepts/accounts-and-zones/#zones) in **Speed** > **Optimization** > **Protocol Optimization** area of the [Cloudflare dashboard](https://dash.cloudflare.com/). |                                                                                                              |
+| **HTTP/3 (QUIC)**      | Accept inbound requests over [HTTP/3](https://www.cloudflare.com/learning/performance/what-is-http3/) by enabling it on your [zone](/fundamentals/concepts/accounts-and-zones/#zones) in **Speed** > **Settings** > **Protocol Optimization** area of the [Cloudflare dashboard](https://dash.cloudflare.com/). |                                                                                                              |
 | **SMTP**               | Use [Email Workers](/email-routing/email-workers/) to process and forward email, without having to manage TCP connections to SMTP email servers                                                                                                                                                                  | [Email Workers](/email-routing/email-workers/)                                                               |