i18n(ja): fix translation defects in the v5.0.x to v5.2.x release notes

[yahonda]

What is changed, added or deleted? (Required)

Fixes translation defects in the Japanese release notes for v5.0.0-RC to v5.2.4 (16 files). This is the first half of round 6 of the releases/ review; v5.3.x, v5.4.x, and the release index are in a separate PR. I checked each item against its EN bullet (release-8.5) and against resources/terms-en-ja.md.

Meaning fixes

• 5.1.0 L271–L272: the privileges were swapped. REPLACE now requires both INSERT and DELETE privileges, not the reverse.
• 5.0.0 L24: the import direction was reversed ("import from").
• 5.0.1: "within 10 seconds" lost the number.
• 5.1.1: "more than 4 replicas" became "4 or more".
• 5.0.3 L120: "not nullable" became "not a NULL value".
• 5.2.1 L16: "caused by the wrong execution plan" was dropped.
• 5.2.2 L3: "partition pruning" became "partition function".
• Swapped or scrambled identifiers:
  • 5.0.0: L271, L433, L434, and L467.
  • 5.1.5: L44, L49, L105, and L107.
  • 5.2.0: L260.
  • 5.2.4: L52, L82, and L171.
  • 5.0.4: L187.
  • 5.1.1: L46.
  • 5.2.2: L70.
• Completed changes that read as instructions to the reader (5.0.0, 5.1.0, 5.2.0).

Wrong-domain words

• 関連号 → 関連問題 (11 places).
• 事業者 → 演算子.
• 異性体 → 異種.
• 未署名 → 符号なし.
• 移籍 → 転送.
• 左悲観的ロック → 残存する悲観的ロック.
• 連合 / ジョイント / 流出.
• 集約機能 → 集計関数.
• 非同期 → 同期されていない.

Glossary and literals

• These stay in English:
  • Raft, ReadIndex, Leader, and Learner.
  • Joint Consensus, Unified Sorter, Resolve Locks, Region syncer, and backupmeta.
  • Error messages.
• Stale Read → ステイル読み取り; Region → リージョン.

Particles and Markdown

• Restores particles dropped after links or backticks.
• Fixes an unclosed parenthesis (5.1.5) and the missing blank line before a nested Note (5.0.0).
• Fixes < artifacts and backticks inside issue-link text.

Not changed:

• Existing 「パニック」 is kept.
• The Data Migration component name, which is a separate pending term decision.
• The order and spacing of handles.

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, i18n(ja): fix translation defects in the v8.0.0, v8.3.0, and v8.4.0 release notes #24152, i18n(ja): fix translation defects in the v7.0.0 to v7.4.0 release notes #24153, i18n(ja): fix translation defects in the v7.5.x and v7.6.0 release notes #24154, i18n(ja): fix translation defects in the v6.0.0 to v6.4.0 release notes #24157, i18n(ja): fix translation defects in the v6.5.x and v6.6.0 release notes #24158

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
  • Corrected and clarified Japanese wording, terminology, and punctuation across release notes for versions 5.0 through 5.2.
  • Refined descriptions of features, improvements, bug fixes, configuration settings, and compatibility changes; listed behavior and release-note items remain unchanged.

[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 lilin90 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]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 3 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Configuration used: Repository: pingcap/docs/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 4a4b5a15-7c22-4f59-8b8c-4f5c96f5fc93

📥 Commits

Reviewing files that changed from the base of the PR and between f848844 and 087882c.

📒 Files selected for processing (1)

• releases/release-5.0.4.md

📝 Walkthrough

Walkthrough

Japanese release-note wording, terminology, and punctuation were revised across releases 5.0.0-rc through 5.2.4. The changes are documentation edits; no implementation changes are reported.

Changes

Release 5.0 editorial updates

Layer / File(s)	Summary
Release 5.0 editorial updates releases/release-5.0.0-rc.md, releases/release-5.0.0.md, releases/release-5.0.1.md, releases/release-5.0.2.md, releases/release-5.0.3.md, releases/release-5.0.4.md, releases/release-5.0.6.md	The notes revise Japanese wording, terminology, and punctuation across feature and bug-fix entries. The BR backup-and-restore entry is placed under a BR heading.

Release 5.1 editorial updates

Layer / File(s)	Summary
Release 5.1 editorial updates releases/release-5.1.0.md, releases/release-5.1.1.md, releases/release-5.1.2.md, releases/release-5.1.4.md, releases/release-5.1.5.md	The notes revise wording and terminology in feature and bug-fix descriptions. The two REPLACE permission entries now state that REPLACE requires both INSERT and DELETE privileges.

Release 5.2 editorial updates

Layer / File(s)	Summary
Release 5.2 editorial updates releases/release-5.2.0.md, releases/release-5.2.1.md, releases/release-5.2.2.md, releases/release-5.2.4.md	The notes revise wording and terminology. The 5.2.1 entry adds a description of the incorrect execution plan and the shallow schema-column copy associated with the runtime error.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: 🔵 Low · up to f8488

The Japanese 5.0.4 note may confuse readers about which upstream change produces the empty TiCDC Open Protocol value. The correction is localized; this is a bounded documentation risk.

Architecture Summary

Architecture risk: 🔵 Low · up to f8488

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; 16 changed files map to changed impact.

Before / after behavior

• observed — Modified behavior in releases/release-5.0.0-rc.md: The Raft Joint Consensus description changes the Japanese term formatting from “ジョイント コンセンサス” to “Joint Consensus.”
• observed — Modified behavior in releases/release-5.0.0-rc.md: The clustered-index issue reference changes “関連号” to “関連問題.”
• observed — Modified behavior in releases/release-5.0.0-rc.md: The invisible-index issue reference changes “関連号” to “関連問題.”
• observed — Modified behavior in releases/release-5.0.0-rc.md: The issue references for the SQL, transaction, and character-set topics use “関連問題” instead of “関連号.” The pessimistic-transaction description adds the missing particle in its schema-version update wording.

🚥 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 release-note version range.
Description check	✅ Passed	The description explains the changes and their rationale, identifies the target branch, provides related references, and completes the AI-involvement and change-type sections. It is mostly complete ag…
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: 5d4a5e18-c63a-4666-9b7d-8c05908bbfad

📥 Commits

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

📒 Files selected for processing (16)

• releases/release-5.0.0-rc.md
• releases/release-5.0.0.md
• releases/release-5.0.1.md
• releases/release-5.0.2.md
• releases/release-5.0.3.md
• releases/release-5.0.4.md
• releases/release-5.0.6.md
• releases/release-5.1.0.md
• releases/release-5.1.1.md
• releases/release-5.1.2.md
• releases/release-5.1.4.md
• releases/release-5.1.5.md
• releases/release-5.2.0.md
• releases/release-5.2.1.md
• releases/release-5.2.2.md
• releases/release-5.2.4.md

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