i18n-ja-release-8.5: translate doc changes from pingcap/docs release-8.5 on 2026-07-23

[github-actions]

What is changed, added or deleted? (Required)

Translate documentation changes from pingcap/docs release-8.5 to Japanese via ai-markdown-translator commit-diff sync.

English commit diff:

37c45d5...b6f7f75

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

• i18n-ja-release-8.5

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

• Source repo: pingcap/docs
• Source branch: release-8.5
• TOCs: TOC.md,TOC-ai.md,TOC-api.md,TOC-best-practices.md,TOC-develop.md,TOC-tidb-releases.md,TOC-tidb-cloud.md,TOC-tidb-cloud-starter.md,TOC-tidb-cloud-essential.md,TOC-tidb-cloud-premium.md,TOC-tidb-cloud-releases.md
• Source files: TOC-tidb-cloud-essential.md,TOC-tidb-cloud-premium.md,TOC-tidb-cloud-releases.md,ai/guides/vector-search-full-text-search-sql.md,best-practices/tidb-best-practices.md,index-advisor.md,sql-statements/sql-statement-cancel-distribution-job.md,sql-statements/sql-statement-distribute-table.md,sql-statements/sql-statement-show-distribution-jobs.md,sql-statements/sql-statement-show-table-distribution.md,statistics.md,sync-diff-inspector/sync-diff-inspector-overview.md,system-variables.md,tidb-cloud/architecture-concepts.md,tidb-cloud/backup-and-restore-concepts.md,tidb-cloud/manage-projects-and-resources.md,tidb-cloud/manage-user-access.md,tidb-cloud/premium/backup-and-restore-premium.md,tidb-cloud/releases/_index.md,tidb-cloud/releases/tidb-cloud-kernel-versioning.md,tidb-cloud/releases/tidb-cloud-release-notes.md,tidb-cloud/releases/tidb-x-cloud.202510.1.md,tidb-cloud/select-cluster-tier.md,tidb-cloud/tidb-cloud-intro.md,tidb-cloud/v8.1-performance-benchmarking-with-tpcc.md,tidb-cloud/v8.5-performance-benchmarking-with-tpcc.md,troubleshoot-tidb-oom.md
• Sync outcome: failure

Translation failures

The following files were not translated automatically and must be handled manually before merging.

• tidb-cloud/tidb-cloud-intro.md: structure-preserving reconciliation declined tidb-cloud/tidb-cloud-intro.md

Docs with document structure mismatches after translation

The following files were translated, but their Markdown heading or CustomContent structure does not match the source HEAD file.

• sync-diff-inspector/sync-diff-inspector-overview.md: heading level sequence differs
  • Source: #x1 ##x6 ###x6 ##x1
  • Target: #x1 ##x6 ###x6 ##x2
  • First difference: heading 15: source (missing), target ##

Before merging this PR, manually translate the failed files above or rerun this workflow with workflow_dispatch and file_names set to those paths.

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

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

[ti-chi-bot]

Hi @github-actions[bot]. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[yahonda]

Review note: missing translation in tidb-cloud/tidb-cloud-intro.md

While reviewing this sync against the English diff (37c45d5...b6f7f75), I found one content gap.

The English tidb-cloud/tidb-cloud-intro.md adds two <CustomContent plan="byoc"> blocks (a BYOC intro paragraph and a BYOC architecture note), but the ja version in this PR does not include them (EN: 167 lines / ja: 149 lines, 2 BYOC blocks vs 0).

For reference, tidb-cloud/architecture-concepts.md does have its ## TiDB Cloud BYOC section translated in this branch, so the omission in tidb-cloud-intro.md looks inconsistent rather than a blanket "BYOC is out of ja scope" skip — though it may still be intentional (BYOC is in private preview).

Missing English blocks:

<CustomContent plan="byoc">

    {{{ .byoc }}} is designed for large-scale production workloads that require greater control, security, and compliance. It enables you to run the data plane in your own AWS account while benefiting from TiDB Cloud's automated operations, elastic scalability, and enterprise-grade security.

    Currently, {{{ .byoc }}} is in private preview on AWS.

</CustomContent>

<CustomContent plan="byoc">

> **Note:**
>
> TiDB Cloud BYOC uses a different architecture from other TiDB Cloud deployment options. In BYOC, the TiDB Cloud control plane is managed by PingCAP, while the data plane runs in your own cloud account. For details, see the [TiDB Cloud BYOC architecture](/tidb-cloud/architecture-concepts.md#tidb-cloud-byoc).

</CustomContent>

All other 25 translated files match the new English structure 1:1, and the remaining English-changed files (.agents/*, tidb-cloud-lake/*, tidb-cloud/byoc/*, TOC-tidb-cloud-byoc.md, TOC-tidb-cloud-lake.md) are not part of the ja doc set, so they are correctly untranslated.

[qiancai]

tidb-cloud/tidb-cloud-intro.md

@yahonda The "tidb-cloud/tidb-cloud-intro.md" was added in f9f521c.

[ti-chi-bot]

@yahonda: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.