i18n(ja): add missing particle after Markdown links (wo before verbs, wa for subject)

[yahonda]

What is changed, added or deleted? (Required)

This PR adds missing particles immediately after Markdown links in the Japanese documentation, where machine-translated text dropped the particle between a link and the following word.

Main fix — missing を (object marker) before a verb (2,071 cases):

[link text](url)使用して → [link text](url)を使用して

Scope: only where a link is the direct object of a transitive verb — 使用 / 実行 / 参照 / 報告 / 取得 / 指定 / 削除 / 確認 / 作成 followed by an active conjugation (して / すると / する / します / した / しない / できる / できない). Compound nouns such as [link]クラスタ / [link]機能 (which need no particle) and passive され forms are not touched.

Also — missing で (instrumental) (3 cases), where the link is the means rather than the object:

Gemini 埋め込みモデルを[自動埋め込み](url)使用する方法 → …)で使用する方法 ("use the model with Auto Embedding")

Also — missing は (topic marker) after a link or code span that is the sentence subject (2 cases):

[Hibernate](https://hibernate.org/orm/)人気のオープンソースJava ORMです。 → …)は人気の…

2,083 insertions across 793 files. Verified mechanically: every changed line differs from its original by the particle alone, except for the 7 lines below. No double particle introduced.

The second commit (apply review fixes for fluency and mistranslations) addresses review feedback on 7 lines that needed more than a particle:

• Removed a stray 実行します that machine translation appended after link text, e.g. [サポートを受ける](/support.md)実行します → [サポートを受けてください](/support.md)。
• Restored mysql-connector-j from the mangled mysql-コネクタ-j
• Reordered a clause: すでに[TiDBに接続](url)使用して + `TiDBClient`あると仮定します → `TiDBClient`を使用して、すでに[TiDBに接続](url)していると仮定します

Note: this PR may conflict with other in-flight i18n PRs that touch the same files; if so, it will be rebased after those are merged.

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

• 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)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)
• v5.3 (TiDB 5.3 versions)

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

• This PR is translated from: N/A (Japanese-only fluency fix)
• Other reference link(s):

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

Note on scope

A few of the lines in this PR also carry a fix that belongs to one of the sibling ja PRs. Where a later sweep found damage on a line this PR already edits, the fix was applied here rather than duplicated into another PR — otherwise the two PRs would conflict. So a small number of lines go beyond the scope stated above, for example:

-…発生します。1パラメータ`gc.max_write_bytes_per_sec`使用すると、…
+…発生します。`gc.max_write_bytes_per_sec`パラメータを使用すると、…

Here the stray 1 (a translation-tool placeholder) and the word order were repaired alongside this PR's particle insertion.

All fifteen ja PRs were verified to merge cleanly in any order (105 pairwise merges, 0 conflicts).

[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

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

[gemini-code-assist]

Code Review

This pull request systematically improves the Japanese documentation by correcting grammatical particles, specifically ensuring the proper use of 'を参照してください' and 'を使用することをお勧めします' across numerous files. The reviewer's feedback is excellent and highly actionable, identifying several remaining typos (such as stray numbers '5', '1', '17'), grammatical awkwardness, missing particles, inconsistent terminology (e.g., 'storage' vs. 'ストレージ'), and minor formatting issues. All suggested changes are accompanied by ready-to-commit code blocks to ensure high-quality, natural Japanese documentation.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[yahonda]

Thanks for the thorough review. To keep this PR focused on its single purpose (adding the missing particle after Markdown links), the 34 review findings have been addressed in separate PRs by kind, per our PR-splitting strategy:

• Stray numbers before links/tables (5/1/17) → i18n(ja): remove stray digits inserted before code spans #23275 (stray-digit removal)
• Everything else — awkward phrasing/reconstruction, extra spaces/periods, missing particles that this PR did not cover (e.g. 有効, 設定), terminology (storage→ストレージ), and the IAMIAM→IAM typo → i18n(ja): miscellaneous review fixes (bit-shift description) #23274 (misc review fixes)
• A couple already covered by other PRs: MySQLDialectを / TIDB_DECODE_SQL_DIGESTSを (code-span を) is in i18n(ja): add missing object-marker particle (wo) before code-span transitive verbs #23272; the は/を報告 on the Hibernate line is already in this PR.

These sibling PRs share some files with this one and will be rebased after the earlier PRs merge.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7f45b74b-fa7d-4f09-b551-c50ade3d0396

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 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

• X
• Mastodon
• Reddit
• LinkedIn

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