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 — transitive verbs where the code span is the direct object:

• 使用 / 実行 / 削除 / 取得 / 確認 / 指定 / 保存 / 作成 / 更新 / 生成 / 定義 / 出力 / 表示 / 計算 / 記録 / 参照
• 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 verbs 設定 / 変更 / 追加 / 変換 / 適用 (を / に / から, e.g. "set to off" = offに設定)

942 insertions across 406 files. All changes are 1-for-1 line replacements — no content changes. Verified mechanically: every changed line differs from its original by the particle alone. No double-を introduced.

Three lines needed a particle other than を, corrected accordingly:

• dm/dm-error-handling.md: binlogの位置をuint32で保存 (not を — would double the object marker)
• system-variables.md: falseは生成しない (matches the true clause, which takes no を)
• tidb-lightning/tidb-lightning-faq.md: ファイルを/tmp/tidb-lightning.tomlに作成 (not を)

One line dropped a redundant marker: develop/dev-guide-paginate-results.md クラスをPageMetaを定義 → クラスPageMetaを定義.

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

[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: ba31efc2-f142-4739-b38f-02124e0cc039

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