Merge branch 'fix/voice-connection-duration-docs' into 'main'

docs(voice): correct connection duration guidance

See merge request deepl-org/deepl/clapi-track/api-docs-mirror!262

Author: Lennart Hoffjann

docs/voice/understanding-voice-sessions.mdx

@@ -48,7 +48,7 @@ Two security properties follow from the token design:
 * Each token and streaming URL is valid for one-time use. Using a token more than once to open a WebSocket connection terminates the session immediately.
 * Only the latest token can request a reconnection. Presenting an outdated token invalidates the session.
 
-Requesting a reconnection token while a connection is still active disconnects that connection, so only reconnect after the existing connection has closed. Connections also have a maximum duration; when it's reached, reconnect the same way to continue the session. See [session limits](/docs/voice/voice-api-requirements#session-limits) for the exact values.
+Requesting a reconnection token while a connection is still active disconnects that connection, so only reconnect after the existing connection has closed. The API keeps connections open for as long as possible, but your client must handle disconnects and reconnect to continue the session. See [session limits](/docs/voice/voice-api-requirements#session-limits) for details.
 
 ## How audio and results flow
 

docs/voice/voice-api-requirements.mdx

@@ -26,7 +26,7 @@ For the detailed list of supported input audio formats, see [Source Media Conten
 * Recommended chunk duration: 50-250 milliseconds for low latency
 * Audio stream speed: maximum 2x real-time
 * Timeout: if no data is received for 30 seconds, the session is terminated
-* Maximum connection duration: after 1 hour, the connection is closed. Establish a new connection by [reconnecting](/api-reference/voice/reconnect-session) to the session
+* Connection duration: the API keeps connections open for as long as possible, but connections can close at any time. Your client must handle disconnects and [reconnect](/api-reference/voice/reconnect-session) to continue the session
 * Using any given token more than once to establish a WebSocket connection terminates the associated session immediately for security reasons
 
 If you need more translation targets or translated speech targets than these limits allow, open multiple concurrent sessions over the same source audio.