docs: fix typos, broken code fences, and metadata errors (daily scan 2026-07-15)

[claude]

Requested by Archie McKenzie · Slack thread

Summary

Daily automated docs-quality scan across every subsection of docs/en-US/, plus blog/en-US/, devlog/en-US/, and authors/. 17 files touched, all conservative, high-confidence fixes — no prose rewrites, no code-semantics changes.

Before / After (grouped by subsection)

docs/en-US/core

• quickstart.mdx: garbled sentence "later check the enqueue the file" → "later enqueue the file"

docs/en-US/key-concepts

• dynamic-content.mdx: inconsistent abbreviation "ie" → "i.e." (matches the correct usage one sentence later)

docs/en-US/locadex

• auto-merge.mdx: misplaced closing quote in image alt text — "Locadex Agent selected" → "Locadex Agent" selected

docs/en-US/next

• api/components/tx.mdx and api/strings/tx.mdx: dangling duplicate predicate ("...to load is significantly slower") → "...to load, which is significantly slower"; both also had a getGT link pointing at the useGT reference page instead of getGT's own page — fixed
• api/config/with-gt-config.mdx: "vercel" → "Vercel" (brand capitalization)
• api/strings/get-messages.mdx: "Translations strings" → "Translation strings"
• guides/migration.mdx: duplicated list number (1, 2, 2) → (1, 2, 3)

docs/en-US/react-core-linter

• rules/static-string.mdx: "Registration functions" → "Translation functions" (matches the rule's actual subject and every other reference in the file)

docs/en-US/react-native

• concepts/stand-alone.mdx: frontmatter description said "gt-react" instead of "gt-react-native" (copy-paste leftover from the shared template)

blog/en-US

• gt-next.mdx: unlabeled code fence → ```bash
• plurals.mdx: 4 unlabeled code fences → ```text; pronoun agreement fix ("check their docs" → "check its docs", referring to a singular library)

devlog/en-US

• gt-next_v6_3_0.mdx, gt-react_v10_18_0.mdx: unlabeled code fences → ```text
• gt-next_v6_10_0.mdx: pronoun agreement fix ("if they are to update" → "if it is to update")

authors/

• archie.mdx: malformed twitter URL had a trailing /photo segment — removed
• jackie.mdx: missing required occupation frontmatter field — added Software Engineer, taken directly from the existing bio text

Not fixed (flagged for follow-up, needs human/build-system judgment — not included in this PR)

• docs/en-US/next: ~33 of 79 files (42%) are blank auto-generation stubs with fully-written source templates under docs-templates/ that were apparently never synced — the highest-impact finding this run, but fixing it means re-running the doc-generation pipeline, not editing prose.
• Several import Video from '@/components/Video' statements in MDX bodies (core/index.mdx, react-core-linter/index.mdx + guides/quickstart.mdx, blog/i18n-without-translation-files.mdx, 3 devlog files) — these are CI hard-fails per CONTRIBUTING.md, but the fix requires a build-system decision (e.g. registering Video as a global MDX component) rather than a one-line content edit.
• docs/en-US/api/**: 6 pages missing frontmatter description — root cause traces to missing description fields in the shared openapi.yaml used to generate these pages, not the .mdx files themselves.
• A couple of incomplete-sentence / missing-content issues (core/locales.mdx, next/tutorials/examples/currency-converter/setup.mdx) that need an author to supply the missing text.

How

Files touched: authors/archie.mdx, authors/jackie.mdx, blog/en-US/gt-next.mdx, blog/en-US/plurals.mdx, devlog/en-US/gt-next_v6_10_0.mdx, devlog/en-US/gt-next_v6_3_0.mdx, devlog/en-US/gt-react_v10_18_0.mdx, docs/en-US/core/quickstart.mdx, docs/en-US/key-concepts/dynamic-content.mdx, docs/en-US/locadex/auto-merge.mdx, docs/en-US/next/api/components/tx.mdx, docs/en-US/next/api/config/with-gt-config.mdx, docs/en-US/next/api/strings/get-messages.mdx, docs/en-US/next/api/strings/tx.mdx, docs/en-US/next/guides/migration.mdx, docs/en-US/react-core-linter/rules/static-string.mdx, docs/en-US/react-native/concepts/stand-alone.mdx.

---

Generated by Claude Code

[moss-bryophyta]

Closing stale docs PR — docs review is moving to a linter-based workflow going forward, and this backlog is now out of date (per Taylor). Keeping #372 and #373.