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

[github-actions]

What is changed, added or deleted? (Required)

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

English commit diff:

fc7b45e...42da425

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-starter.md,TOC-tidb-cloud.md,ai/concepts/vector-search-overview.md,ai/guides/vector-search-full-text-search-python.md,ai/guides/vector-search-full-text-search-sql.md,ai/guides/vector-search-hybrid-search.md,ai/integrations/vector-search-integrate-with-amazon-bedrock.md,ai/integrations/vector-search-integrate-with-django-orm.md,ai/integrations/vector-search-integrate-with-jinaai-embedding.md,ai/integrations/vector-search-integrate-with-langchain.md,ai/integrations/vector-search-integrate-with-llamaindex.md,ai/integrations/vector-search-integrate-with-peewee.md,ai/integrations/vector-search-integrate-with-sqlalchemy.md,ai/integrations/vector-search-integration-overview.md,ai/quickstart-via-python.md,ai/quickstart-via-sql.md,ai/reference/vector-search-data-types.md,ai/reference/vector-search-functions-and-operators.md,ai/reference/vector-search-improve-performance.md,ai/reference/vector-search-index.md,ai/reference/vector-search-limitations.md,mysql-compatibility.md,sql-statements/sql-statement-add-index.md,sql-statements/sql-statement-create-index.md,sql-statements/sql-statement-create-table.md,sql-statements/sql-statement-flashback-cluster.md,system-variables.md,tidb-cloud/backup-and-restore.md,tidb-cloud/branch-github-integration.md,tidb-cloud/branch-manage.md,tidb-cloud/branch-overview.md,tidb-cloud/connect-via-standard-connection-serverless.md,tidb-cloud/dedicated/_index.md,tidb-cloud/essential-changefeed-overview.md,tidb-cloud/essential-database-audit-logging.md,tidb-cloud/essential/_index.md,tidb-cloud/limited-sql-features-tidb-x.md,tidb-cloud/limited-sql-features.md,tidb-cloud/migrate-from-mysql-using-data-migration.md,tidb-cloud/premium/_index.md,tidb-cloud/premium/connect-to-premium-via-aws-private-endpoint.md,tidb-cloud/releases/tidb-cloud-release-notes.md,tidb-cloud/security-concepts.md,tidb-cloud/serverless-export.md,tidb-cloud/serverless-private-link-connection.md,tidb-cloud/set-up-private-endpoint-connections-serverless.md,tidb-cloud/set-up-private-endpoint-connections.md,tidb-cloud/starter/_index.md,tidb-cloud/tidb-cloud-import-local-files.md,tidb-configuration-file.md
• Sync outcome: failure

Translation failures

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

• tidb-cloud/branch-github-integration.md: No sections matched
• tidb-cloud/dedicated/_index.md: Could not get target file content for tidb-cloud/dedicated/_index.md
• tidb-cloud/essential/_index.md: Could not get target file content for tidb-cloud/essential/_index.md
• tidb-cloud/premium/_index.md: Could not get target file content for tidb-cloud/premium/_index.md
• tidb-cloud/starter/_index.md: Could not get target file content for tidb-cloud/starter/_index.md
• tidb-configuration-file.md: No sections matched

Docs with document structure mismatches after translation

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

• tidb-cloud/set-up-private-endpoint-connections-serverless.md: heading level sequence differs
  • Source: #x1 ##x4 ###x4 ##x1 ###x5 ##x1 ###x1
  • Target: #x1 ##x4 ###x1 ##x1 ###x8 ##x1 ###x1
  • First difference: heading 7: source ###, 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]

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.

[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

[yahonda]

Review suggestions have been added.

[yahonda]

tidb-cloud/set-up-private-endpoint-connections-serverless.md: heading level sequence differs

Fixed the markdown heading levels.

#	English	Japanese	Level
1	# Connect to {{{ .starter }}} or Essential via AWS PrivateLink	# AWS PrivateLink経由でTiDB Cloud StarterまたはEssentialに接続します。	H1 ✅
2	## Restrictions	## 制限	H2 ✅
3	## Prerequisites	## 前提条件	H2 ✅
4	## Choose an endpoint model	## エンドポイントモデルを選択する	H2 ✅
5	## Set up a private endpoint with AWS (endpoint shared model)	## AWSでプライベートエンドポイントを設定する（endpoint shared model）	H2 ✅
6	### Step 1. Choose a {{{ .starter }}} or Essential instance	### ステップ1. TiDB Cloud StarterまたはEssentialインスタンスを選択します	H3 ✅
7	### Step 2. Create an AWS interface endpoint	### ステップ2. AWSインターフェースエンドポイントを作成する	H3 ✅
8	### Step 3. Authorize your private endpoint in TiDB Cloud (optional)	### ステップ3．TiDB Cloudでプライベートエンドポイントを認証する（オプション）	H3 ✅
9	### Step 4. Connect to your {{{ .starter }}} or Essential instance	### ステップ4. TiDB Cloud StarterまたはEssentialインスタンスに接続します	H3 ✅
10	## Set up a private endpoint with AWS (endpoint exclusive model)	## AWSでプライベートエンドポイントを設定する（エンドポイント占有モデル）	H2 ✅
11	### Step 1. Select a {{{ .essential }}} instance	### ステップ1. {{{ .essential }}} インスタンスを選択する	H3 ✅
12	### Step 2. Create an AWS interface endpoint {#...exclusive-model}	### ステップ2. AWSインターフェースエンドポイントを作成する {#...exclusive-model}	H3 ✅
13	### Step 3. Create a private endpoint connection {#...exclusive-model}	### ステップ3. プライベートエンドポイント接続を作成する {#...exclusive-model}	H3 ✅
14	### Step 4. Enable private DNS {#...exclusive-model}	### ステップ4. プライベートDNSを有効にする {#...exclusive-model}	H3 ✅
15	### Step 5. Connect to your {{{ .essential }}} instance	### ステップ5. {{{ .essential }}} インスタンスに接続する	H3 ✅
16	## Troubleshooting	## トラブルシューティング	H2 ✅
17	### I cannot connect to a {{{ .starter }}} or Essential instance via a private endpoint after enabling private DNS. Why?	### プライベートDNSを有効にした後、プライベートエンドポイント経由でTiDB Cloud StarterまたはEssentialインスタンスに接続できません。なぜでしょうか？	H3 ✅

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