Skip to content

docs(custom-vocabulary): optimize page for GEO - #148

Open
karamouche wants to merge 2 commits into
mainfrom
fix/geo-custom-vocabulary
Open

karamouche wants to merge 2 commits into
mainfrom
fix/geo-custom-vocabulary

Conversation

@karamouche

Copy link
Copy Markdown
Contributor

Summary

  • Update meta description and opening copy while keeping the existing H1
  • Document vocabulary entry formats (string vs object) and fix pronunciations wording (plain-text variants, not IPA)
  • Add tuning and evaluation guidance with language, API reference, benchmarks, and pricing links

Test plan

  • Preview /chapters/audio-intelligence/custom-vocabulary in mint dev
  • Confirm H1 remains “Custom vocabulary”
  • Check parameter reference, tuning tips, and evaluation links

Clarify phoneme matching vs custom spelling, fix pronunciations wording, and add tuning and evaluation guidance.
@mintlify

mintlify Bot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
gladia 🟢 Ready View Preview Oct 1, 2026, 6:35 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@mfernandez-gladia mfernandez-gladia left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Post-processing / intensity / pronunciations copy is accurate.

This branch was successfully deployed

1 active deployment
staging — 90f19526 Deployed Oct 1, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants