Glossary
Overview
Section titled “Overview”GrowthOS documentation is available in English, Hindi, and Marathi, but a handful of product terms stay in English everywhere so that a support ticket, a screenshot, and a doc page always describe the same thing. This glossary is the canonical list.
The rule is simple: feature and concept names that appear as literal UI labels, such as Idea Lab, PRD, Sprint, Copilot, Planner, and Viewer, are never translated. Everything around those terms, the instructions, explanations, and connecting sentences, is fully localized.
Use this page whenever you are writing a doc, a message to a teammate, or a support reply in Hindi or Marathi and are unsure whether to translate a word. If the word names a specific GrowthOS feature or seat type, keep it in English.
What you can do here
Section titled “What you can do here”- Look up any product term you are unsure how to refer to in a non-English sentence.
- Confirm whether a word is a feature name (keep in English) or a general concept (translate freely).
- Point new hires here before they write their first doc contribution or support message.
When to use
Section titled “When to use”- Translating docs or product copy into Hindi or Marathi.
- Onboarding a multilingual team where terminology needs to stay consistent.
- Writing support replies that mix English feature names with local-language explanations.
Prerequisites
Section titled “Prerequisites”- None; this page is open to everyone.
Where to find it
Section titled “Where to find it”- Getting Started → Glossary in the docs sidebar, in every locale.
Step-by-step
Section titled “Step-by-step”- Scan the glossary table below for the term you need.
- Keep the term itself in English exactly as written in the table.
- Localize the surrounding sentence in whichever language you are writing.
- Prefer this glossary over an ad-hoc translation of a feature name, even if a literal translation exists.
- Suggest an addition to this list if you find a term used inconsistently across docs.
What success looks like
Section titled “What success looks like”- Feature names read identically across the English, Hindi, and Marathi versions of a page.
- A support agent and a customer can refer to the same feature without confusion, regardless of language.
- New docs contributions do not introduce ad-hoc translations of feature names.
Tips & best practices
Section titled “Tips & best practices”- Consistency beats literal translation for UI-aligned terms; a slightly awkward English word in a Hindi sentence is better than a made-up local term nobody recognizes.
- When in doubt, check how the term appears in the actual product UI, not just in older docs.
- Bold the term the first time it appears in a paragraph so readers can spot it quickly.
Common mistakes
Section titled “Common mistakes”- Translating a feature name literally instead of keeping it in English, which breaks search and support matching.
- Using two different translations for the same general concept across different pages.
- Assuming every English word in a sentence is a protected term; only the ones in this list are.