Skip to content

i18n(ja): move particles trapped inside bold UI-label spans outside - #23559

Open
yahonda wants to merge 7 commits into
pingcap:i18n-ja-release-8.5from
yahonda:fix-particle-trapped-in-bold-2026-08-19
Open

i18n(ja): move particles trapped inside bold UI-label spans outside#23559
yahonda wants to merge 7 commits into
pingcap:i18n-ja-release-8.5from
yahonda:fix-particle-trapped-in-bold-2026-08-19

Conversation

@yahonda

@yahonda yahonda commented Aug 19, 2026

Copy link
Copy Markdown
Member

First-time contributors' checklist

What is changed, added or deleted? (Required)

Corpus-wide sweep for a defect where a Japanese particle (を/の/が/に/は/で/と) was bolded together with the preceding label instead of sitting outside the bold span, e.g. **Raft store CPU を** instead of **Raft store CPU**を. This is inconsistent with the convention used throughout the rest of the corpus, where only the label/term is bolded and the particle is plain text.

  • 120 files, 256 occurrences fixed by moving the trailing particle outside the closing **.
  • Also fixes two related pre-existing straddling-bracket typos found in the same sweep (external-storage-uri.md, tidb-cloud/set-up-private-endpoint-connections-on-google-cloud.md) where a bracket was split across the bold boundary.
  • Scope is limited to the particle-position defect only; no wording/translation changes.

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

  • 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):

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

Summary by CodeRabbit

  • Documentation
    • Improved Japanese wording, punctuation, quotation marks, and Markdown emphasis across integration, connection, dashboard, migration, monitoring, and TiDB Cloud guides.
    • Clarified connection setup labels, password-generation steps, Dedicated IP access list guidance, private endpoint instructions, and import/export procedures.
    • Corrected links, navigation labels, button names, and technical terminology for more consistent and accurate instructions.
    • Updated timeout documentation to clarify setQueryTimeout() limitations for older TiDB versions and disabled global-kill configurations.

@ti-chi-bot

ti-chi-bot Bot commented Aug 19, 2026

Copy link
Copy Markdown

