i18n(ja): fix translation defects in the v3.0-beta to v3.0.14 release notes

[yahonda]

What is changed, added or deleted? (Required)

Fixes translation defects in the Japanese release notes for v3.0-beta to v3.0.14 (20 files). This is the first half of round 8 of the releases/ review; v3.0.15 to v3.1.2 are in a separate PR. I checked each item against its EN bullet (release-8.5) and against resources/terms-en-ja.md.

Meaning and number fixes

• 3.0-beta L69: "MySQL 320 handshake protocol" was rendered as 3.20. 320 is the protocol identifier (HandshakeResponse320).
• 3.0.8:
  • "the memory might leak" became "memory occurs".
  • "the binlog Prewrite time" became a count (回).
  • The fix and the bug were merged in the system_time_zone item.
• 3.0.0-rc.2:
  • "Allow … to contain no OrderBy clause" became "make it not contain".
  • "the default value of tidb_disable_txn_auto_retry" had the variable as the old value.
• 3.0.1: SetVar as the agent; SELECT … FOR UPDATE not using the correct TSO.
• 3.0.4: the file descriptor leak item read as current behavior. It is now a fixed bug.
• 3.0.14: "the update statement that contains a view and does not update the view".
• Feature additions that read as instructions to the reader: 3.0.3, 3.0.4, 3.0.8, 3.0.0-rc.3, 3.0.2.
• Many identifiers that had been moved to the end of a sentence are back in place:
  • 3.0.0-rc.1 L33, L84, and L89.
  • 3.0-ga L45 and L163.
  • 3.0.1 L67.
  • 3.0.2 L95.
  • 3.0.3 L71.
  • 3.0.9 L40.
  • 3.0.12 L38.

Wrong-domain words

• 攻撃 (aggression) → 集計.
• 執行者 → エグゼキューター.
• 時間外 → タイムアウトしていない.
• デグレード → ダウングレード.
• 表現 → 式.
• 分数 → 小数部.
• 演算子 → オペレーター (PD operators).
• 優先される → 横取り（プリエンプト）される.
• 未使用 → 未消費.
• 選挙 → 選出.
• 領域 → リージョン.

Literals

• These stay in English:
  • RaftStore/raftstore, Apply, failpoint.
  • The trouble_shooting dashboard, Overview, Disk Latency.
  • The error message "Incorrect arguments to NAME_CONST", and remove-tombstone.
  • Beta.1 in a heading.
• 3.0.10 L47: a stray "ix " copied from an EN typo is removed.

Particles

• Restores particles dropped after links or backticks (about 120 sites).

Not changed:

• Existing 「パニック」 and the established 「ラーナー」.
• Some Grafana dashboard names in v3.0.0-rc.1 and v3.0.2.
• The order and spacing of handles and issue links.

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, i18n(ja): fix translation defects in the v5.0.x to v5.2.x release notes #24164, i18n(ja): fix translation defects in the v5.3.x and v5.4.x release notes and the release index #24165, i18n(ja): fix translation defects in the v4.0.0-beta to v4.0.9 release notes #24171, i18n(ja): fix translation defects in the v4.0.10 to v4.0.16 release notes #24172

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

[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 40 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: 41d10b74-a1fc-4579-8c74-9e80e41d4a4c

📥 Commits

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

📒 Files selected for processing (20)

• releases/release-3.0-beta.md
• releases/release-3.0-ga.md
• releases/release-3.0.0-beta.1.md
• releases/release-3.0.0-rc.1.md
• releases/release-3.0.0-rc.2.md
• releases/release-3.0.0-rc.3.md
• releases/release-3.0.1.md
• releases/release-3.0.10.md
• releases/release-3.0.11.md
• releases/release-3.0.12.md
• releases/release-3.0.13.md
• releases/release-3.0.14.md
• releases/release-3.0.2.md
• releases/release-3.0.3.md
• releases/release-3.0.4.md
• releases/release-3.0.5.md
• releases/release-3.0.6.md
• releases/release-3.0.7.md
• releases/release-3.0.8.md
• releases/release-3.0.9.md

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

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