i18n(ja): fix translation defects in the v5.3.x and v5.4.x release notes and the release index

[yahonda]

What is changed, added or deleted? (Required)

Fixes translation defects in the Japanese release notes for v5.3.0 to v5.4.3, plus releases/_index.md and releases/versioning.md (10 files). This is the second half of round 6 of the releases/ review. releases/release-timeline.md was reviewed and had no defects. I checked each item against EN (release-8.5) and against resources/terms-en-ja.md.

Meaning fixes

• 5.4.0 L410 and 5.3.0 L280: "the disk is fully written" (disk full) became "writing to the disk completed" or a generic write error.
• 5.4.0 L273: the TiCDC performance-impact sentence was reversed.
• 5.4.0 L265: "source-consuming" was rendered literally. EN means resource-consuming.
• Scrambled sentences:
  • 5.4.0: L60, L170, and L232.
  • 5.3.1: L48, L106, and L120.
  • 5.4.1: L69 and L168.
• Swapped identifiers: 5.4.0 L397 (minio/'/').
• Truncated sentences: 5.3.0 L226 and 5.4.0 L129.
• 5.3.4 L50: an unclosed parenthesis with the issue link inside the sentence.
• versioning.md: "has the form of X.Y.Z" became "starts from".

Literals

• Translated version strings are restored: 「4.0.0-ベータ.1」, 「1.1 アルファ」, and the _index.md summary (4.0.0-beta, 3.0.0-beta.1, ...).
• The warning message |Warning | 1292 | Truncated incorrect xxx: 'xx', the error message "GC life time is shorter than transaction duration", and the Continuous Profile UI label stay in English.
• So do TSO/PD Follower Proxy, Scatter Region, Resolve Locks, Region syncer, slow score, checkpointTs, and the Apply/Store thread pools. Lowercase "learner" is ラーナー.

Markdown

• 5.4.0 L242: a raw <a href="/character-set-and-collation.md"> inside a bold heading is restored to the EN Markdown link.
• Restores particles dropped after backticks and <code> spans; removes duplicated words and < artifacts.

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
  • Updated release notes from TiDB 5.3.0 through 5.4.3 with clearer Japanese wording for compatibility details, features, improvements, and fixes. The listed product changes remain unchanged.
  • Clarified version-format guidance and standardized beta-version labels.

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

📝 Walkthrough

Walkthrough

This pull request edits Japanese release notes for TiDB 5.3.0–5.4.3 and updates release-index and versioning text. The changes clarify selected technical descriptions and terminology. No implementation code or public declarations change.

Changes

Release documentation

Layer / File(s)	Summary
TiDB 5.3 release notes releases/release-5.3.0.md, releases/release-5.3.1.md, releases/release-5.3.2.md, releases/release-5.3.4.md	The notes clarify selected compatibility, improvement, and bug-fix descriptions. They also correct Japanese wording and technical terminology.
TiDB 5.4 release notes releases/release-5.4.0.md, releases/release-5.4.1.md, releases/release-5.4.2.md, releases/release-5.4.3.md	The notes clarify selected settings, conditions, and bug-fix descriptions. They also correct Japanese wording and technical terminology.
Release index and versioning text releases/_index.md, releases/versioning.md	The release index uses beta version identifiers. The versioning text clarifies the X.Y.Z format and patch-version numbering, and uses English Beta and Alpha labels in historical examples.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: 🔵 Low · up to e177d

A 5.3.0 release note blurs the disk condition that can trigger a TiKV panic with the later disk-full response. Clarifying the wording is a bounded documentation fix; the PR is otherwise mergeable.

Architecture Summary

Architecture risk: 🔵 Low · up to e177d

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

Before / after behavior

• observed — Modified behavior in releases/_index.md: The summary now uses version identifiers for the listed beta releases instead of Japanese beta labels.
• observed — Modified behavior in releases/release-5.3.0.md: Corrects the temporary-table system-variable descriptions and clarifies the optimizer’s 80% changed-row threshold, TSO Follower Proxy behavior, and temporary-table size limit: exceeding that limit produces an error.
• observed — Modified behavior in releases/release-5.3.0.md: Clarifies that TiCDC and BR support global temporary tables from v5.3.0, and that older versions can produce downstream table-definition errors. Corrects the description of restored clusters and the warning text for invalid system-variable values; from v5.3.0, those values return success with a warning rather than an error.
• observed — Modified behavior in releases/release-5.3.0.md: Corrects Japanese wording in the auto-analyze timing, DM upgrade, and Prometheus deployment notes. The described behavior and version values are unchanged.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Title check	✅ Passed	The title clearly identifies the Japanese translation fixes and the affected release notes and index. It is somewhat long, but remains specific and relevant.
Description check	✅ Passed	The description explains the changes, affected versions, related references, and AI involvement. It also addresses the applicable checklist items and provides enough detail for review.

✨ 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: b07c6081-cbd6-4c82-a1f5-ccecc085511b

📥 Commits

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

📒 Files selected for processing (10)

• releases/_index.md
• releases/release-5.3.0.md
• releases/release-5.3.1.md
• releases/release-5.3.2.md
• releases/release-5.3.4.md
• releases/release-5.4.0.md
• releases/release-5.4.1.md
• releases/release-5.4.2.md
• releases/release-5.4.3.md
• releases/versioning.md

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