[yahonda]

What is changed, added or deleted? (Required)

tidb-cloud/serverless-high-availability.md defines the two high availability options as ゾーン高可用性 (zonal high availability) and リージョン高可用性 (regional high availability), and release-notes-2025.md uses the same terms. Other pages used ゾーナル高可用性, リージョナル高可用性, and リージョンごとの高可用性. This PR unifies them to the defined terms.

Changed sites (4 in 3 files):

• tidb-cloud/byoc/create-tidb-instance-byoc.md: リージョナル高可用性 ×2 → リージョン高可用性, ゾーナル高可用性 ×2 → ゾーン高可用性 (one line)
• tidb-cloud/byoc/manage-resource-pools-byoc.md: ゾーナル高可用性またはリージョナル高可用性 → ゾーン高可用性またはリージョン高可用性
• tidb-cloud/premium/create-tidb-instance-premium.md: リージョンごとの高可用性 → リージョン高可用性

The English source says "zonal high availability" or "regional high availability" at every changed site. The same change in files that open PRs already edit is made there: #24564 (tidb-cloud/releases/tidb-cloud-release-notes.md) and #24565 (tidb-cloud/architecture-concepts.md).

"cross-zone high availability" (ゾーン間高可用性) is a different English term and is not changed. The bold console option labels Zonal and Regional stay in English.

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.

• i18n-ja-release-8.5 (TiDB Japanese documentation for TiDB 8.5 versions)

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

• This PR is translated from:
• Other reference link(s):
  • Related PRs: i18n(ja): fix TiDB Cloud release notes found in the second full review #24564, i18n(ja): fix TiDB Cloud docs (architecture to import) found in the second full review #24565

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

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

[coderabbitai]

Caution

Review failed

The pull request is closed.

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

[yahonda]

Closing: these changes are now part of #24565.