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

[yahonda]

What is changed, added or deleted? (Required)

Follow-up to #23315, sweeping the same translation-pipeline damage outside the 。-anchored subset that PR covered.

The old MT pipeline numbered inline elements (code spans, links) before translating and sometimes failed to restore one, leaving a bare digit where the text belongs — often shuffling the surrounding spans too. The English source is intact; only the Japanese is damaged.

EN: The former command shows the states of all resources and data sources.
JA: コマンド 1 は、すべてのリソースとデータソースの状態を表示します。
->  前者のコマンドは、すべてのリソースとデータソースの状態を表示します。

327 lines across 208 files. This branch was rebuilt from i18n-ja-release-8.5 so the diff shows only this PR's own contribution; lines that #23315 or #23275 also touch are left to those PRs. Verified that the rebuild changes nothing about the end result: merging all fifteen ja PRs produces a byte-identical tree before and after.

This pass also covers a form the earlier detection missed entirely — a bare digit with no space after it (。1パラメータ\gc.max_write_bytes_per_sec`を使用するとfor EN "You can use thegc.max_write_bytes_per_secparameter"). 76 such lines were repaired. Two of them had lost real information:dm/dm-config-overview.md said 「1の最大長はsource-idです」 where the English is "The maximum length of source-idis **32**", andserverless-private-link-connection-to-amazon-msk.mdhad lost the "SASL" ofSASL/SCRAM`.

Several instances were carrying wrong technical information:

file	was	now
tiflash/tiflash-configuration.md ×2	値が 1 から[0.0, 1.0)の範囲 / [0.0, 1.0)から10000000000000の範囲	[0.0, 1.0)の範囲 — the invented bounds are not in the English
predicate-push-down.md	述語は…a < 1に簡略化されて TiKV にプッシュダウンされます	…プッシュダウンされることはありません — EN is "the predicate is not like case 2"; the old text also contradicted its own next sentence
faq/monitor-faq.md	extraレプリカが不足していること	余分なレプリカが存在すること
tiflash/tiflash-alert-rules.md ×3	…から提供されました	PingCAP またはコミュニティからサポートを受ける。
transaction-overview.md	最大値はtxn-total-size-limitで、1 TB です	txn-total-size-limitの最大値は 1 TB です
tune-tikv-thread-performance.md	RaftstoreRaftstore数	Raftstoreスレッド数

Also fixed, same pipeline, no digit involved: 7 occurrences of 「〜をビュー。」 (EN imperative "View X" left as a bare noun, not a sentence) — e.g. `TIDB_TRX`テーブルをビュー: → `TIDB_TRX`テーブルを確認します:; and migrate-large-mysql-to-tidb.md where the file and directory spans were swapped (`metadata`ディレクトリにある`${data-path}`ファイル → `${data-path}`ディレクトリにある`metadata`ファイル).

How it was checked

984 candidate sites were extracted, then every one was cross-checked against release-8.5 before editing — 760 turned out to be genuine numbers (「手順 3」,「16 進数」,「2 進対数スケール」, version/step/layer numbers, region and instance IDs) and were left untouched.

Mechanical verification of the result:

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

Scope note

Together with #23315 this closes the bare-digit defect class. The sweep repeatedly surfaced a different, pervasive artifact — a particle dropped right after a code span (`header`が`true`場合, `stream_count` 8 です) — which is only partially covered by #23272 / #23273 and would need its own pass.

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): follow-up to i18n(ja): restore text dropped by the translation pipeline #23315; 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: 1e8737d3-ff92-4b3d-a04c-3e6added0c05

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