From 5d17aa3ea8e89f8a3bb482a1e7b6a6d5509be2ea Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Tue, 14 Jul 2026 15:20:30 +0000
Subject: [PATCH] Fix docs CI hard-fails, broken links, and prose typos

- Remove stray `import Video from '@/components/Video'` statements (CI
  hard-fail: bare import in MDX body); <Video> is globally provided, as
  proven by existing usage elsewhere without any import.
- Add missing code-fence language ids across several blog/devlog posts.
- Fix broken/mislinked API references (getGT pointing at the useGT page,
  dictionary `d` references that should read `t`), a duplicated list
  number, an inverted prefixDefaultLocale example, and other prose bugs
  (typos, dangling sentences, subject-verb agreement, "fallback" used as
  a verb, dangling empty sections).
- Fill in missing/malformed author frontmatter fields.
---
 authors/archie.mdx                                          | 2 +-
 authors/default.mdx                                         | 1 +
 authors/jackie.mdx                                          | 1 +
 blog/en-US/gt-next.mdx                                      | 2 +-
 blog/en-US/i18n-without-translation-files.mdx               | 2 --
 blog/en-US/multilingual-nextjs-seo.mdx                      | 4 ++--
 blog/en-US/plurals.mdx                                      | 6 +++---
 devlog/en-US/gt-next_v6_10_0.mdx                            | 2 +-
 devlog/en-US/gt-next_v6_2_0.mdx                             | 4 ++--
 devlog/en-US/gt-next_v6_3_0.mdx                             | 2 +-
 devlog/en-US/gt-react_v10_15_0.mdx                          | 2 --
 devlog/en-US/gt-react_v10_18_0.mdx                          | 2 +-
 devlog/en-US/gt-react_v10_19_0.mdx                          | 2 --
 devlog/en-US/react-core-linter_v0_1_0.mdx                   | 2 --
 docs/en-US/core/index.mdx                                   | 2 --
 docs/en-US/core/locales.mdx                                 | 2 +-
 docs/en-US/locadex/next.mdx                                 | 2 --
 docs/en-US/next/api/components/t.mdx                        | 2 +-
 docs/en-US/next/api/components/tx.mdx                       | 4 ++--
 docs/en-US/next/api/config/with-gt-config.mdx               | 2 +-
 docs/en-US/next/api/dictionary/use-translations.mdx         | 6 +++---
 docs/en-US/next/api/helpers/get-locale.mdx                  | 4 ++--
 docs/en-US/next/api/middleware/create-next-middleware.mdx   | 4 +---
 docs/en-US/next/api/strings/get-gt.mdx                      | 4 ++--
 docs/en-US/next/api/strings/get-messages.mdx                | 4 ++--
 docs/en-US/next/api/strings/tx.mdx                          | 4 ++--
 .../en-US/next/api/types/dictionary-translation-options.mdx | 4 ++--
 docs/en-US/next/concepts/environments.mdx                   | 2 +-
 docs/en-US/next/guides/local-tx.mdx                         | 1 -
 docs/en-US/next/guides/migration.mdx                        | 2 +-
 docs/en-US/next/index.mdx                                   | 2 +-
 docs/en-US/next/tutorials/examples/next-speedrun.mdx        | 2 +-
 docs/en-US/overview/faqs.mdx                                | 2 +-
 docs/en-US/react-core-linter/guides/quickstart.mdx          | 2 --
 docs/en-US/react-core-linter/index.mdx                      | 2 --
 docs/en-US/react-core-linter/rules/static-string.mdx        | 2 +-
 docs/en-US/react/api/components/gtprovider.mdx              | 2 +-
 37 files changed, 40 insertions(+), 57 deletions(-)

