i18n(ja): repair sentences scrambled by the translation pipeline

[yahonda]

What is changed, added or deleted? (Required)

Sites where the old MT pipeline scrambled the sentence itself — transposed or duplicated code spans, tore a list apart, or left its internal markers in the text. A missing particle can be inserted; these cannot, because the word order is wrong. Each sentence was rewritten against the English source.

25 lines across 18 files, in two groups.

1. Scrambled word order (11 lines)

EN: If you cannot confirm the condition that the query result falls in only one partition
    (such as `in`, `between`, `>`, `<`, `>=`, `<=`), you cannot use the partition pruning optimization.
JA: クエリ結果`between` 1つの`>` `in` ）のみに該当するという条件を確認できない場合は、
    パーティションプルーニング最適化`<=`使用できません。 `<` `>=`
->  クエリ結果が1つのパーティションのみに該当するという条件（ `in` 、 `between` 、 `>` 、 `<` 、 `>=` 、 `<=`など）を
    確認できない場合は、パーティションプルーニング最適化を使用できません。例:

Three of the six operators had been stranded after the sentence-final period; the word パーティション and the trailing 例: had been swallowed.

Others in this group carried wrong information rather than just bad grammar:

file	was	now
functions-and-operators/window-functions.md	7がnの場合	nが1の場合 — EN "When n is 1"
tiflash/troubleshoot-tiflash.md	…を返して次のステップに進みます	…を実行してから次のステップに進みます — EN's "and" had become 返す
ticdc/ticdc-open-api-v2.md	詳細は3のセクションを参照してください	詳細はそのセクションを参照してください — EN "See that section"
sql-statements/sql-statement-drop-index.md	`CLUSTERED`型`CLUSTERED`主キー	`CLUSTERED`型の主キー — duplicated span

2. Leftover tool markers (14 lines)

{{B, {{B-, -E}} — the same pipeline artifact as the PLACEHOLDER strings fixed in #23315, but in a different surface form that a grep PLACEHOLDER misses. The English source contains zero occurrences of either, so all of it is garbage; in every case it had swallowed words and shuffled the neighbouring spans.

JA: TiDB は`SELECT` 、 `USE` }、{{B- `SHOW` -E}} など、データを変更しないステートメントのみを実行します。
->  TiDB は`SELECT` 、 `USE` 、 `SHOW` など、データを変更しないステートメントのみを実行します。

Legitimate }} in JSON and log samples was excluded from the sweep and left untouched.

How it was checked

• Every site read against release-8.5 before editing.
• Per changed line, the multiset of code spans and of link URLs is unchanged — spans were only repositioned (or, for a duplicate, the extra one removed). 0 invented spans, 0 altered URLs.
• No doubled particle introduced. grep -rn '{{B\|PLACEHOLDER\|-E}}': 0 remaining across the whole tree.

Relationship to the sibling PRs

Developed on top of the other open ja PRs and harmonized with them: all fourteen merge cleanly in any order (verified — 91 pairwise merges, 0 conflicts).

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 accuracy fix)
• Other reference link(s): sibling ja PRs i18n(ja): add missing object-marker particle (wo) before code-span transitive verbs #23272 i18n(ja): add missing particle after Markdown links (wo before verbs, wa for subject) #23273 i18n(ja): miscellaneous review fixes (bit-shift description) #23274 i18n(ja): remove stray digits inserted before code spans #23275 i18n(ja): standardize the "Data Service" product name (データサービス → Data Service) #23291 i18n(ja): restore admonition labels to English (Note/Warning/Tip) #23292 i18n(ja): fix trailing "page number" typo after page reference links #23294 i18n(ja): restore variable names and clean up heading anchors in system variable docs #23295 i18n(ja): unify "plan cache" katakana term (remove stray space) in sql-prepared-plan-cache.md #23297 i18n(ja): fix partial negations rendered as full negations #23311 i18n(ja): restore text dropped by the translation pipeline #23315 i18n(ja): restore text dropped by the translation pipeline (part 2) #23316 i18n(ja): restore particles dropped after code spans and links #23318

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

[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: 9b0e4ffb-0961-4709-acab-71ec12e24f5d

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

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