Hyperlint Automation Fix

Author: hyperlint-ai[bot]

src/content/docs/agents/api-reference/using-ai-models.mdx

@@ -20,7 +20,7 @@ You can also use the model routing features in [AI Gateway](/ai-gateway/) to rou
 
 Because Agents are built on top of [Durable Objects](/durable-objects/), each Agent or chat session is associated with a stateful compute instance. Traditional serverless architectures often present challenges for persistent connections needed in real-time applications like chat.
 
-A user can disconnect during a long-running response from a modern reasoning model (such as `o3-mini` or DeepSeek R1), or lose conversational context when refreshing the browser. Instead of relying on request-response patterns and managing an external database to track & store conversation state, state can be stored directly within the Agent. If a client disconnects, the Agent can write to its own distributed storage, and catch the client up as soon as it reconnects: even if it's hours or days later.
+If a client disconnects, the Agent can write to its own distributed storage, and catch the client up as soon as it reconnects: even if it is hours or days later.
 
 ## Calling AI Models
 
@@ -174,7 +174,7 @@ export class MyAgent extends Agent<Env> {
 
 </TypeScriptExample>
 
-Your wrangler configuration will need an `ai` binding added. This is shared across both Workers AI and AI Gateway.
+To configure your wrangler setup, include an `ai` binding, which is applicable for both Workers AI and AI Gateway.
 <WranglerConfig>
 
 ```toml