Fix: Clarify webhook timeout reasons

Co-authored-by: sahil <[email protected]>

Author: cursoragent

fern/server-url/events.mdx

@@ -114,7 +114,7 @@ For inbound phone calls, you can specify the assistant dynamically. If a PhoneNu
 ```
 
 <Note>
-  You must respond to the `assistant-request` webhook within <strong>7.5 seconds end-to-end</strong>. This limit is fixed and not configurable: Twilio enforces a 15-second cap, and Vapi reserves ~7.5 seconds for call setup. The timeout value shown elsewhere in the dashboard does not apply to this webhook.
+  You must respond to the `assistant-request` webhook within <strong>7.5 seconds end-to-end</strong>. This limit is fixed and not configurable: the telephony provider enforces a 15-second cap, and Vapi reserves ~7.5 seconds for call setup. The timeout value shown elsewhere in the dashboard does not apply to this webhook.
 
   To avoid timeouts:
   - Return quickly with an existing <code>assistantId</code> or a minimal assistant, then enrich context asynchronously after the call starts using <a href="/calls/call-features">Live Call Control</a>.