docs: refresh translations for recent English changes - #3636

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At i18n/tr/pages/handlers/cancellation.md, line 46:

<comment>The `Client` inflection is incorrect and makes this sentence unnatural. Use `` `Client`'ını kullanırken `` to express giving up while using this SDK's client.</comment>

<file context>
@@ -0,0 +1,60 @@
+
+Prompt ve kaynak fonksiyonları tam olarak araçlar gibi iptal edilir.
+
+İptal, stdio ve Streamable HTTP üzerinde aynı şekilde çalışır. Bu SDK'nın `Client`'ında vazgeçmek, `call_tool`'u bekleyen görevi iptal etmek ya da `read_timeout_seconds` süresinin dolmasına izin vermek demektir.
+
+!!! warning
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At i18n/tr/pages/handlers/cancellation.md, line 12:

<comment>This sentence is grammatically incomplete, so the page does not clearly introduce the two handler types that need special handling. Rewrite it as `İki tür işleyici için ise bir şey yapmanız gerekir: ...`.</comment>

<file context>
@@ -0,0 +1,60 @@
+
+Bu olduğunda SDK **işleyicinizi iptal eder**. İşleyicinin beklediği `await` istisna fırlatır, fonksiyon geri sarılır ve döndürdüğü hiçbir şey gönderilmez. Çoğu işleyicinin bu konuda bir şey yapması gerekmez.
+
+İki tür işleyicinin ise gerekir: temizlemesi gereken bir şey olan işleyici ve düz bir `def` olan işleyici.
+
+## `async def` araçta temizlik yapma {#clean-up-in-an-async-def-tool}
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At i18n/tr/pages/client/transports.md, line 64:

<comment>The translation changes `resumed streams` to `sürdürülen akışlar`, which describes an ongoing stream rather than a stream resumed after disconnection. Use `devam ettirilen akışlar` so readers know this limit also covers the reconnection path.</comment>

<file context>
@@ -44,22 +44,40 @@ Dikkat edilecek iki şey:
+```
+
+Varsayılan değer olay başına 1 MiB; bu, olay ayrıştırılmadan önce bayt cinsinden ölçülür. Sınır
+POST yanıtlarına, GET akışına ve sürdürülen akışlara uygulanır. Bir POST yanıtındaki ya da sürdürülen
+bir akıştaki aşırı büyük bir olay, o isteği bir SSE hatasıyla başarısız kılar. Arka plandaki GET akışında ise istemci
+hatayı log'a yazar ve akışı yeniden dener. Sunucuya güveniyorsanız ve daha büyük olaylara ihtiyacınız varsa
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At i18n/de/pages/advanced/header-parameters.md, line 54:

<comment>`um aus dem zu antworten` is not idiomatic German and makes this instruction unclear. Use `die auf Grundlage dessen antwortet, was du schon hast` instead.</comment>

<file context>
@@ -0,0 +1,65 @@
+--8<-- "docs_src/header_parameters/tutorial003.py"
+```
+
+* Übergib die Funktion, um aus dem zu antworten, was du schon hast.
+* Gib `None` für ein Tool zurück, bei dem es nichts zu prüfen gibt.
+
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At i18n/ja/pages/advanced/middleware.md, line 52:

<comment>この文は英語の「4 本の接続からなる単一プール」を「4 つの接続プール」としており、同時実行数の例のリソース構成を変えています。4 本の接続からなる 1 つのプールを表すよう修正してください。

