generaltranslation · claude · Jul 21, 2026
diff --git a/authors/archie.mdx b/authors/archie.mdx
@@ -4,7 +4,7 @@ avatar: /static/avatars/archie.png
 occupation: CEO
 company: General Translation
 email: archie@generaltranslation.com
-twitter: https://x.com/archiemckenzie_/photo
+twitter: https://x.com/archiemckenzie_
 linkedin: https://www.linkedin.com/in/archie-mckenzie
 ---
 

diff --git a/authors/default.mdx b/authors/default.mdx
@@ -1,6 +1,7 @@
 ---
 name: Team
 avatar: /static/avatars/logo.png
+occupation: Team
 company: General Translation
 email: archie@generaltranslation.com
 twitter: https://x.com/generaltxn

diff --git a/authors/jackie.mdx b/authors/jackie.mdx
@@ -1,6 +1,7 @@
 ---
 name: Jackie Chen
 avatar: /static/avatars/jackie.png
+occupation: Software Engineer
 company: General Translation
 email: jackie@generaltranslation.com
 twitter: https://x.com/Some_Jackie

diff --git a/blog/en-US/ai-chatbot.mdx b/blog/en-US/ai-chatbot.mdx
@@ -200,7 +200,7 @@ const gt = useGT();
 
 That was it! All of the text in the chatbot was now internationalized and available in any language.
 
-## Deploying to Production
+## Deploying to production
 
 Deploying to production was even easier. I swapped out my `GT_API_KEY` environment variable with a production API key and ran the translate command:
 

diff --git a/blog/en-US/gt-next.mdx b/blog/en-US/gt-next.mdx
@@ -8,7 +8,7 @@ tags: ['guide', 'internationalization', 'nextjs', 'gt-next']
 
 **Internationalization (i18n) sucks. We're building a Next.js library, gt-next, to make it easier.** Today we're launching it in open beta.
 
-``` copy
+```bash copy
 npm i gt-next
 ```
 
@@ -69,7 +69,7 @@ export default function Page() {
 
 #### Use a developer API key to see translations locally
 
-```.env copy
+```env copy
 GT_API_KEY="gtx-dev-cae62d6fe1e33bda603c9a2926ab0fb8"
 GT_PROJECT_ID="abcdef12-3456-789a-bcd4-ef123456789a"
 ```

diff --git a/blog/en-US/i18n-without-translation-files.mdx b/blog/en-US/i18n-without-translation-files.mdx
@@ -6,8 +6,6 @@ authors: [jackie]
 tags: ['guide', 'internationalization', 'nextjs', 'i18n', 'gt-next', 'translation-files', 'developer-experience']
 ---
 
-import Video from '@/components/Video';
-
 Everyone who's internationalized a JavaScript app knows the workflow. You install an i18n library, create an `en.json` file, pull every user-facing string out of your components, assign each one a key, and reference the key where the string used to be. Then you duplicate that JSON file for every language you support. `es.json`, `fr.json`, `ja.json`.
 
 At first, it's fine. Thirty strings, three languages, 90 entries.

diff --git a/blog/en-US/multilingual-nextjs-seo.mdx b/blog/en-US/multilingual-nextjs-seo.mdx
@@ -33,7 +33,7 @@ Search engines need separate, crawlable URLs to index each language version inde
 
 This means **locale-in-the-URL** — not cookies, not query parameters, not `Accept-Language` detection alone.
 
-```
+```text
 ✅ generaltranslation.com/en/about
 ✅ generaltranslation.com/fr/about
 ✅ generaltranslation.com/es/about
@@ -46,7 +46,7 @@ This means **locale-in-the-URL** — not cookies, not query parameters, not `Acc
 
 First, nest your pages under a `[locale]` dynamic segment:
 
-```
+```text
 app/
 └── [locale]/
     ├── layout.tsx
@@ -80,7 +80,6 @@ It's one of the simplest and most impactful things you can do for accessibility
 
 Without it, screen readers guess the language (often wrong), and search engines have less confidence in their language classification.
 
-{/* useLocale works in both client and server rendered components, just not in async components */}
 gt-next provides the `useLocale` hook that makes this trivial in your root layout:
 
 ```tsx title="app/[locale]/layout.tsx"

