Minor edits

Author: daisyfaithauma

src/content/docs/ai-gateway/providers/universal.mdx

@@ -14,8 +14,6 @@ You can use the Universal Endpoint to contact every provider.
 https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}
 ```
 
-## Description
-
 AI Gateway offers multiple endpoints for each Gateway you create - one endpoint per provider, and one Universal Endpoint. The Universal Endpoint requires some adjusting to your schema, but supports additional features. Some of these features are, for example, retrying a request if it fails the first time, or configuring a [fallback model/provider](/ai-gateway/configuration/fallbacks/).
 
 You can use the Universal endpoint to contact every provider. The payload is expecting an array of message, and each message is an object with the following parameters:
@@ -25,17 +23,17 @@ You can use the Universal endpoint to contact every provider. The payload is exp
 - `authorization`: the content of the Authorization HTTP Header that should be used when contacting this provider. This usually starts with “Token” or “Bearer”.
 - `query`: the payload as the provider expects it in their official API.
 
-## Example
+## cURL example
 
 <Render file="universal-gateway-example" />
 
 The above will send a request to Workers AI Inference API, if it fails it will proceed to OpenAI. You can add as many fallbacks as you need, just by adding another JSON in the array.
 
-## Websockets API <Badge text="beta" variant="tip" size="small" />
+## WebSockets API <Badge text="beta" variant="tip" size="small" />
 
 The Universal Endpoint can also be accessed via a [WebSockets API](/ai-gateway/configuration/websockets-api/) which provides a single persistent connection, enabling continuous communication. This API supports all AI providers connected to AI Gateway, including those that do not natively support WebSockets.
 
-## Example request
+## WebSockets example
 
 ```javascript
 import WebSocket from "ws";
@@ -87,7 +85,7 @@ Since the same settings can be configured in multiple locations, AI Gateway appl
 
 This hierarchy ensures consistent behavior, prioritizing the most specific configurations. Use provider-level and request-level headers for fine-tuned control, and gateway settings for general defaults.
 
-## Example
+## Hierarchy example
 
 This example demonstrates how headers set at different levels impact caching behavior: