docs: fix code fences, prose typos, and list numbering (daily scan 2026-06-27)

[claude]

Requested by Archie McKenzie · Slack thread

Summary

Automated daily documentation quality scan for 2026-06-27. 13 high-confidence fixes across 8 files.

Before / After

Blog

blog/en-US/gt-next.mdx

• Line 11: ``` copy → ```bash copy (missing language identifier)

blog/en-US/multilingual-nextjs-seo.mdx

• Line 36: ``` → ```text (URL examples block, missing language identifier)
• Line 49: ``` → ```text (directory tree block, missing language identifier)

blog/en-US/plurals.mdx

• Lines 15, 90, 171, 180: ``` → ```text (four example-output blocks, missing language identifiers)

Devlog

devlog/en-US/gt-next_v6_10_0.mdx

• Line 57: "from the reading the URL path" → "from reading the URL path" (duplicate "the")

Docs — next/guides

docs/en-US/next/guides/cache-components.mdx

• Lines 74, 91: four-backtick closing fences → three-backtick (matching opening fences)

docs/en-US/next/guides/migration.mdx

• Lines 105–107: Second list item numbered 2. → 3. (duplicate numbering in a 3-option list)

Docs — next/api/strings

docs/en-US/next/api/strings/get-gt.mdx

• Line 151: "Translations strings with getGT" → "Translating strings with getGT" (grammar)

docs/en-US/next/api/strings/get-messages.mdx

• Line 155: "Translations strings with getMessages" → "Translating strings with getMessages" (grammar)

How

Scanned every .mdx file in the repo with parallel subagents (one per subsection), verified findings by direct file reads, and applied only high-confidence fixes:

• Code fences without language identifiers (CONTRIBUTING.md requires all fences to have a language tag)
• Mismatched backtick counts (4-backtick closers for 3-backtick openers)
• Prose typos confirmed by reading the exact lines
• Skipped: auto-generated Fumadocs API pages (marked "do not edit"), heading-level patterns consistent across all SDK FAQ pages (likely intentional), and import statements required for MDX component rendering

[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.