diff --git a/authors/archie.mdx b/authors/archie.mdx
index b64acf16..b4504c22 100644
--- 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
index ea49a632..1b003778 100644
--- 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
index 2ac16548..c99d0722 100644
--- 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/gt-next.mdx b/blog/en-US/gt-next.mdx
index 4f30479e..eeaa8ea9 100644
--- 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
 ```
 
diff --git a/blog/en-US/i18n-without-translation-files.mdx b/blog/en-US/i18n-without-translation-files.mdx
index 0be9ae2d..d7af7a33 100644
--- 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
index b019428a..1ac2d899 100644
--- 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
diff --git a/blog/en-US/plurals.mdx b/blog/en-US/plurals.mdx
index 02b1af42..5ce90c5c 100644
--- 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)
 ```
 
@@ -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-next_v6_10_0.mdx b/devlog/en-US/gt-next_v6_10_0.mdx
index 4cc7d094..d55f7a44 100644
--- a/devlog/en-US/gt-next_v6_10_0.mdx
+++ b/devlog/en-US/gt-next_v6_10_0.mdx
@@ -54,7 +54,7 @@ Cached components use their parameters as cache keys, any cached component that
 
 When `experimentalLocaleResolution` is enabled:
 - I18n proxy must be enabled for locale resolution to work (see [I18n Proxy](/docs/next/guides/middleware))
-- It overrides any custom `getLocale` functions (locale resolution happens from the reading the URL path)
+- It overrides any custom `getLocale` functions (locale resolution happens from reading the URL path)
 - It disables `getRegion` and `getDomain` functions
 - It conflicts with the deprecated `experimentalEnableSSG` configuration - only one can be enabled at a time
 - You can customize the locale parameter name with `experimentalLocaleResolutionParam` (defaults to `'locale'`)