diff --git a/blog/en-US/plurals.mdx b/blog/en-US/plurals.mdx
@@ -12,7 +12,7 @@ layout: PostLayout
 
 We often encounter apps that display awkward messages like:
 
-```
+```text
 You have 1 new message(s)
 ```
 
@@ -87,7 +87,7 @@ pluralize(2, 'child', 'children') // "children"
 
 But what if you need more complicated logic, like:
 
-```
+```text
 "No one is watching"
 "1 person is watching"
 "2 people are watching"
@@ -168,7 +168,7 @@ languages like Arabic and Polish have more than just these two forms.
 
 For example, an English-speaking user might expect:
 
-```
+```text
 "No one is watching"
 "1 person is watching"
 "2 people are watching"
@@ -177,7 +177,7 @@ For example, an English-speaking user might expect:
 Whereas an Arabic-speaking user might expect different expressions for singular,
 dual (when the count is exactly two things), and small and large plural forms:
 
-```
+```text
 "لا أحد يشاهد"
 "1 شخص يشاهد"
 "2 شخصان يشاهدان"

diff --git a/devlog/en-US/gt-i18n_v0_1_0.mdx b/devlog/en-US/gt-i18n_v0_1_0.mdx
@@ -16,8 +16,8 @@ Though `generaltranslation` is also a runtime-agnostic library, it is—by desig
 
 ## What's Included
 
-- **[`msg()`](#)** - String registration and variable interpolation
-- **[`mFallback()`](#)** and **[`gtFallback()`](#)** - Migration helpers for incremental adoption
+- **`msg()`** - String registration and variable interpolation
+- **`mFallback()`** and **`gtFallback()`** - Migration helpers for incremental adoption
 
 ---
 

diff --git a/devlog/en-US/gt-next_v6_3_0.mdx b/devlog/en-US/gt-next_v6_3_0.mdx
@@ -63,7 +63,7 @@ export default function Page() {
 
 To support interpolation, the `msg()` function returns an encoded message instead of a plain string. The format looks like this:
 
-```
+```text
 <interpolated content>:<base64 encoded string>
 ```
 

diff --git a/devlog/en-US/gt-react_v10_15_0.mdx b/devlog/en-US/gt-react_v10_15_0.mdx
@@ -5,8 +5,6 @@ authors: [ernest]
 tags: ['gt-react', 'derive', 'tagged-template', 'i18n']
 ---
 
