i18n(ja): fix translation defects in the v8.0.0, v8.3.0, and v8.4.0 release notes

[yahonda]

What is changed, added or deleted? (Required)

Fixes translation defects in the Japanese release notes for v8.0.0, v8.3.0, and v8.4.0. This is round 3 of the releases/ review (round 1 is #24143 and round 2 is #24148). I checked each item against its EN bullet (release-8.5).

Meaning fixes

• Swapped or scrambled identifiers:
  • 8.0.0: OR/AND in the Index Merge item; the br parameters --load-stats and --tikv-max-restore-concurrency; log/br; SYSDATE()/tidb_sysdate_is_now/1; PLAN REPLAYER/CREATE GLOBAL BINDING/IN(); NULL/EXCHANGE PARTITION; SURVIVAL_PREFERENCES/SHOW CREATE PLACEMENT POLICY; the condition and effect in the snapshot lost caused by GC item.
  • 8.3.0: Selection/IndexRangeScan; YEAR/JSON_TYPE; the two tidb_enable_inl_join_inner_multi_pattern error items; the second sentence about the default value of tidb_analyze_column_options.
  • 8.4.0: the Statement Summary Tables sentence; the filter simplification A → B; scatter-range/scatter-range-scheduler/pd-ctl; ANALYZE/Unknown column ....
• Other meaning fixes:
  • 8.0.0: "goroutine leak" was rendered as a memory leak. "Crash" was dropped. "Clients are not affected" was weakened to "the impact is minimized". "Fails to spill" became "does not spill". "Slow queries" became "query delay". "The number of digits by which to increase the scale" (div_precision_increment) became "whether to increase".
  • 8.4.0: the aes192-ctr key length was dropped from --log.crypter.key. --master-key-crypter-method said the master key is one of the algorithms. The scope of "only" was wrong in the Claim-Check item. "Can be encrypted" became past tense.

Wrong-domain words

• 関数 → 機能 where EN "functions" means capabilities (8.0.0, 8.4.0).
• 証人 → Witness.
• 流出 → スピル.
• 低速ログ → スローログ.
• PD の分解 → 分離.
• ごみ収集 → ガベージコレクション.
• ロックを解除する → ロックを解決する (the target heading is 「ロックを解決する」).
• 領域 → リージョン.
• 自己インクリメント → 単調増加.
• 交通状況のリプレイ → トラフィック再生.
• 散乱 → 分散 / Scatter Region.

Literals kept in English

• Connection Count (Grafana).
• By TABLE / By DB (UI labels).
• Claim-Check.
• Key Management Service (Cloud KMS).
• GLOBAL scope.
• @[hi-rustin] handle text, as in EN.

Particles and Markdown

• Restores particles dropped after links or backticks (about 25 sites).
• Removes text duplicated after a link (8.0.0 L79 and L283).
• Removes stray 。 after handles and inside link text.
• Fixes an unclosed parenthesis (8.4.0 L327) and a missing sentence break (8.0.0 L185).

Not changed: the Data Migration component name (a separate pending term decision), the spacing between handles, and the 8.4.0 ORDER BY "is stuck" item, whose EN wording is unclear.

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• i18n-ja-release-8.5 (TiDB Japanese documentation for TiDB 8.5 versions)

What is the related PR or file link(s)?

• This PR is translated from:
• Other reference link(s): i18n(ja): fix translation defects in the v8.5.x release notes #24143, i18n(ja): fix translation defects in the v8.1.0, v8.1.2, and v8.2.0 release notes #24148

AI agent involvement

• The changes in this PR were primarily made by an AI agent on behalf of the PR author.

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

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated the Japanese 8.0, 8.3, and 8.4 release notes for clarity, terminology, and accuracy.
  • Clarified statistics collection settings for upgraded and new clusters, plus descriptions of cached-table lookups, query controls, traffic replay, TiCDC storage behavior, encryption key sizes, and log-backup recovery.
  • Corrected wording and examples across feature, compatibility, improvement, and bug-fix entries.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated Japanese release notes for versions 8.0.0, 8.3.0, and 8.4.0. The edits correct wording and clarify documented feature details, configuration settings, improvements, compatibility notes, and bug-fix descriptions.

Changes

Release note updates

Layer / File(s)	Summary
Release 8.0.0 notes releases/release-8.0.0.md	Clarifies feature and system-variable descriptions, Lightning conflict strategies, improvements, restore options, and existing bug-fix entries.
Release 8.3.0 notes releases/release-8.3.0.md	Clarifies statistics column-selection defaults, configuration and system-variable descriptions, improvements, compatibility details, and existing bug-fix entries.
Release 8.4.0 notes releases/release-8.4.0.md	Clarifies feature scenarios, Claim-Check behavior, BR encryption key lengths, improvement descriptions, and existing bug-fix details.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~15 minutes

Change: Other

Merge Risk: 🔵 Low · up to 35ffb

The Japanese guidance could lead users to expose the index to other sessions while testing. Correct the wording; the issue is localized and straightforward to fix.

Architecture Summary

Architecture risk: 🔵 Low · up to 35ffb

The change affects 1 system.

Changed systems: releases

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — releases (service) was modified; 3 changed files map to changed impact.

Before / after behavior

• observed — Modified behavior in releases/release-8.0.0.md: 機能一覧表の PD の項目を「分解」から「分離」に修正し、PD のスケジューリング機能の説明を「関数」から「機能」に変更しました。
• observed — Modified behavior in releases/release-8.0.0.md: Titan の共有キャッシュの説明で、設定項目のデフォルト値と blob-cache-size に関する表現を修正しました。
• observed — Modified behavior in releases/release-8.0.0.md: 自動統計収集の優先キューの項目に記載された貢献者名を変更しました。
• observed — Modified behavior in releases/release-8.0.0.md: プランキャッシュの導入文で、重複した「キャッシュ」の表記を修正しました。

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the Japanese translation fixes and the three affected release notes.
Description check	✅ Passed	The description explains the changes, affected branch, related PRs, and AI involvement. It also identifies items left unchanged. The required information is mostly complete.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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

[coderabbitai]

Actionable comments posted: 1

---

ℹ️ Review info

⚙️ Run configuration

• Configuration used: Repository: pingcap/docs/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 448db70f-e021-417c-abdb-724000933b54

📥 Commits

Reviewing files that changed from the base of the PR and between a4dfec7 and 35ffb17.

📒 Files selected for processing (3)

• releases/release-8.0.0.md
• releases/release-8.3.0.md
• releases/release-8.4.0.md

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 1 remain after this review.

[qiancai]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-10-08 07:52:37.89246719 +0000 UTC m=+285567.639698039: ☑️ agreed by qiancai.