Add more languages support for disfluency

[giorgosHadji]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Jul 22, 2026 12:27pm

[petemomo]

Thanks for this — and for adding the language codes, which brings the list in line with the profanities convention on the page. One ask, one question (inline), and two optional nits (inline).

The API spec still says English-only. spec/realtime.yaml (line 1130) reads "[disfluency] is only present in English", and the API reference pages are generated from that spec — merged as-is, the docs would claim both 20-language and English-only support. Since the spec lives in this repo, could you update that description in this PR? If the spec change is tracked elsewhere (e.g. it mirrors an upstream source), let me know and we'll file a follow-up instead.

[petemomo]

Nit: "the full list above" is a positional reference. Something like "the expandable list at the start of this section covers English" survives restructuring better.

[giorgosHadji]

Indeed! Nice! changed

[giorgosHadji]

Thanks for this — and for adding the language codes, which brings the list in line with the profanities convention on the page. One ask, one question (inline), and two optional nits (inline).

The API spec still says English-only. spec/realtime.yaml (line 1130) reads "[disfluency] is only present in English", and the API reference pages are generated from that spec — merged as-is, the docs would claim both 20-language and English-only support. Since the spec lives in this repo, could you update that description in this PR? If the spec change is tracked elsewhere (e.g. it mirrors an upstream source), let me know and we'll file a follow-up instead.

I have changed the spec as well here to reflect the change.
Nice catch Pete! Missed that

[petemomo]

All addressed — thanks for the fast turnaround, and for going beyond the ask: catching the extra reference in voice-agent-api.mdx and making the Smart formatting heading self-contained too.

Verified locally on the updated branch:

• No English-only disfluency claims remain anywhere in docs or spec.
• The new #supported-languages-for-disfluencies anchor is used consistently in all three places, and nothing links to the old #languages anchor, so that rename is safe.
• The page renders correctly with the new headings and updated in-page link.

One optional nit, take it or leave it: "Disfluency detection is supported for [supported languages]" in voice-agent-api.mdx doubles up — "available for the [supported languages]" reads smoother.

The Mandarin naming unification stays as the agreed separate task — we'll pick it up on our side. LGTM 👍