generaltranslation · moss-bryophyta · Jun 17, 2026
diff --git a/docs/en-US/cli/faqs.mdx b/docs/en-US/cli/faqs.mdx
@@ -11,7 +11,7 @@ The [`translate`](/docs/cli/translate) command requires a production API key, wh
 
 Run it in your CI/CD pipeline **before** building your app for production. It should not be used during development — in development, use development API keys for on-demand translation instead.
 
-### Can I use the CLI with libraries other than gt-next and gt-react?
+### Can I use the CLI with libraries other than `gt-next` and `gt-react`?
 
 Yes. The CLI can generate translations for third-party i18n libraries like [next-intl](https://next-intl.dev/) and [i18next](https://react.i18next.com/). It can also translate standalone JSON, Markdown, MDX, JS, and TS files.
 

diff --git a/docs/en-US/cli/formats/gt.mdx b/docs/en-US/cli/formats/gt.mdx
@@ -9,7 +9,7 @@ This tutorial will show you how to automatically manage your project's translati
 
 <Callout type='warn'>
   **Note:** This should only be used when you are shipping a production build.
-  If you are using gt-next, gt-react, or gt-react-native in development, this
+  If you are using `gt-next`, `gt-react`, or `gt-react-native` in development, this
   command is not needed.
 </Callout>
 

diff --git a/docs/en-US/locadex/next.mdx b/docs/en-US/locadex/next.mdx
@@ -12,7 +12,7 @@ It takes 5 minutes to install.
 
 Locadex:
 
-- Configures your project to use the gt-next i18n library
+- Configures your project to use the `gt-next` i18n library
 - Modifies your React components and strings to support multilingual content
 - Translates your app into as many languages as you need
 - Continuously internationalizes and translates as you push new content

diff --git a/docs/en-US/next-lint/index.mdx b/docs/en-US/next-lint/index.mdx
@@ -7,7 +7,7 @@ description: ESLint plugin for gt-next components.
   This is in alpha. Subject to changes.
 </Callout>
 
-ESLint plugin that catches common translation errors in gt-next components.
+ESLint plugin that catches common translation errors in `gt-next` components.
 
 ## Installation
 

diff --git a/docs/en-US/next/concepts/compiler.mdx b/docs/en-US/next/concepts/compiler.mdx
@@ -3,7 +3,7 @@ title: Compiler
 description: gt-next's Rust-based SWC plugin
 ---
 
-gt-next includes a Rust-based SWC plugin that performs build-time analysis to catch common translation errors and optimize performance.
+`gt-next` includes a Rust-based SWC plugin that performs build-time analysis to catch common translation errors and optimize performance.
 
 ## Features
 

diff --git a/docs/en-US/next/faqs.mdx b/docs/en-US/next/faqs.mdx
@@ -5,7 +5,7 @@ description: Frequently asked questions about gt-next
 
 ### What happens if there are missing translations in production?
 
-If a translation for some content is missing in production, gt-next automatically falls back to the original source text. Your app will still render correctly — users will just see the default language for that piece of content.
+If a translation for some content is missing in production, `gt-next` automatically falls back to the original source text. Your app will still render correctly — users will just see the default language for that piece of content.
 
 ### Why do I have to install the CLI tool?
 
@@ -30,7 +30,7 @@ In production, `<T>` won't do this, so your API keys are never exposed to the cl
 
 The `<T>` component doesn't support translating dynamic content and variables directly, because the translations could potentially change with every re-render. However, you can still include dynamic content inside a `<T>` by wrapping it with `<Var>`, `<DateTime>`, or `<Currency>` components. This is similar to how other libraries handle string interpolation.
 
-gt-next also has a [`<Tx>`](/docs/next/api/components/tx) server-side component which translates content at runtime and supports dynamic content, but it requires an API key.
+`gt-next` also has a [`<Tx>`](/docs/next/api/components/tx) server-side component which translates content at runtime and supports dynamic content, but it requires an API key.
 
 ### Can I deploy my app without depending on GT servers?
 

diff --git a/docs/en-US/next/guides/cache-components.mdx b/docs/en-US/next/guides/cache-components.mdx
@@ -3,7 +3,7 @@ title: Cache Components
 description: Setting up Cache Components in gt-next
 ---
 
-This guide shows how to use gt-next with Next.js Cache Components to optimize internationalized applications.
+This guide shows how to use `gt-next` with Next.js Cache Components to optimize internationalized applications.
 
 ---
 
@@ -15,7 +15,7 @@ If you have not already, follow the [Next.js Cache Components guide](https://nex
   <Step>
   ### Enable cache components and configure request functions
 
-Enable cache components in your Next.js config, and define custom `getLocale` and `getRegion` request functions that use `next/root-params` so that gt-next can resolve the locale inside cached components.
+Enable cache components in your Next.js config, and define custom `getLocale` and `getRegion` request functions that use `next/root-params` so that `gt-next` can resolve the locale inside cached components.
 
 <Callout type='warn'>
 Your `[locale]` segment must be a **root parameter** — the first dynamic segment in your app directory, with no `app/layout.tsx` above it. Your root layout must live inside `app/[locale]/`.

diff --git a/docs/en-US/next/index.mdx b/docs/en-US/next/index.mdx
@@ -206,7 +206,7 @@ npx gt auth
 </Callout>
 
 <Accordions>
-  <Accordion title="Can I use gt-next without API keys?">
+  <Accordion title="Can I use `gt-next` without API keys?">
     Yes. Without API keys, `gt-next` works as a standard i18n library. You won't get on-demand translation in development, but you can still:
     - Provide your own translation files manually
     - Use all components (`<T>`, `<Var>`, `LocaleSelector`, etc.)

diff --git a/docs/en-US/react-native/faqs.mdx b/docs/en-US/react-native/faqs.mdx
@@ -5,7 +5,7 @@ description: Frequently asked questions about gt-react-native
 
 ### What happens if there are missing translations in production?
 
-If a translation for some content is missing in production, gt-react-native automatically falls back to the original source text. Your app will still render correctly — users will just see the default language for that piece of content.
+If a translation for some content is missing in production, `gt-react-native` automatically falls back to the original source text. Your app will still render correctly — users will just see the default language for that piece of content.
 
 ### Why do I have to install the CLI tool?
 

diff --git a/docs/en-US/react-native/tutorials/quickstart-expo.mdx b/docs/en-US/react-native/tutorials/quickstart-expo.mdx
@@ -262,7 +262,7 @@ npx gt auth
 </Callout>
 
 <Accordions>
-  <Accordion title="Can I use gt-react-native without API keys?">
+  <Accordion title="Can I use `gt-react-native` without API keys?">
     Yes. Without API keys, `gt-react-native` works as a standard i18n library. You won't get on-demand translation in development, but you can still:
     - Provide your own translation files manually
     - Use all components (`<T>`, `<Var>`, `LocaleSelector`, etc.)

diff --git a/docs/en-US/react-native/tutorials/quickstart.mdx b/docs/en-US/react-native/tutorials/quickstart.mdx
@@ -259,7 +259,7 @@ npx gt auth
 </Callout>
 
 <Accordions>
-  <Accordion title="Can I use gt-react-native without API keys?">
+  <Accordion title="Can I use `gt-react-native` without API keys?">
     Yes. Without API keys, `gt-react-native` works as a standard i18n library. You won't get on-demand translation in development, but you can still:
     - Provide your own translation files manually
     - Use all components (`<T>`, `<Var>`, `LocaleSelector`, etc.)

diff --git a/docs/en-US/react/faqs.mdx b/docs/en-US/react/faqs.mdx
@@ -5,7 +5,7 @@ description: Frequently asked questions about gt-react
 
 ### What happens if there are missing translations in production?
 
-If a translation for some content is missing in production, gt-react automatically falls back to the original source text. Your app will still render correctly — users will just see the default language for that piece of content.
+If a translation for some content is missing in production, `gt-react` automatically falls back to the original source text. Your app will still render correctly — users will just see the default language for that piece of content.
 
 ### Why do I have to install the CLI tool?
 

diff --git a/docs/en-US/react/index.mdx b/docs/en-US/react/index.mdx
@@ -256,7 +256,7 @@ npx gt auth
 </Callout>
 
 <Accordions>
-  <Accordion title="Can I use gt-react without API keys?">
+  <Accordion title="Can I use `gt-react` without API keys?">
     Yes. Without API keys, `gt-react` works as a standard i18n library. You won't get on-demand translation in development, but you can still:
     - Provide your own translation files manually
     - Use all components (`<T>`, `<Var>`, `LocaleSelector`, etc.)