[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 csuzhangxc 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:

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 ti-chi-bot Bot added the area/develop This PR relates to the area of TiDB App development. label Aug 19, 2026
@coderabbitai

coderabbitai Bot commented Aug 19, 2026

Copy link
Copy Markdown

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

The pull request updates Japanese documentation across AI integrations, development guides, dashboards, TiDB Cloud procedures, troubleshooting pages, and release notes. The changes correct wording, punctuation, links, quotations, icons, and Markdown emphasis. No code or product behavior changes.

Changes

Documentation corrections

Layer / File(s) Summary
AI and dashboard instructions
ai/integrations/*, ai/vector-search-get-started-using-python.md, dashboard/*
Corrects connection labels, password-generation wording, Japanese grammar, and Markdown emphasis in AI integration and Dashboard procedures.
Development and connection guides
develop/dev-guide-*.md
Corrects Japanese wording, configuration terminology, links, punctuation, and emphasis in connection, integration, transaction, schema, timeout, and sample-application guides.
TiDB Cloud procedures
tidb-cloud/*.md, tidb-cloud/premium/*
Corrects navigation labels, action text, links, quotation boundaries, status descriptions, and Markdown emphasis across TiDB Cloud procedures.
Operational, integration, and release documentation
benchmark/*, deploy-monitoring-services.md, external-storage-uri.md, grafana-tikv-dashboard.md, resources/*, ticdc/*, tidb-troubleshooting-map.md, troubleshoot-write-conflicts.md, tune-tikv-thread-performance.md
Corrects Japanese wording, links, punctuation, inline markup, and emphasis in benchmark, monitoring, TiCDC, troubleshooting, and release documentation.

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

Merge Risk: 🟡 Moderate · up to ea22b

This corpus-wide formatting change still leaves several Japanese wording, UI-label rendering, and cluster-sizing guidance defects that can mislead users or display labels inconsistently. Merge should wait for these bounded documentation corrections.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes moving Japanese particles outside bold UI-label spans, which is the main change.
Description check ✅ Passed The description explains the scope, affected files, version, AI involvement, and change categories; empty reference links are non-critical.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

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

@ti-chi-bot ti-chi-bot Bot added missing-translation-status This PR does not have translation status info. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Aug 19, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 26


ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: a59a65f9-2df6-4409-b52a-5bd0ec7cbcc2

📥 Commits

Reviewing files that changed from the base of the PR and between b77d42f and 6ba2630.

📒 Files selected for processing (114)
  • ai/integrations/tidb-mcp-cursor.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/vector-search-get-started-using-python.md
  • benchmark/v4.0-performance-benchmarking-with-tpch.md
  • dashboard/continuous-profiling.md
  • dashboard/dashboard-cluster-info.md
  • dashboard/dashboard-diagnostics-access.md
  • dashboard/dashboard-resource-manager.md
  • dashboard/dashboard-session-share.md
  • dashboard/dashboard-session-sso.md
  • deploy-monitoring-services.md
  • develop/dev-guide-aws-appflow-integration.md
  • develop/dev-guide-connection-parameters.md
  • develop/dev-guide-create-table.md
  • develop/dev-guide-gui-datagrip.md
  • develop/dev-guide-gui-dbeaver.md
  • develop/dev-guide-gui-mysql-workbench.md
  • develop/dev-guide-gui-navicat.md
  • develop/dev-guide-gui-vscode-sqltools.md
  • develop/dev-guide-proxysql-integration.md
  • develop/dev-guide-sample-application-aws-lambda.md
  • develop/dev-guide-sample-application-golang-gorm.md
  • develop/dev-guide-sample-application-golang-sql-driver.md
  • develop/dev-guide-sample-application-java-hibernate.md
  • develop/dev-guide-sample-application-java-jdbc.md
  • develop/dev-guide-sample-application-java-mybatis.md
  • develop/dev-guide-sample-application-java-spring-boot.md
  • develop/dev-guide-sample-application-nextjs.md
  • develop/dev-guide-sample-application-nodejs-mysql2.md
  • develop/dev-guide-sample-application-nodejs-mysqljs.md
  • develop/dev-guide-sample-application-nodejs-prisma.md
  • develop/dev-guide-sample-application-nodejs-sequelize.md
  • develop/dev-guide-sample-application-nodejs-typeorm.md
  • develop/dev-guide-sample-application-python-django.md
  • develop/dev-guide-sample-application-python-mysql-connector.md
  • develop/dev-guide-sample-application-python-mysqlclient.md
  • develop/dev-guide-sample-application-python-peewee.md
  • develop/dev-guide-sample-application-python-pymysql.md
  • develop/dev-guide-sample-application-python-sqlalchemy.md
  • develop/dev-guide-sample-application-ruby-mysql2.md
  • develop/dev-guide-schema-design-overview.md
  • develop/dev-guide-timeouts-in-tidb.md
  • develop/dev-guide-transaction-restraints.md
  • develop/dev-guide-update-data.md
  • develop/dev-guide-wordpress.md
  • external-storage-uri.md
  • grafana-tikv-dashboard.md
  • resources/tidb-pdf-generation-tutorial.md
  • ticdc/integrate-confluent-using-ticdc.md
  • ticdc/ticdc-bidirectional-replication.md
  • tidb-cloud/backup-and-restore.md
  • tidb-cloud/branch-manage.md
  • tidb-cloud/changefeed-sink-to-apache-kafka.md
  • tidb-cloud/configure-external-storage-access.md
  • tidb-cloud/configure-maintenance-window.md
  • tidb-cloud/configure-serverless-firewall-rules-for-public-endpoints.md
  • tidb-cloud/configure-sql-users.md
  • tidb-cloud/connected-care-overview.md
  • tidb-cloud/create-tidb-cluster-serverless.md
  • tidb-cloud/data-service-api-key.md
  • tidb-cloud/data-service-custom-domain.md
  • tidb-cloud/data-service-manage-data-app.md
  • tidb-cloud/data-service-manage-endpoint.md
  • tidb-cloud/data-service-manage-github-connection.md
  • tidb-cloud/data-service-oas-with-nextjs.md
  • tidb-cloud/data-service-postman-integration.md
  • tidb-cloud/essential-changefeed-sink-to-kafka.md
  • tidb-cloud/essential-database-audit-logging.md
  • tidb-cloud/import-csv-files.md
  • tidb-cloud/import-parquet-files-serverless.md
  • tidb-cloud/import-parquet-files.md
  • tidb-cloud/migrate-from-mysql-using-data-migration.md
  • tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md
  • tidb-cloud/migrate-sql-shards.md
  • tidb-cloud/monitor-alert-email.md
  • tidb-cloud/monitor-alert-flashduty.md
  • tidb-cloud/monitor-alert-pagerduty.md
  • tidb-cloud/monitor-alert-slack.md
  • tidb-cloud/monitor-alert-zoom.md
  • tidb-cloud/naming-conventions-for-data-import.md
  • tidb-cloud/pause-or-resume-tidb-cluster.md
  • tidb-cloud/premium/connect-to-premium-via-aws-private-endpoint.md
  • tidb-cloud/premium/create-tidb-instance-premium.md
  • tidb-cloud/premium/dual-layer-data-encryption-premium.md
  • tidb-cloud/premium/import-from-s3-premium.md
  • tidb-cloud/releases/release-notes-2023.md
  • tidb-cloud/releases/release-notes-2025.md
  • tidb-cloud/scale-tidb-cluster.md
  • tidb-cloud/serverless-export.md
  • tidb-cloud/serverless-private-link-connection-to-amazon-msk.md
  • tidb-cloud/serverless-private-link-connection-to-aws-rds.md
  • tidb-cloud/set-up-private-endpoint-connections-on-azure.md
  • tidb-cloud/set-up-private-endpoint-connections-on-google-cloud.md
  • tidb-cloud/set-up-sink-private-endpoint.md
  • tidb-cloud/setup-azure-self-hosted-kafka-private-link-service.md
  • tidb-cloud/setup-self-hosted-kafka-private-service-connect.md
  • tidb-cloud/size-your-cluster.md
  • tidb-cloud/tidb-cloud-auditing.md
  • tidb-cloud/tidb-cloud-budget.md
  • tidb-cloud/tidb-cloud-password-authentication.md
  • tidb-cloud/tidb-cloud-poc.md
  • tidb-cloud/tidb-cloud-quickstart.md
  • tidb-cloud/tidb-cloud-support.md
  • tidb-cloud/top-ru.md
  • tidb-cloud/v8.5-performance-highlights.md
  • tidb-troubleshooting-map.md
  • troubleshoot-write-conflicts.md
  • tune-tikv-thread-performance.md

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.

Comment thread ai/integrations/vector-search-integrate-with-amazon-bedrock.md
Comment thread dashboard/dashboard-session-sso.md
Comment thread develop/dev-guide-gui-dbeaver.md Outdated
Comment thread develop/dev-guide-sample-application-golang-sql-driver.md
Comment thread develop/dev-guide-sample-application-nodejs-typeorm.md Outdated
Comment thread tidb-cloud/monitor-alert-pagerduty.md Outdated
Comment thread tidb-cloud/monitor-alert-slack.md Outdated
Comment thread tidb-cloud/serverless-private-link-connection-to-amazon-msk.md Outdated
Comment thread tidb-cloud/set-up-private-endpoint-connections-on-azure.md Outdated
Comment thread troubleshoot-write-conflicts.md
@ti-chi-bot ti-chi-bot Bot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Aug 19, 2026
yahonda added a commit to yahonda/docs that referenced this pull request Aug 19, 2026
…odeRabbit

Addresses CodeRabbit's functional-correctness findings on PR pingcap#23559:
- dev-guide-gui-dbeaver.md: closing quote outside the bold dialog label (4x)
- naming-conventions-for-data-import.md, pause-or-resume-tidb-cluster.md,
  data-service-custom-domain.md: opening quote outside the bold status/field label
- branch-manage.md: closing bold marker inside the bracketed [Action] label
- connected-care-overview.md: duplicated word (異なる異なる)
- data-service-manage-github-connection.md: missing し in デプロイして
- migrate-from-mysql-using-data-migration.md: bold span cut a word in half
  with no genuine UI label to emphasize; unbolded the plain prose
- essential-changefeed-sink-to-kafka.md, changefeed-sink-to-apache-kafka.md:
  align the Avro conditional phrasing within each procedure

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
tidb-cloud/size-your-cluster.md (1)

272-272: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Request the TiKV storage type in the Plus storage procedure.

This section documents TiKV storage, but the request text says TiFlashストレージタイプを申請. Support may process the wrong storage request.

Apply this exact replacement
-Plusストレージは、より高いパフォーマンスと安定性を提供し、これらの拡張機能を反映した価格設定となっています。現在、このストレージタイプは、AWSにデプロイされたクラスターに対してのみ、リクエストに応じて利用可能です。リクエストするには、 [TiDB Cloudコンソール](https://tidbcloud.com)の右下にある**「?」**をクリックし、 **Support Tickets**をクリックして[ヘルプセンター](https://tidb.support.pingcap.com/servicedesk/customer/portals)に進みます。チケットを作成し、 **「説明」**フィールドに「 TiFlashストレージタイプを申請」と入力して、 **「送信」**をクリックしてください。
+Plusストレージは、より高いパフォーマンスと安定性を提供し、これらの拡張機能を反映した価格設定となっています。現在、このストレージタイプは、AWSにデプロイされたクラスターに対してのみ、リクエストに応じて利用可能です。リクエストするには、 [TiDB Cloudコンソール](https://tidbcloud.com)の右下にある**「?」**をクリックし、 **Support Tickets**をクリックして[ヘルプセンター](https://tidb.support.pingcap.com/servicedesk/customer/portals)に進みます。チケットを作成し、 **「説明」**フィールドに「TiKVストレージタイプを申請」と入力して、 **「送信」**をクリックしてください。

As per path instructions, this Markdown fix is provided as an exact replacement.

Source: Path instructions


ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: c6096136-e5fa-4dad-93ba-de23c1ed6cde

📥 Commits

Reviewing files that changed from the base of the PR and between 6ba2630 and 8cd34e2.

📒 Files selected for processing (46)
  • dashboard/continuous-profiling.md
  • deploy-monitoring-services.md
  • develop/dev-guide-aws-appflow-integration.md
  • develop/dev-guide-connection-parameters.md
  • develop/dev-guide-sample-application-java-hibernate.md
  • develop/dev-guide-sample-application-java-jdbc.md
  • develop/dev-guide-sample-application-java-mybatis.md
  • develop/dev-guide-sample-application-java-spring-boot.md
  • develop/dev-guide-sample-application-nodejs-mysql2.md
  • develop/dev-guide-sample-application-nodejs-mysqljs.md
  • develop/dev-guide-sample-application-nodejs-prisma.md
  • develop/dev-guide-sample-application-nodejs-sequelize.md
  • develop/dev-guide-sample-application-nodejs-typeorm.md
  • develop/dev-guide-sample-application-python-django.md
  • develop/dev-guide-sample-application-python-mysql-connector.md
  • develop/dev-guide-sample-application-python-mysqlclient.md
  • develop/dev-guide-sample-application-python-peewee.md
  • develop/dev-guide-sample-application-python-pymysql.md
  • develop/dev-guide-sample-application-python-sqlalchemy.md
  • develop/dev-guide-sample-application-ruby-mysql2.md
  • develop/dev-guide-schema-design-overview.md
  • develop/dev-guide-timeouts-in-tidb.md
  • develop/dev-guide-update-data.md
  • external-storage-uri.md
  • resources/tidb-pdf-generation-tutorial.md
  • tidb-cloud/backup-and-restore.md
  • tidb-cloud/changefeed-sink-to-apache-kafka.md
  • tidb-cloud/configure-sql-users.md
  • tidb-cloud/connected-care-overview.md
  • tidb-cloud/data-service-manage-github-connection.md
  • tidb-cloud/data-service-oas-with-nextjs.md
  • tidb-cloud/essential-changefeed-sink-to-kafka.md
  • tidb-cloud/essential-database-audit-logging.md
  • tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md
  • tidb-cloud/monitor-datadog-integration.md
  • tidb-cloud/premium/dual-layer-data-encryption-premium.md
  • tidb-cloud/releases/release-notes-2023.md
  • tidb-cloud/serverless-private-link-connection-to-amazon-msk.md
  • tidb-cloud/serverless-private-link-connection-to-aws-rds.md
  • tidb-cloud/set-up-private-endpoint-connections-on-azure.md
  • tidb-cloud/set-up-private-endpoint-connections-on-google-cloud.md
  • tidb-cloud/setup-azure-self-hosted-kafka-private-link-service.md
  • tidb-cloud/size-your-cluster.md
  • tidb-cloud/tidb-cloud-password-authentication.md
  • tidb-cloud/top-ru.md
  • tidb-troubleshooting-map.md

Included review availability: Your plan provides up to 4 included reviews per hour; 0 remain after this review.

Comment thread dashboard/continuous-profiling.md
Comment thread develop/dev-guide-connection-parameters.md Outdated
Comment thread tidb-cloud/data-service-oas-with-nextjs.md
Comment thread tidb-cloud/essential-database-audit-logging.md Outdated
Comment thread tidb-cloud/size-your-cluster.md
Across 120 files, a Japanese particle (を/の/が/に/は/で/と) was bolded
together with the preceding label instead of sitting outside the bold
span, e.g. **Raft store CPU を** instead of **Raft store CPU**を. Move
the trailing particle outside the closing ** to match the convention
used throughout the rest of the corpus. Also fixes two related
straddling-bracket typos found in the same sweep (external-storage-uri.md,
set-up-private-endpoint-connections-on-google-cloud.md).
…found in 1:1 EN review

Full 1:1 comparison against the English source for every file touched by
the particle-trapped-in-bold sweep, covering:
- dropped particles (を/が/は/の/で) near links, buttons, and identifiers
- garbled/duplicated text fragments and misplaced links
- a systemic straddling-bracket + garbled IP-access-list sentence
  repeated across 15 dev-guide-sample-application-*.md files
- broken <mdsvgicon> container tags restored to self-closing <MDSvgIcon />
- one inverted-meaning mistranslation (Batch Operation / DELETE) in
  tidb-cloud/releases/release-notes-2023.md
- a garbled repo-name link (tikv/tikv, tikv/pd) in deploy-monitoring-services.md
…odeRabbit

Addresses CodeRabbit's functional-correctness findings on PR pingcap#23559:
- dev-guide-gui-dbeaver.md: closing quote outside the bold dialog label (4x)
- naming-conventions-for-data-import.md, pause-or-resume-tidb-cluster.md,
  data-service-custom-domain.md: opening quote outside the bold status/field label
- branch-manage.md: closing bold marker inside the bracketed [Action] label
- connected-care-overview.md: duplicated word (異なる異なる)
- data-service-manage-github-connection.md: missing し in デプロイして
- migrate-from-mysql-using-data-migration.md: bold span cut a word in half
  with no genuine UI label to emphasize; unbolded the plain prose
- essential-changefeed-sink-to-kafka.md, changefeed-sink-to-apache-kafka.md:
  align the Avro conditional phrasing within each procedure
@yahonda
yahonda force-pushed the fix-particle-trapped-in-bold-2026-08-19 branch from cf009e3 to 4f6093a Compare August 19, 2026 06:33
FetchSize から Integer.MIN_VALUE に設定する should use を...に instead
of から (set FetchSize TO Integer.MIN_VALUE, not FROM).
@yahonda
yahonda force-pushed the fix-particle-trapped-in-bold-2026-08-19 branch from a55da1c to ea22bca Compare August 19, 2026 07:20

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 6

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (3)
develop/dev-guide-aws-appflow-integration.md (1)

138-138: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Keep Japanese quotation marks inside the bold UI labels.

  • develop/dev-guide-aws-appflow-integration.md#L138-L138: change 「**接続」** to **「接続」**.
  • develop/dev-guide-gui-dbeaver.md#L71-L71: change **「接続方法**」 to **「接続方法」**.

Source: Path instructions

tidb-cloud/monitor-alert-flashduty.md (1)

61-61: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Keep particles outside bold UI labels.

  • tidb-cloud/monitor-alert-flashduty.md#L61-L61: change **加入者タイプの** to **加入者タイプ**の.
  • tidb-cloud/monitor-alert-flashduty.md#L90-L90: change **加入者タイプの** to **加入者タイプ**の.
  • tidb-cloud/monitor-alert-flashduty.md#L117-L117: change **加入者タイプの** to **加入者タイプ**の.
  • tidb-cloud/monitor-alert-slack.md#L62-L62: change **購読者タイプの** to **購読者タイプ**の.
  • tidb-cloud/monitor-alert-slack.md#L91-L91: change **購読者タイプの** to **購読者タイプ**の.
  • tidb-cloud/monitor-alert-slack.md#L118-L118: change **購読者タイプの** to **購読者タイプ**の.

Source: Path instructions

develop/dev-guide-gui-mysql-workbench.md (1)

78-78: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Correct the shared Japanese UI-label emphasis boundaries. The changed lines close ** after という, before , or after , so the rendered labels include the wrong text.

  • develop/dev-guide-gui-mysql-workbench.md#L78-L78: close the bold span after and before という.
  • develop/dev-guide-gui-mysql-workbench.md#L149-L149: close the bold span after and before という.
  • develop/dev-guide-gui-mysql-workbench.md#L174-L174: close the bold span after and before という.
  • develop/dev-guide-gui-navicat.md#L74-L74: close the bold span after and before という.
  • develop/dev-guide-gui-navicat.md#L112-L112: close the bold span after and before という.
  • develop/dev-guide-gui-navicat.md#L143-L143: close both label spans after ; keep outside the second span.
  • develop/dev-guide-gui-navicat.md#L149-L149: close the bold span after and before という.
  • develop/dev-guide-gui-navicat.md#L170-L170: close the bold span after and before という.

Source: Path instructions


ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 1aadb28d-27fe-459c-af5f-af0180ca40b5

📥 Commits

Reviewing files that changed from the base of the PR and between 8cd34e2 and ea22bca.

📒 Files selected for processing (29)
  • develop/dev-guide-aws-appflow-integration.md
  • develop/dev-guide-connection-parameters.md
  • develop/dev-guide-gui-datagrip.md
  • develop/dev-guide-gui-dbeaver.md
  • develop/dev-guide-gui-mysql-workbench.md
  • develop/dev-guide-gui-navicat.md
  • resources/tidb-pdf-generation-tutorial.md
  • ticdc/integrate-confluent-using-ticdc.md
  • tidb-cloud/backup-and-restore.md
  • tidb-cloud/branch-manage.md
  • tidb-cloud/changefeed-sink-to-apache-kafka.md
  • tidb-cloud/configure-external-storage-access.md
  • tidb-cloud/connected-care-overview.md
  • tidb-cloud/data-service-custom-domain.md
  • tidb-cloud/data-service-manage-github-connection.md
  • tidb-cloud/data-service-postman-integration.md
  • tidb-cloud/essential-changefeed-sink-to-kafka.md
  • tidb-cloud/migrate-from-mysql-using-data-migration.md
  • tidb-cloud/migrate-sql-shards.md
  • tidb-cloud/monitor-alert-flashduty.md
  • tidb-cloud/monitor-alert-slack.md
  • tidb-cloud/monitor-alert-zoom.md
  • tidb-cloud/naming-conventions-for-data-import.md
  • tidb-cloud/pause-or-resume-tidb-cluster.md
  • tidb-cloud/premium/create-tidb-instance-premium.md
  • tidb-cloud/releases/release-notes-2023.md
  • tidb-cloud/tidb-cloud-auditing.md
  • tidb-cloud/tidb-cloud-poc.md
  • tidb-cloud/tidb-cloud-quickstart.md

Included review availability: Your plan provides up to 4 included reviews per hour; 0 remain after this review.

Comment thread develop/dev-guide-aws-appflow-integration.md Outdated
Comment thread develop/dev-guide-aws-appflow-integration.md
Comment thread develop/dev-guide-connection-parameters.md Outdated
Comment thread develop/dev-guide-connection-parameters.md Outdated
Comment thread tidb-cloud/changefeed-sink-to-apache-kafka.md Outdated
Comment thread tidb-cloud/configure-external-storage-access.md Outdated
yahonda and others added 2 commits August 19, 2026 16:48
- dev-guide-aws-appflow-integration.md: remove duplicated "console"
  noun after a link that already says "AWS Management Console"
- dev-guide-connection-parameters.md: add missing particle before
  "enable"; fix "actual numeric value HDD" mistranslation of
  "actual number of HDD"
- changefeed-sink-to-apache-kafka.md: add missing particle before
  "data types"
- configure-external-storage-access.md: move Japanese comma/particle
  outside bold IAM-permission-name spans (x3), matching this PR's
  particle-trapped-in-bold fix pattern

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The English source never wraps a bold UI-label span (e.g. Click
**Connect**) in quotes, but the ja translation had accumulated 「」
around many such spans (e.g. **「接続」**), across single-word button
labels, symbols (**「+」**, **「...」**), and longer descriptive labels
(**「クラウドストレージからデータをインポート」**). Verified this
pattern holds against EN for a representative sample across short and
long labels before doing a mechanical, corpus-wide strip: **「X」** ->
**X**, applied only where the quote marks sit immediately inside the
bold delimiters (1,577 occurrences across 233 files).

This supersedes the narrower carve-outs used in PR pingcap#23551/pingcap#23552,
which kept a handful of terms quoted for in-file convention (接続
タイプ, スキーマロード, 接続方法, 組織設定, etc.) - per the standing
policy, in-file consistency is not a reason to keep quoting a term EN
never quotes.

Verified per-file: line count, ** count, [ count, and ] count are
all unchanged (0 anomalies across all 233 changed files) - only the
「」 characters were removed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…-bold-2026-08-19

Resolved 42 file conflicts (took this branch's particle-fix as the
base, then re-applied the quote-stripping substitution on top). Also
found and fixed a gap: several lines had a particle trapped between
the closing 」 and the closing ** (e.g. **「X」を**), which this
branch's own fix correctly un-traps to **「X」**を - but since that
line wasn't conflicted (fix-strip-non-en-quotes-2026-08-20 couldn't
match the trapped-particle form in the base branch), git auto-merged
it without reprocessing, leaving the quotes in place. Ran a second,
whole-tree pass of the quote-strip substitution after the merge to
catch these newly-matchable cases: 92 more occurrences across 62
files. Verified 0 remaining quote-wrapped bold spans and 0
bracket-count anomalies across all 238 changed files.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@pingcap-cla-assistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ yahonda
❌ test


test seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@qiancai qiancai added translation/no-need No need to translate this PR. and removed missing-translation-status This PR does not have translation status info. labels Aug 20, 2026
@ti-chi-bot ti-chi-bot Bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Aug 20, 2026
@ti-chi-bot

ti-chi-bot Bot commented Aug 20, 2026

Copy link
Copy Markdown

[LGTM Timeline notifier]

Timeline:

  • 2026-08-20 11:07:08.319062744 +0000 UTC m=+154263.490156850: ☑️ agreed by qiancai.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/develop This PR relates to the area of TiDB App development. needs-1-more-lgtm Indicates a PR needs 1 more LGTM. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. translation/no-need No need to translate this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants