i18n(ja): add missing object-marker particle (wo) before code-span transitive verbs

[yahonda]

What is changed, added or deleted? (Required)

This PR adds the missing を (object marker) particle before code-span verbs in the Japanese documentation. Machine-translated text frequently dropped を between a code span (command flag, identifier, SQL keyword, etc.) and the following transitive verb.

Example: `--force`使用すると → `--force`を使用すると

Scope — only unambiguous transitive verbs where the code span is the direct object:

• 使用 (use), 実行 (execute), 削除 (delete), 取得 (get), 確認 (check), 指定 (specify)
• followed by an active conjugation (して / すると / する / します / した / しない / できる / できない)

Excluded — to avoid introducing incorrect particles:

• Passive され forms (which take が, not を)
• Compound nouns such as 実行中 / 使用時 (which need no を)
• 設定 / 変更 / 追加 (context-dependent を / に / で, e.g. "set to off" = offに設定)

912 insertions across 397 files. All changes are 1-for-1 line replacements (particle insertion only) — no content changes. No double-を introduced (verified).

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

[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 performs a comprehensive proofreading of the Japanese documentation, primarily focusing on correcting particles (such as adding "を" after backticked command, function, or parameter names) and refining verb forms to improve natural logical flow and readability. A review comment was provided pointing out a translation issue in sql-tuning-best-practice.md where the operator list and pushdown description were unnatural compared to the English original; this comment has been kept as it identifies a valid translation improvement opportunity.

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.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-07-15 15:17:43.224465574 +0000 UTC m=+813249.260560650: ☑️ agreed by qiancai.