-import Video from '@/components/Video';
-
 ## The `declareStatic()` → `derive()` rename
 
 This release is the first to ship with the new `derive()` name. Previously, this function was called `declareStatic()` and the JSX component was `<Static>`. In [PR #1062](https://github.com/generaltranslation/gt/pull/1062), both were renamed to `derive()` and `<Derive>` for clarity.

diff --git a/devlog/en-US/gt-react_v10_18_0.mdx b/devlog/en-US/gt-react_v10_18_0.mdx
@@ -94,7 +94,7 @@ function StatusMessage({ isMasculine }) {
 
 At build time, the CLI sees the `derive()` call and registers two separate source entries, each producing its own translation:
 
-```
+```text
 "I am tired" ($context: "inflect as masculine") → "Estoy cansado"
 "I am tired" ($context: "inflect as feminine")  → "Estoy cansada"
 ```

diff --git a/devlog/en-US/gt-react_v10_19_0.mdx b/devlog/en-US/gt-react_v10_19_0.mdx
@@ -5,8 +5,6 @@ authors: [ernest]
 tags: ['gt-react', 'browser', 'hot-reload', 'dev-experience', 'i18n']
 ---
 
-import Video from '@/components/Video';
-
 <Video src='https://assets.gtx.dev/devlogs/gt-react-browser-tx-hot-reload.mp4' />
 
 ## Overview

diff --git a/devlog/en-US/react-core-linter_v0_1_0.mdx b/devlog/en-US/react-core-linter_v0_1_0.mdx
@@ -11,8 +11,6 @@ tags: ['react-core-linter', '0.1.0', 'eslint', 'linting', 'static-validation']
 
 This plugin catches common implementation errors that we have seen in the wild.
 
-import Video from '@/components/Video';
-
 <Video src='https://assets.gtx.dev/docs/react-core-linter/web-0.1.0.mp4' />
 
 ## Installation

diff --git a/docs/en-US/cli/quickstart.mdx b/docs/en-US/cli/quickstart.mdx
@@ -34,6 +34,7 @@ Use the CLI when you want to:
 - Keep translations in version control alongside your source content.
 
 ## Quickstart [#quickstart]
+
 Install `gt`, configure your project, and run your first translation. You need an existing project with a `package.json` and Node.js installed.
 
 ### 1. Install `gt`

diff --git a/docs/en-US/integrations/mintlify/guides/managing-translations.mdx b/docs/en-US/integrations/mintlify/guides/managing-translations.mdx
@@ -1,6 +1,6 @@
 ---
 
-title: Managing translations 
+title: Managing translations
 description: How to add or remove languages, keep Mintlify translations current, and edit generated translations with General Translation.
 related:
   links:

diff --git a/docs/en-US/platform/core/guides/translating-files.mdx b/docs/en-US/platform/core/guides/translating-files.mdx
@@ -9,7 +9,7 @@ related:
 
 ---
 
-The `generaltranslation` library can translate full source files. This page explains how to upload, enqueue, status, and download workflows for files.
+The `generaltranslation` library can translate full source files. This page explains how to upload, enqueue, check the status of, and download files for translation.
 
 ## Before you start [#before-start]
 

diff --git a/docs/en-US/platform/core/quickstart.mdx b/docs/en-US/platform/core/quickstart.mdx
@@ -1,7 +1,7 @@
 ---
 
 title: Quickstart
-description: Learn what the `generaltranslation` Core library does, when to use it, and how to translate your first string.
+description: Learn what the generaltranslation Core library does, when to use it, and how to translate your first string.
 related:
   links:
     - /docs/platform/core/guides/translating-strings

diff --git a/docs/en-US/platform/core/reference/gt-class/constructor.mdx b/docs/en-US/platform/core/reference/gt-class/constructor.mdx
@@ -49,7 +49,7 @@ The constructor accepts a single optional [`GTConstructorParams`](/docs/platform
 | [`sourceLocale`](#source-locale) | Default source locale for translations. | `string` | Yes | — |
 | [`targetLocale`](#target-locale) | Default target locale for translations. | `string` | Yes | — |
 | [`locales`](#locales) | Supported locale codes. | `string[]` | Yes | — |
-| [`baseUrl`](#base-url) | Custom API base URL for enterprise deployments. | `string` | Yes | — |
+| [`baseUrl`](#base-url) | Custom API base URL for Enterprise deployments. | `string` | Yes | — |
 | [`customMapping`](#custom-mapping) | Custom locale code mappings and property overrides. | [`CustomMapping`](/docs/platform/core/reference/types/custom-mapping) | Yes | — |
 
 ### `apiKey` [#api-key]
@@ -92,7 +92,7 @@ Array of supported locale codes. Each code is standardized to its canonical form
 
 **Type** `string` · **Optional**
 
-Custom API base URL, used for enterprise deployments that point at a self-hosted or region-specific endpoint.
+Custom API base URL, used for Enterprise deployments that point at a self-hosted or region-specific endpoint.
 
 ### `customMapping` [#custom-mapping]
 

diff --git a/docs/en-US/platform/dashboard/guides/adding-translation-context.mdx b/docs/en-US/platform/dashboard/guides/adding-translation-context.mdx
@@ -31,7 +31,7 @@ General Translation applies reusable translation instructions through Context Gr
 
 a) **Glossary** defines **key terms**: product and brand names, features, and technical terms. *Example: Locadex is the GT agent. This product name should never be translated.*
 
-b) **Directives** define **style and tone**: audience, formality, conventions, and formatting. *Example: Use active voice, avoid jargon, and use formal “sie”*
+b) **Directives** define **style and tone**: audience, formality, conventions, and formatting. *Example: Use active voice, avoid jargon, and use formal “Sie”*
 
 All Context Groups are stored at the Organization-wide level. They can then be applied to one or more Projects.
 
@@ -97,7 +97,7 @@ When you create a Context Group from a Project, it is still created at the Organ
 
 In most cases, you should directly assign or reassign Projects to Context Groups.
 
-However, for major changes, you can also use **Export** to download a group's Glossary and Directives. Then use **Import** to fill an empty Glossary and Directive fields from a supported file. 
+However, for major changes, you can also use **Export** to download a group's Glossary and Directives. Then use **Import** to fill empty Glossary and Directive fields from a supported file.
 
 ## Set priority when groups overlap [#priority]
 

diff --git a/docs/en-US/platform/dashboard/reference/project-settings.mdx b/docs/en-US/platform/dashboard/reference/project-settings.mdx
@@ -1,6 +1,8 @@
 ---
+
 title: "Project settings"
 description: "Project settings control how an individual Project appears and how its translations are delivered."
+
 ---
 
 Each Project in the Dashboard has its own settings, separate from Organization-wide settings. Use them to rename the Project, change its source locale, enable CDN delivery or AI Context, copy the Project ID, and delete the Project.

diff --git a/docs/en-US/platform/locadex/guides/auto-merging-prs.mdx b/docs/en-US/platform/locadex/guides/auto-merging-prs.mdx
@@ -46,7 +46,7 @@ This is useful when your team reviews or edits generated translations in the Das
 
 ## Add validation commands [#add-validation-commands]
 
-If Locadex should run a build, lint, or test command before creating the pull request, add a **post-process command**. (Pre-process commands run before Locadex processes files, post-process commands run after Locadex processes files).
+If Locadex should run a build, lint, or test command before creating the pull request, add a **post-process command**. (Pre-process commands run before Locadex processes files; post-process commands run after Locadex processes files.)
 
 For example:
 

diff --git a/docs/en-US/platform/locadex/guides/configuring-workflows.mdx b/docs/en-US/platform/locadex/guides/configuring-workflows.mdx
@@ -54,7 +54,7 @@ Use a stable prefix so Locadex branches are easy to find in GitHub.
 
 Use the toggle buttons to control how Locadex creates and manages pull requests:
 
-- **Auto-merge PRs** merges Locadex pull requests automatically when checks pass. See more information at [Auto-merge Locadex PRs.](/docs/platform/locadex/guides/auto-merging-prs)
+- **Auto-merge PRs** merges Locadex pull requests automatically when checks pass. See more information at [Auto-merge Locadex PRs](/docs/platform/locadex/guides/auto-merging-prs).
 - **Run on exact content changes** narrows Locadex’s relevance check for the Codegen workflow. When enabled, Locadex checks only the changed lines in the diff. When disabled, it may check the full modified file. This setting does not affect the Translation or Locales workflows.
 - **Save local edits** preserves manual translation edits before Locadex runs.
 
@@ -68,7 +68,7 @@ The text boxes at the bottom of the page provide additional customizability:
 Use commands to run steps such as setup or validation on your Project. Use commands to install dependencies, build your Project, lint generated changes, or run Project-specific checks. Commands can be run before or after Locadex processes files:
 
 - **Pre-process command** runs before Locadex processes files. For example, run `npm run build`.
-- **Post-process command** runs after Locadex processes files. For example, run `npm run typecheck` .
+- **Post-process command** runs after Locadex processes files. For example, run `npm run typecheck`.
 
 Commands run from the repository root and inside the [Locadex VM image](/docs/platform/locadex/reference/vm-image). If a workflow fails because a package, script, or binary is missing, add a pre-process command.
 

diff --git a/docs/en-US/platform/locadex/guides/managing-languages.mdx b/docs/en-US/platform/locadex/guides/managing-languages.mdx
@@ -23,7 +23,7 @@ Choose or edit the language your source content is written in. Most English Proj
 
 ## Choose target languages [#choose-target-languages]
 
-Choose the languages Locadex should translate into. You can select target languages from all 120 General Translation supported locales. Read more about locales at [Understanding locale codes](/docs/platform/core/guides/locale-codes) and [General Translation supported locales.](/docs/platform/dashboard/reference/supported-locales)
+Choose the languages Locadex should translate into. You can select target languages from all 120 General Translation supported locales. Read more about locales at [Understanding locale codes](/docs/platform/core/guides/locale-codes) and [General Translation supported locales](/docs/platform/dashboard/reference/supported-locales).
 
 ## Save changes [#save-changes]
 

diff --git a/docs/en-US/python/reference/functions/extract-variables.mdx b/docs/en-US/python/reference/functions/extract-variables.mdx
@@ -1,7 +1,7 @@
 ---
 
 title: extract_variables
-description: Filter reserved GT keys from an options dict to get user variables in General Translation Python. API reference for extract_variables.
+description: Filter reserved General Translation keys from an options dict to get user variables in General Translation Python. API reference for extract_variables.
 
 ---
 

diff --git a/docs/en-US/react/guides/configuring.mdx b/docs/en-US/react/guides/configuring.mdx
@@ -8,6 +8,7 @@ related:
     - /docs/react/guides/translating-strings
     - /docs/react/guides/managing-locales
     - /docs/react/guides/storing-translations
+
 ---
 
 Server-rendered React and each framework integration need configuration plus a `GTProvider` that exposes translations to your components. React SPAs initialize directly with `initializeGTSPA`; follow the [React SPA Quickstart](/docs/react/react-spa-quickstart) for that setup.

diff --git a/docs/en-US/react/nextjs-pages-router-quickstart.mdx b/docs/en-US/react/nextjs-pages-router-quickstart.mdx
@@ -235,7 +235,7 @@ To see translations in development, you need API keys from General Translation.
 Create a **`.env.local`** file:
 
 ```bash title=".env.local"
-GT_API_KEY="your-api-key"
+GT_DEV_API_KEY="your-dev-api-key"
 GT_PROJECT_ID="your-project-id"
 ```
 

diff --git a/docs/en-US/react/nextjs-quickstart.mdx b/docs/en-US/react/nextjs-quickstart.mdx
@@ -197,7 +197,7 @@ To see translations in development, you need API keys from General Translation.
 Create a **`.env.local`** file:
 
 ```bash title=".env.local"
-GT_API_KEY="your-api-key"
+GT_DEV_API_KEY="your-dev-api-key"
 GT_PROJECT_ID="your-project-id"
 ```
 
@@ -335,12 +335,12 @@ That's it — your app is now multilingual. 🎉
     This is expected. In development, translations happen on-demand (your content is translated in real time via the API). This delay **does not exist in production** — all translations are pre-generated by `npx gt translate`.
   </Accordion>
   <Accordion title="Some translations are inaccurate">
-    Ambiguous text can lead to inaccurate translations. For example, "apple" could mean the fruit or the company. Add a `context` prop to help:
+    Ambiguous text can lead to inaccurate translations. For example, "apple" could mean the fruit or the company. Add a `$context` prop to help:
 
     ```jsx
-    <T context="the technology company">Apple</T>
+    <T $context="the technology company">Apple</T>
     ```
 
-    Both `<T>`, `useGT()`, and `getGT()` support the `context` option.
+    `<T>`, `useGT()`, and `getGT()` all support the `$context` option.
   </Accordion>
 </Accordions>
diff --git a/docs/en-US/react/reference/lint-rules.mdx b/docs/en-US/react/reference/lint-rules.mdx
@@ -13,7 +13,7 @@ The General Translation React Core linter (`@generaltranslation/react-core-linte
 
 | Rule | What it flags | Auto-fix |
 | --- | --- | --- |
-| [`static-string`](#static-string) | Dynamic or non-static strings passed to translation functions ([`useGT`](/docs/react/reference/hooks/use-gt), [`getGT`](/docs/node/reference/functions/get-gt), [`msg`](/docs/react/reference/functions/msg)), and non-static sugar variables. | Yes |
+| [`static-string`](#static-string) | Dynamic or non-static strings passed to translation functions ([`useGT`](/docs/react/reference/hooks/use-gt), [`getGT`](/docs/react/nextjs/reference/functions/get-gt), [`msg`](/docs/react/reference/functions/msg)), and non-static sugar variables. | Yes |
 | [`static-jsx`](#static-jsx) | Dynamic content inside [`<T>`](/docs/react/reference/components/t) that is not wrapped in a variable component. | Yes |
 | [`no-data-attrs-on-branch`](#no-data-attrs) | `data-*` attributes on [`<Branch>`](/docs/react/reference/components/branch), which the component ignores. | No |
-Original file line number
+Diff line change
@@ Expand Up / @@ -63,7 +63,7 @@ export default function Page() { @@
     To support interpolation, the `msg()` function returns an encoded message instead of a plain string. The format looks like this:
-    ```
+    ```text
     <interpolated content>:<base64 encoded string>
     ```
@@ Expand Down @@