(Based on your team's feedback about keeping translated docs aligned with the English source.) .</comment>

<file context>
@@ -45,12 +45,28 @@ tools/call took 0.1 ms
+
+ミドルウェアは必ずしも `call_next(ctx)` を呼ぶ必要はありません。代わりに `MCPError` を送出すると、そのメッセージ 1 つが**拒否**されます。接続は維持され、次のメッセージは通ります。
+
+たとえば、検索のたびに 4 本の接続プールから接続を 1 本占有するとします。このミドルウェアは、ツール呼び出しを同時に 4 つまで実行させ、5 つ目は拒否します。
+
+```python title="server.py" hl_lines="15-16 40-55 59"
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At i18n/zh-hant/pages/handlers/cancellation.md, line 12:

<comment>`有兩種需要：` is grammatically incomplete and obscures what the two kinds have in common. Replace it with `有兩種處理函式需要特別處理：`.</comment>

<file context>
@@ -0,0 +1,57 @@
+
+這時 SDK 會**取消你的處理函式**。它正在等待的那個 `await` 會引發例外，函式逐層退出，它回傳的任何東西都不會送出。大多數處理函式不需要為此做任何事。
+
+有兩種需要：有東西要清理的處理函式，以及用普通 `def` 寫的處理函式。
+
+## 在 `async def` 工具中清理 {#clean-up-in-an-async-def-tool}
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At i18n/de/pages/client/transports.md, line 47:

<comment>„ein `httpx2.AsyncClient`, der ohne gebaut wird“ fehlt das Objekt von „ohne“ — der Satz ist ungrammatisch. Die Entsprechungen in den anderen Sprachen (z. B. es „construido sin uno“, ru „созданный без него“) führen das Bezugsobjekt korrekt an. Ergänze „ohne einen (Timeout)“.</comment>

<file context>
@@ -44,23 +44,41 @@ Zwei Dinge fallen auf:
 * Der `httpx2.AsyncClient` gehört dir, also betrittst und verlässt **du** ihn. Das SDK schließt nie einen Client, den es nicht selbst erzeugt hat.
 * `streamable_http_client(url, http_client=...)` gibt einen Transport zurück, und `Client(transport)` nimmt ihn an wie alles andere auch.
 
+Behalte das `timeout=` bei. Es ist dasselbe, das der SDK-eigene Client verwendet (30 Sekunden, 300 für Lesevorgänge); ein `httpx2.AsyncClient`, der ohne gebaut wird, bekommt den 5-Sekunden-Standardwert von `httpx2`, und ein Tool-Aufruf, der länger läuft, schlägt mit einem Read-Timeout fehl.
+
 Eine Anmerkung zu TLS: `httpx2` prüft Zertifikate gegen den Trust Store des Betriebssystems (über
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At i18n/pt/pages/handlers/cancellation.md, line 12:

<comment>`Dois tipos precisam:` is incomplete Portuguese and makes the opening summary read awkwardly. Write `Dois tipos precisam de atenção:` before listing the affected handlers.</comment>

<file context>
@@ -0,0 +1,60 @@
+
+Quando isso acontece, o SDK **cancela o seu handler**. O `await` em que ele está esperando lança uma exceção, a função é desempilhada, e nada do que ela retornar é enviado. A maioria dos handlers não precisa fazer nada a respeito.
+
+Dois tipos precisam: um handler com algo para limpar, e um handler que é um `def` comum.
+
+## Faça a limpeza em uma ferramenta `async def` {#clean-up-in-an-async-def-tool}
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At i18n/pt/pages/troubleshooting.md, line 135:

<comment>Use the established translated page title `Parâmetros de cabeçalho` here. The current `Parâmetros de header` label gives the same page two different Portuguese names.</comment>

<file context>
@@ -128,6 +128,14 @@ Adicione os parênteses. `@mcp.resource(...)` e `@mcp.prompt()` dizem a mesma co
+
+Um argumento de ferramenta está marcado com `x-mcp-header` de um jeito que a especificação não permite, e `<reason>` diz qual regra ele quebra. Clientes em `2026-07-28` deixariam uma ferramenta assim fora da listagem deles, então o SDK se recusa a registrá-la.
+
+Só argumentos `str`, `int` e `bool` podem ser marcados, e `str | None` não é nenhum deles. **[Parâmetros de header](advanced/header-parameters.md)** tem a forma de escrever um argumento opcional.
+
+Como a entrada acima, isso lança quando o módulo é **importado**, antes de qualquer cliente se conectar.
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At i18n/de/pages/handlers/cancellation.md, line 24:

<comment>`Hier sind das 5 Sekunden` is grammatically incorrect German. Replace `das` with `es`.</comment>

<file context>
@@ -0,0 +1,60 @@
+
+* Das `finally` läuft, egal wie das Tool endet: ob es zurückgekehrt ist, eine Exception ausgelöst hat oder abgebrochen wurde.
+* Aufräumcode, der `await` verwenden muss, braucht `shield=True`. In einem abgebrochenen Handler löst auch jedes weitere `await` eine Exception aus. Ohne die Abschirmung würde `release_hold` also schon in seiner ersten Zeile stoppen.
+* Einen abgeschirmten Block kann nichts abbrechen, gib ihm also ein Zeitlimit. Hier sind das `5` Sekunden.
+
+!!! tip
</file context>