diff --git a/devlog/en-US/gt-next_v6_2_0.mdx b/devlog/en-US/gt-next_v6_2_0.mdx
index 44172874..048ea331 100644
--- a/devlog/en-US/gt-next_v6_2_0.mdx
+++ b/devlog/en-US/gt-next_v6_2_0.mdx
@@ -48,8 +48,8 @@ export default function Page() {
 We deliberately kept `gt()` synchronous to match other i18n libraries.
 The downside was a `two-step translation process`:
 
-    1.	Register the text with the API.
-    2.	Wait for a second render to display the translated result.
+1. Register the text with the API.
+2. Wait for a second render to display the translated result.
 
 Now, thanks to the compiler, translatable content is scanned ahead of time and passed directly into `useGT()` or `getGT()` at compile time.
 This means translations are immediately available at runtime — no page refreshes.
diff --git a/devlog/en-US/gt-next_v6_3_0.mdx b/devlog/en-US/gt-next_v6_3_0.mdx
index ce7567e9..9ea11079 100644
--- 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
index c54b98b2..6fb6daf6 100644
--- 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
index 397ef4ab..7fde2e46 100644
--- 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
index 398a1267..f7e37e85 100644
--- 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
index 22baaa2c..65f77a7e 100644
--- 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/core/index.mdx b/docs/en-US/core/index.mdx
index 4d76d69f..45bb187f 100644
--- a/docs/en-US/core/index.mdx
+++ b/docs/en-US/core/index.mdx
@@ -8,8 +8,6 @@ description: Overview of the generaltranslation library
 The `generaltranslation` library serves as GT's core i18n library housing utility functions and classes for translation and formatting.
 It is often used with framework packages like `gt-next` and `gt-react`, but can be used as a standalone library.
 
-import Video from '@/components/Video';
-
 <Video src='https://assets.gtx.dev/core-demo.mp4' />
 
 ```typescript title="index.ts"
diff --git a/docs/en-US/core/locales.mdx b/docs/en-US/core/locales.mdx
index 284ad8ef..60c6c563 100644
--- a/docs/en-US/core/locales.mdx
+++ b/docs/en-US/core/locales.mdx
@@ -42,7 +42,7 @@ Together, `zh-Hant-HK` means "Chinese, written in traditional characters, as spo
 See the [list of supported locales](/docs/platform/supported-locales) for a searchable list of all locales currently supported by General Translation.
 
 Technically, the library supports any validly constructed tag, including private use codes with no widely recognized meaning. 
-However, the platform will only translate
+However, the platform will only translate into locales that are officially supported.
 
 ### Equivalent locale tags
 
diff --git a/docs/en-US/locadex/next.mdx b/docs/en-US/locadex/next.mdx
index 1f3e3ea0..ca614b9a 100644
--- a/docs/en-US/locadex/next.mdx
+++ b/docs/en-US/locadex/next.mdx
@@ -8,8 +8,6 @@ Translating your Next.js app into French 🇫🇷, Spanish 🇪🇸, Japanese 
 **Locadex is an AI agent built to handle 100% of the internationalization (i18n) work for you.**
 It takes 5 minutes to install.
 
-{/* ![Installation screen for Locadex](/images/screenshots/locadex-install.png) */}
-
 Locadex:
 
 - Configures your project to use the gt-next i18n library
diff --git a/docs/en-US/next/api/components/t.mdx b/docs/en-US/next/api/components/t.mdx
index 16b13610..51a03697 100644
--- a/docs/en-US/next/api/components/t.mdx
+++ b/docs/en-US/next/api/components/t.mdx
@@ -80,7 +80,7 @@ This ensures fast load times for all locales, but it can only translate content
 
 Once generated, translations are either (1) stored in the CDN or (2) stored in your app's build output, according to your configuration.
 From there, the translated content is served to your users.
-If a translation is not found, it will fallback to the original content.
+If a translation is not found, it will fall back to the original content.
 
 Make sure to follow the [deployment guide here](/docs/next/tutorials/quickdeploy).
 
diff --git a/docs/en-US/next/api/components/tx.mdx b/docs/en-US/next/api/components/tx.mdx
index 9e8c23ad..1ac4bfb8 100644
--- a/docs/en-US/next/api/components/tx.mdx
+++ b/docs/en-US/next/api/components/tx.mdx
@@ -71,12 +71,12 @@ This means translation will be performed live.
 
 `<Tx>` translates jsx at runtime.
 This means that translations are performed live, so you can translate content that is only known at runtime.
-The trade off is that there is a delay while waiting for an on-demand translation to load is significantly slower.
+The trade off is that on-demand translation is significantly slower, since there is a delay while waiting for the translation to load.
 
 While loading, `<Tx>` will return undefined unless languages are similar (en-US vs en-GB), though this behavior can be customized with render settings.
 If an error occurs, `<Tx>` will return the original content.
 
-Our advice is to translate everything you can at build time using [`<T>`](/docs/next/api/components/t), [`getGT`](/docs/next/api/strings/use-gt), or [`useGT`](/docs/next/api/strings/use-gt),
+Our advice is to translate everything you can at build time using [`<T>`](/docs/next/api/components/t), [`getGT`](/docs/next/api/strings/get-gt), or [`useGT`](/docs/next/api/strings/use-gt),
 and only use on-demand translations, like `<Tx>` and [`tx`](/docs/next/api/strings/tx) when necessary.
 
 Make sure to follow the [deployment guide here](/docs/next/tutorials/quickdeploy).
diff --git a/docs/en-US/next/api/config/with-gt-config.mdx b/docs/en-US/next/api/config/with-gt-config.mdx
index 16ed49f0..3b99f617 100644
--- a/docs/en-US/next/api/config/with-gt-config.mdx
+++ b/docs/en-US/next/api/config/with-gt-config.mdx
@@ -24,7 +24,7 @@ export default withGTConfig(nextConfig, {
 **Legacy**
 
 `initGT` is the legacy way to configure the `gt-next` library. It returns a function callback which is then called on the `NextConfig` object.
-The props for both functions are the same, with the exception that `withGTProps` requires `NextConfig` to also be passed in.
+The props for both functions are the same, with the exception that `withGTConfig` requires `NextConfig` to also be passed in.
 </Callout>
 
 Use `withGTConfig` to:
diff --git a/docs/en-US/next/api/dictionary/use-translations.mdx b/docs/en-US/next/api/dictionary/use-translations.mdx
index 26e75d34..8ce27a94 100644
--- a/docs/en-US/next/api/dictionary/use-translations.mdx
+++ b/docs/en-US/next/api/dictionary/use-translations.mdx
@@ -44,7 +44,7 @@ For async components, see [`getTranslations`](/docs/next/api/dictionary/get-tran
 
 ### Returns
 
-A translation function `d` that, given an id, will return the translated version of the corresponding entry
+A translation function `t` that, given an id, will return the translated version of the corresponding entry
 
 ```jsx
 (id: string, options?: DictionaryTranslationOptions) => string
@@ -53,7 +53,7 @@ A translation function `d` that, given an id, will return the translated version
 | Name                  | Type | Description                                                                 |
 |-----------------------|--|-----------------------------------------------------------------------------|
 | `id`             | `string` | The id of the entry to be translated                                     |
-| `options?`            | [`DictionaryTranslationOptions`](/docs/next/api/types/dictionary-translation-options) | Translation options to customize the behavior of `d`. |
+| `options?`            | [`DictionaryTranslationOptions`](/docs/next/api/types/dictionary-translation-options) | Translation options to customize the behavior of `t`. |
 
 ---
 
@@ -86,7 +86,7 @@ export default async function TranslateGreeting() {
 ```
 
 ### Using variables [#variables]
-In order to pass values, you must (1) assign an identifier and (2) reference the identifier when calling the `d` function.
+In order to pass values, you must (1) assign an identifier and (2) reference the identifier when calling the `t` function.
 
 In this example, we use `{}` to pass variables to the translations.
 In the dictionary, we assign identifier `{userName}`.
diff --git a/docs/en-US/next/api/helpers/get-locale.mdx b/docs/en-US/next/api/helpers/get-locale.mdx
index 747e26cf..388ce91d 100644
--- a/docs/en-US/next/api/helpers/get-locale.mdx
+++ b/docs/en-US/next/api/helpers/get-locale.mdx
@@ -30,11 +30,11 @@ When an unsupported locale is requested, a fallback locale will be selected.
 For instance, in the event of an unsupported locale,
 if (1) the user has configured multiple preferred locales in their browser settings,
 and (2) one of these locales is supported by your application,
-then the locale will fallback to the best language.
+then the locale will fall back to the best language.
 
 Additionally, if no possible fallback locales are available,
 but two locales share the same language (e.g., `en-US` and `en-GB`),
-then the locale will fallback to the supported locale that shares the same language.
+then the locale will fall back to the supported locale that shares the same language.
 
 If neither condition can be met, then the default locale will be used.
 
diff --git a/docs/en-US/next/api/middleware/create-next-middleware.mdx b/docs/en-US/next/api/middleware/create-next-middleware.mdx
index 9b59791d..f89d13ae 100644
--- a/docs/en-US/next/api/middleware/create-next-middleware.mdx
+++ b/docs/en-US/next/api/middleware/create-next-middleware.mdx
@@ -100,7 +100,7 @@ You can remove the default locale prefix by setting the `prefixDefaultLocale` op
 
 ```js title="proxy.ts" copy
 export default createNextMiddleware({
-  prefixDefaultLocale: true,
+  prefixDefaultLocale: false,
 });
 ```
 
@@ -111,5 +111,3 @@ If you set this to `false` (which is the default), then only the default locale
 
 ## Notes
  * The `createNextMiddleware` function is a utility function that creates a proxy/middleware function for use with Next.js. Place it in `proxy.ts` in your project root.
-
-## Next steps
diff --git a/docs/en-US/next/api/strings/get-gt.mdx b/docs/en-US/next/api/strings/get-gt.mdx
index b4b12ac4..1db5f5ea 100644
--- a/docs/en-US/next/api/strings/get-gt.mdx
+++ b/docs/en-US/next/api/strings/get-gt.mdx
@@ -47,7 +47,7 @@ This ensures fast load times for all locales, but it can only translate content
 
 Once generated, translations are either (1) stored in the CDN or (2) stored in your app's build output, according to your configuration.
 From there, the translated content is served to your users.
-If a translation is not found, it will fallback to the original content.
+If a translation is not found, it will fall back to the original content.
 
 Make sure to follow the [deployment guide here](/docs/next/tutorials/quickdeploy).
 
@@ -148,7 +148,7 @@ export default async function TranslateGreeting() {
 
 ## Notes
  * The `getGT` function is a server-side function that translates strings.
- * Translations strings with `getGT` happen before runtime, during the build process (unless in development).
+ * Translation strings with `getGT` happen before runtime, during the build process (unless in development).
 
 ## Next steps
  * See [`useGT`](/docs/next/api/strings/use-gt) for client-side string translations at buildtime.
diff --git a/docs/en-US/next/api/strings/get-messages.mdx b/docs/en-US/next/api/strings/get-messages.mdx
index d4355fe0..499f1569 100644
--- a/docs/en-US/next/api/strings/get-messages.mdx
+++ b/docs/en-US/next/api/strings/get-messages.mdx
@@ -47,7 +47,7 @@ This ensures fast load times for all locales, but it can only translate content
 
 Once generated, translations are either (1) stored in the CDN or (2) stored in your app's build output, according to your configuration.
 From there, the translated content is served to your users.
-If a translation is not found, it will fallback to the original content.
+If a translation is not found, it will fall back to the original content.
 
 Make sure to follow the [deployment guide here](/docs/next/tutorials/quickdeploy).
 
@@ -152,7 +152,7 @@ export default async function TranslateGreeting() {
 
 ## Notes
  * The `getMessages` function is a server-side function that translates encoded strings from `msg`.
- * Translations strings with `getMessages` happen before runtime, during the build process (unless in development).
+ * Translation strings with `getMessages` happen before runtime, during the build process (unless in development).
 
 ## Next steps
  * See [`useMessages`](/docs/next/api/strings/use-messages) for client-side string translations from encoded strings at buildtime.
diff --git a/docs/en-US/next/api/strings/tx.mdx b/docs/en-US/next/api/strings/tx.mdx
index 2f00e28d..a50fca5a 100644
--- a/docs/en-US/next/api/strings/tx.mdx
+++ b/docs/en-US/next/api/strings/tx.mdx
@@ -52,9 +52,9 @@ A promise that resolves to a string containing the translated content, or the or
 
 The `tx` function translates strings at runtime.
 This means that translations are performed live, so you can translate content that is only known at runtime.
-The trade off is that there is a delay while waiting for an on-demand translation to load is significantly slower.
+The trade off is that on-demand translation is significantly slower, since there is a delay while waiting for the translation to load.
 
-Our advice is to translate everything you can at build time using [`getGT`](/docs/next/api/strings/use-gt), [`useGT`](/docs/next/api/strings/use-gt), or [`<T>`](/docs/next/api/components/t),
+Our advice is to translate everything you can at build time using [`getGT`](/docs/next/api/strings/get-gt), [`useGT`](/docs/next/api/strings/use-gt), or [`<T>`](/docs/next/api/components/t),
 and only use on-demand translations, like `tx` and [`<Tx>`](/docs/next/api/components/tx), when necessary.
 
 Make sure to follow the [deployment guide here](/docs/next/tutorials/quickdeploy).
diff --git a/docs/en-US/next/api/types/dictionary-translation-options.mdx b/docs/en-US/next/api/types/dictionary-translation-options.mdx
index 97d8336c..93e5c374 100644
--- a/docs/en-US/next/api/types/dictionary-translation-options.mdx
+++ b/docs/en-US/next/api/types/dictionary-translation-options.mdx
@@ -44,7 +44,7 @@ See [`tx`](/docs/next/api/strings/tx) for translating strings with dynamic conte
 
 ### Passing variables
 
-In order to pass a variable to the dictionary entry, we need to do two things: (1) add a variable to the entry and (2) reference said variable in the [`d`](/docs/next/api/strings/use-gt) invocation.
+In order to pass a variable to the dictionary entry, we need to do two things: (1) add a variable to the entry and (2) reference said variable in the [`t`](/docs/next/api/dictionary/use-translations) invocation.
 
 First, we add a variable to the dictionary entry with the following syntax: `{username}`.
 `username` is the name of the variable.
@@ -110,7 +110,7 @@ const Component = () => {
 ## Notes
  * Variables are passed as top-level keys in the options object, not nested under a `variables` key.
 
-### Next steps
+## Next steps
  * See [dictionaries](/docs/next/guides/dictionaries) for more information on dictionaries and common practices.
  * See [`useTranslations`](/docs/next/api/dictionary/use-translations) or [`getTranslations`](/docs/next/api/dictionary/get-translations) for more information on dictionaries interface.
  * See [`ICU message format`](https://unicode-org.github.io/icu/userguide/format_parse/messages/) for more information on formatting options.
diff --git a/docs/en-US/next/concepts/environments.mdx b/docs/en-US/next/concepts/environments.mdx
index 921fc34f..135c3308 100644
--- a/docs/en-US/next/concepts/environments.mdx
+++ b/docs/en-US/next/concepts/environments.mdx
@@ -52,7 +52,7 @@ When rendering a component (that uses `useGT`, `<T>`, or `useTranslations`) in a
 1. If it detects a valid, stored translation for the given content, it will render the translation.
 2. If no translation is found, it will attempt to dynamically translate the content via the General Translation API.
 3. After translating, the translation will be rendered, and stored in memory for future use.
-4. If the translation times out, it will fallback and render the original content.
+4. If the translation times out, it will fall back and render the original content.
 
 <Callout type="info">
   Our API also internally caches development translations for a short period of time, so if the same translation is requested again, it will be served from cache.
diff --git a/docs/en-US/next/guides/local-tx.mdx b/docs/en-US/next/guides/local-tx.mdx
index de5e9e04..9388e5eb 100644
--- a/docs/en-US/next/guides/local-tx.mdx
+++ b/docs/en-US/next/guides/local-tx.mdx
@@ -135,4 +135,3 @@ export default async function loadTranslations(locale: string) {
 
 - [Middleware Guide](/docs/next/guides/middleware) - Language detection and routing
 - [Languages Guide](/docs/next/guides/languages) - Configure supported languages
-- API References:
diff --git a/docs/en-US/next/guides/migration.mdx b/docs/en-US/next/guides/migration.mdx
index a7af6c92..dfe00b05 100644
--- a/docs/en-US/next/guides/migration.mdx
+++ b/docs/en-US/next/guides/migration.mdx
@@ -104,7 +104,7 @@ You'll never have to wait for translations again.
 
     1. Fully migrate your entire project to `gt-next`, and remove the old i18n library.
     2. Fully migrate your project, but keep using dictionaries from the old i18n library.
-    2. Keep using the old i18n library for now, and only migrate part of your project to `gt-next`.
+    3. Keep using the old i18n library for now, and only migrate part of your project to `gt-next`.
 
     For more details on each option, see the [migration strategies](#strategies) section.
   </Step>
diff --git a/docs/en-US/next/index.mdx b/docs/en-US/next/index.mdx
index 4804318f..2f5e71f0 100644
--- a/docs/en-US/next/index.mdx
+++ b/docs/en-US/next/index.mdx
@@ -341,7 +341,7 @@ That's it — your app is now multilingual. 🎉
     <T context="the technology company">Apple</T>
     ```
 
-    Both `<T>`, `useGT()`, and `getGT()` support the `context` option.
+    All of `<T>`, `useGT()`, and `getGT()` support the `context` option.
   </Accordion>
 </Accordions>
 
diff --git a/docs/en-US/next/tutorials/examples/next-speedrun.mdx b/docs/en-US/next/tutorials/examples/next-speedrun.mdx
index 315d130a..ad7c4e12 100644
--- a/docs/en-US/next/tutorials/examples/next-speedrun.mdx
+++ b/docs/en-US/next/tutorials/examples/next-speedrun.mdx
@@ -42,7 +42,7 @@ npm i gt
 ## Step 3: Add your environment variables.
 
 Navigate to the [Dashboard](https://generaltranslation.com/en-US/signin).
-Go to the Dev Api Keys page on the nav bar and create a new API key and Project ID.
+Go to the Dev API Keys page on the nav bar and create a new API key and Project ID.
 Then add them to your `.env` file.
 
 ```bash copy
diff --git a/docs/en-US/overview/faqs.mdx b/docs/en-US/overview/faqs.mdx
index 56028394..243f3e30 100644
--- a/docs/en-US/overview/faqs.mdx
+++ b/docs/en-US/overview/faqs.mdx
@@ -13,7 +13,7 @@ For example, `en-US` is a locale code, which refers to the English language as s
 
 ### Can I use the libraries without using the General Translation platform?
 
-Yes you can! 
+Yes, you can! 
 General Translation internationalization libraries are free, open-source, and can be configured to fetch translations from any source.
 
 Read the docs on how to load your own translations [here](/docs/next/api/config/load-translations).
diff --git a/docs/en-US/react-core-linter/guides/quickstart.mdx b/docs/en-US/react-core-linter/guides/quickstart.mdx
index a3f31b96..0b7393ca 100644
--- a/docs/en-US/react-core-linter/guides/quickstart.mdx
+++ b/docs/en-US/react-core-linter/guides/quickstart.mdx
@@ -10,8 +10,6 @@ description: Quickstart guide for the React Core Linter
 This is an ESLint plugin designed to be used with any of our i18n libraries, `gt-react`, `gt-next`, or `gt-react-native`.
 It checks for common implementation errors and offers fixes.
 
-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/react-core-linter/index.mdx b/docs/en-US/react-core-linter/index.mdx
index e7048410..a301160f 100644
--- a/docs/en-US/react-core-linter/index.mdx
+++ b/docs/en-US/react-core-linter/index.mdx
@@ -11,8 +11,6 @@ description: ESLint plugin for GT React libraries
 
 It checks for issues like dynamic content inside `<T>` components and dynamic strings in translation functions, and offers autofixes.
 
-import Video from '@/components/Video';
-
 <Video src='https://assets.gtx.dev/docs/react-core-linter/web-0.1.0.mp4' />
 
 ## Rules
diff --git a/docs/en-US/react-core-linter/rules/static-string.mdx b/docs/en-US/react-core-linter/rules/static-string.mdx
index 06dfad67..1336ed23 100644
--- a/docs/en-US/react-core-linter/rules/static-string.mdx
+++ b/docs/en-US/react-core-linter/rules/static-string.mdx
@@ -21,7 +21,7 @@ Ensures that translation functions like [`gt`](/docs/react/api/strings/use-gt) a
 
 ### staticStringRequired
 
-Registration functions can only accept static strings.
+Translation functions can only accept static strings.
 
 #### ❌ Incorrect
 
diff --git a/docs/en-US/react/api/components/gtprovider.mdx b/docs/en-US/react/api/components/gtprovider.mdx
index 65c8d604..6594c338 100644
--- a/docs/en-US/react/api/components/gtprovider.mdx
+++ b/docs/en-US/react/api/components/gtprovider.mdx
@@ -216,7 +216,7 @@ createRoot(document.getElementById("root")!).render(
 
 ### Render settings
 
-Render settings controls the loading behavior for translations.
+Render settings control the loading behavior for translations.
 There are two fields: `timeout` and `method`.
 
 - `timeout` is the number of milliseconds to wait for a translation to load before showing a fallback (default: `8000ms`).