dify-docs-terminology-check

Terminology drift happens when documentation terms fall out of sync with product UI labels. You can catch terminology drift by running a full-file audit that compares doc content against the official glossary and codebase i18n sources, ensuring wording stays aligned with the live interface.

Yes, translation validation supports English, Chinese, and Japanese documentation. The audit compares translated content against approved glossary terms and product UI labels to ensure wording remains consistent across localized feature guides.

The best way to find missing or outdated terms is to perform a glossary gap reporting audit. This process reviews documentation content against the source of truth in the codebase, identifying missing, outdated, or renamed terms that require glossary updates.

No, the terminology audit explicitly excludes environment variable documentation. It focuses on verifying glossary terms, bolded UI elements, and feature headings in standard documentation files rather than environment configuration guides.

You can audit docs against a specific Dify codebase branch by running a branch-specific terminology check. This compares the documentation's bolded UI terms and feature headings against the i18n sources checked out from the target branch.