i18n(ja): restore text dropped by the translation pipeline

[yahonda]

What is changed, added or deleted? (Required)

The machine-translation pipeline numbers inline elements (code spans, links) before translating and restores them afterwards. In many places it failed to restore one, leaving a bare digit where the text should be — and often shuffling the surrounding code spans as well. The English source is intact; only the Japanese is damaged.

EN: ... in which the `WHERE` clause is used to specify the databases and tables to be checked.
    If you want to check the replication status of all databases, remove the `WHERE` clause from the statement.
JA: ... 次のステートメントを実行します。3 句は、確認するデータベースとテーブルを指定します。
    ... ステートメントから`WHERE`句`WHERE`削除します。
->  ... 次のステートメントを実行します。`WHERE`句は、確認するデータベースとテーブルを指定します。
    ... ステートメントから`WHERE`句を削除します。

155 lines across 115 files. Two kinds of damage:

1. Dropped text (127 lines). A digit stands where a code span or word belongs. Deleting the digit alone is not enough — the sentence loses its subject — so each line was reconstructed from the English source.
2. Literal tool tokens (18 lines). Strings such as {{B-PLACEHOLDER-2-PLACEHOLDER-E}} leaked into the published text. The English source contains zero occurrences of "PLACEHOLDER", so all of it is garbage.

Several instances were losing technical information outright:

file	was	now
runtime-filter.md	効率はANALYZE %向上します	効率は 50 %向上します（50 was gone）
as-of-timestamp.md	NOW(3)秒単位で取得	ミリ秒単位で取得（wrong precision）
grafana-pd-dashboard.md	(P99) 100msである必要があります	100ms未満である必要があります（「未満」was gone）
develop/dev-guide-sql-development-specification.md	INの数は300でなければなりません	300未満でなければなりません
pd-control.md ×2	2 に設定すると	falseに設定すると（the value was gone）

How it was checked

Every line was cross-checked against release-8.5 before editing. Mechanical verification after editing:

• link targets: 0 added, removed or altered;
• code spans: 0 invented — every code span introduced exists verbatim in the English source file;
• doubled particles (をを/はは/がが/にに/でで/、、/。。): no increase over the base;
• grep -r PLACEHOLDER: 0 remaining.

Scope note

This PR covers the artifacts that follow a sentence-ending 。. A wider sweep suggests roughly 1,600 further bare-digit sites across ~550 files that still need the same treatment; those are left for follow-up PRs. Note that sweep mixes in genuine numbers (「12 テーブル」, 「0 に設定すると」), so each hit needs an English cross-check before editing.

This damage predates the current translation tooling, which has since been replaced, so it is a finite backlog rather than something that regenerates on each sync.

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

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: e4037f40-1b4d-4587-9cb4-51239b714079

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

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment