Drop the 29 Next name from prose and fix typos

[next-devin]

What changed

• Theme intro snippet (content/_snippets/_view-intro-theme.mdx, shown on the themes index and the URLs and template paths page): "the 29 Next platform" now reads "the Next Commerce platform". This also fixes "themeing" and "Github".
• Admin API spec description (tools/config.py): "API versioning allows 29 Next…" now reads "Next Commerce". The permissions link moves from the retired developers.29next.com/docs/api/admin/permissions/ to /docs/admin-api/permissions, and "Oauth" becomes "OAuth".
• Specs: public/api/admin/{2023-02-10,2024-04-01,unstable}.yaml carry the new description. Only info.description was edited. A full update_api_docs.py run would re-download the specs from the live API and bring in unrelated upstream changes, so I didn't run it. The parsed description in each spec now matches config.py exactly.
• Typos: about 30 misspellings in the order and subscription management guides, event tracking, translations, and the custom template guides, found with codespell and typos-cli. Brand casing is also fixed in prose (GitHub, OAuth, PayPal, JavaScript, PyPI), along with a few doubled words.

Legacy technical names (X-29next-API-Version, X-29Next-Signature, {store}.29next.store) and the "Why 29next?" callout are unchanged on purpose.

Checks

• check-frontmatter: OK
• validate-links: no errors in any edited file. The remaining errors are in locally generated GraphQL and agent-setup pages, and main has errors of the same kind.

🤖 Generated with Claude Code

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

This PR is a documentation-only sweep: brand rename (29 Next → Next Commerce in prose, while preserving legacy identifiers like X-29next-API-Version, {store}.29next.store, and the Why 29next? callout), GitHub casing fixes, and ~30 misspellings found by codespell / typos-cli. All edits stay on the stated target (prose and info.description), the hostnames and X-29Next-Api-Version header in the YAML samples are correctly left alone, and the new permissions link path (/docs/admin-api/permissions) matches existing usage in content/docs/admin-api/index.mdx:18 and content/docs/admin-api/guides/assets.mdx:19. No logic, security, or runtime impact.

Files Reviewed (26 files)

• content/_snippets/_view-google-analytics.mdx
• content/_snippets/_view-google-tag-manager.mdx
• content/_snippets/_view-intro-theme.mdx
• content/docs/admin-api/guides/order-management.mdx
• content/docs/admin-api/guides/payment-methods/bankcard.mdx
• content/docs/admin-api/guides/payment-methods/paypal.mdx
• content/docs/admin-api/guides/subscription-management.mdx
• content/docs/apps/app-kit.mdx
• content/docs/apps/guides/dispute-service.mdx
• content/docs/apps/guides/fulfillment-service.mdx
• content/docs/apps/oauth/getting-started.mdx
• content/docs/apps/oauth/index.mdx
• content/docs/apps/oauth/session-auth.mdx
• content/docs/storefront/event-tracking.mdx
• content/docs/storefront/themes/guides/custom-page-templates.mdx
• content/docs/storefront/themes/guides/custom-product-templates.mdx
• content/docs/storefront/themes/guides/product-metadata.md
• content/docs/storefront/themes/index.mdx
• content/docs/storefront/themes/templates/filters.md
• content/docs/storefront/themes/templates/urls-and-template-paths.mdx
• content/docs/storefront/themes/theme-kit.mdx
• content/docs/storefront/themes/translations.mdx
• public/api/admin/2023-02-10.yaml
• public/api/admin/2024-04-01.yaml
• public/api/admin/unstable.yaml
• tools/config.py

---

_{Reviewed by minimax-m3 · Input: 0 · Output: 0 · Cached: 0}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	developer-docs	5b27530	Commit Preview URL Branch Preview URL	Sep 29 2026, 01:23 PM