i18n(ja): fix translation defects in the v7.5.x and v7.6.0 release notes

[yahonda]

What is changed, added or deleted? (Required)

Fixes translation defects in the Japanese release notes for v7.5.0 to v7.6.0 (9 files; v7.5.8 had none). This is the second half of round 4 of the releases/ review; v7.0.0 to v7.4.0 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

• 7.6.0:
  • L16: 「数十万から数十万」 → 「数万から数十万」 ("tens to hundreds of thousands").
  • L408: "non-partitioned table" was rendered as a partitioned table.
  • Swapped identifiers in L36 (br/--granularity), L235 (ANALYZE/scan), L385 (CHECK/ENFORCED), and L403 (ANALYZE TABLE/WITH 0 TOPN).
  • Scrambled L292, L371, L374, and L449.
• 7.5.x:
  • "Store messages" was read as the verb "save" (5 places).
  • "Restarting TiKV due to waiting for the log" became "restart in order to wait" (4 places).
  • 7.5.1 L201: the ALTER TABLE ... MODIFY COLUMN ... NOT NULL cause.
  • 7.5.4 L58: the Sort spill condition.
  • 7.5.3 L97: "for more than 500 ms".
  • 7.5.0: "wide tables" became 「テーブルサイズが大きい」.
• Broken contributor handles: 「D3ハンター」 and 「金星の上」 (7.5.1) → @[D3Hunter] and @[overvenus]; @@[afeinberg] and a missing @ (7.6.0).
• Mistranslations: RU was rendered as 「ロシア」 (7.5.1 L36), plus 2人のDDL所有者, 感度調整, 印刷, and やり直しモジュール.
• 7.5.7 L20: the list of new TiKV configuration items was scrambled around a colon. It is rebuilt in the EN order with the same links.

Glossary and literals

• Stale Read → ステイル読み取り. Leader stays in English, and so do Resolved TS, Syncpoint, Connection Count, Active PD Follower, a Grafana metric name, an error message, and **barrier-ts**.
• @[hi-rustin] as in EN.

Particles and Markdown

• Restores particles dropped after links or backticks (about 50 sites); removes stray particles, >, a duplicated word, and backticks inside issue-link text.

Not changed: lines that #24151 also changes, or lines next to them (7.5.4 L96 and 7.5.6 L69 will be fixed after #24151 is merged); Online Unsafe Recovery naming; and 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

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 Japanese release notes for TiDB 7.5.0–7.6.0 with corrections to wording, terminology, grammar, links, and attributions.
  • Clarified descriptions of performance highlights, compatibility changes, configuration settings, improvements, and bug fixes, including table-creation scale, LOAD DATA transaction behavior, TiKV slow logs, and reported issue details.
  • These edits update the release-note descriptions; they do not change product behavior.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: pingcap/docs/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: a152a9ad-552b-4248-a5a6-09a38e59d7cd

📥 Commits

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

📒 Files selected for processing (9)

• releases/release-7.5.0.md
• releases/release-7.5.1.md
• releases/release-7.5.2.md
• releases/release-7.5.3.md
• releases/release-7.5.4.md
• releases/release-7.5.5.md
• releases/release-7.5.6.md
• releases/release-7.5.7.md
• releases/release-7.6.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.

---

📝 Walkthrough

Walkthrough

Release notes for TiDB 7.5.0 through 7.6.0 receive wording, terminology, attribution, and link corrections. Some entries clarify the described scenarios, conditions, and settings. No implementation behavior changes.

Changes

Release note corrections

Layer / File(s)	Summary
Wording and terminology corrections releases/release-7.5.*.md, releases/release-7.6.0.md	The release notes correct Japanese and English wording, terminology, attributions, and links. Several entries clarify the described performance scenarios, compatibility details, configuration settings, and reported fixes.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to e897f

The changes are release-note wording only, and no material factual error was established in the operational claims checked. No actionable merge-blocking risk remains.

Architecture Summary

Architecture risk: 🔵 Low · up to e897f

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

Before / after behavior

• observed — Modified behavior in releases/release-7.5.0.md: The highlights table changes the performance scenario from large tables to wide tables, fixes DXF link placement and an extra ADD, corrects duplicated wording, and repairs the resource-control link. The stated maximum improvement remains 94%.
• observed — Modified behavior in releases/release-7.5.0.md: The DXF description now says that only one TiDB node could execute a DDL task at a time before v7.1.0, rather than saying only one TiDB node could execute tasks concurrently.
• observed — Modified behavior in releases/release-7.5.0.md: The performance note changes the scenario associated with the reported maximum 94% improvement from large tables to wide tables.
• observed — Modified behavior in releases/release-7.5.0.md: The DM Binlog Filter text corrects the DROP COLUMN clause and separates the continuous-data-validation item from the preceding explanation. The validation entry’s pre-v7.5.0 description is corrected to state that the feature ensures consistency during replication from DM to downstream.

🚥 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 affected v7.5.x and v7.6.0 release notes.
Description check	✅ Passed	The description explains the changes, affected version branch, related references, and AI involvement. It provides substantial detail and addresses the required template sections.
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

Warning

Some tools did not complete. Review the errors below.

🔧 LanguageTool

LanguageTool checks are incomplete because the process-local organization character budget was exhausted. Remaining chunks and files were skipped; findings from completed checks are retained.

---

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

[qiancai]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

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