[yahonda]

What is changed, added or deleted? (Required)

This PR fixes two problems in tidb-cloud/byoc/multi-region-deployment.md. They were found during a line-by-line review of the Japanese BYOC docs (#24524). The Japanese page is translated from this English page, so it has the same problems.

Line	Before	After	Why
154	A plain \--stack all update is safe…	A plain `--stack all` update is safe…	The escaped \--stack all is a command-line option, so it is now in code format, as in the code blocks above and below it (lines 149, 164, 185, and 203).
219	…perform the joint validation described in Section 5 for each new region.	…perform the joint validation described in [TiDB Cloud BYOC Joint Validation](/tidb-cloud/byoc/joint-validation.md) for each new region.	The document has no Section 5. The joint validation is Phase 5 of the onboarding process (byoc-onboarding-overview.md: "Phase 5: Validation"), which is documented in joint-validation.md. The text now links to that page.

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v8.5 (TiDB 8.5 versions)
• v8.4 (TiDB 8.4 versions)
• v8.3 (TiDB 8.3 versions)
• v8.2 (TiDB 8.2 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)

What is the related PR or file link(s)?

• This PR is translated from:
• Other reference link(s):
  • i18n(ja): fix TiDB Cloud BYOC docs found in a full review #24524 (Japanese BYOC review)

AI agent involvement

• The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated the regional deployment guide to link directly to the BYOC Joint Validation document.

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: pingcap/docs/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: b24f44a3-becc-4f81-9437-7445e1e6dbe1

📥 Commits

Reviewing files that changed from the base of the PR and between 6e320b1 and d71e62f.

📒 Files selected for processing: 1

• tidb-cloud/byoc/multi-region-deployment.md

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 1 remain after this review.

📝 Walkthrough

The multi-region deployment guide now links to the BYOC Joint Validation document. It also changes the Markdown rendering of the --stack all safety statement without changing its meaning.

Changes: Deployment guide

Layer / File(s)	Summary
Update deployment guide text tidb-cloud/byoc/multi-region-deployment.md	The safety statement keeps its meaning, and its command text renders plainly. The completion step links directly to the BYOC Joint Validation document instead of referring to “Section 5.”

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Suggested reviewers: lilin90

Merge Risk: ⚪ Minimal · up to d71e6

The guide renders the command correctly and links the completion step to the existing joint-validation document. No actionable merge risk remains.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title clearly identifies both documentation fixes: code formatting and correction of a section reference in the BYOC multi-region deployment document.
Description check		The description explains both changes, their reasons, the affected TiDB version, the related PR, AI involvement, and applicable change categories. It provides sufficient context for review.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lilin90 for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment