i18n(ja): fix dropped/duplicated particles in backported release-note bullets

[yahonda]

What is changed, added or deleted? (Required)

Found while reading through release notes: several bullets (mostly backported bug-fix descriptions appearing identically across multiple release branches) had dropped or duplicated particles, or a particle choice that subtly misstated the relationship EN describes.

Fixed:

• Missing する verb connecting "output the log" to "problem" in a stats-loading bullet, across 4 files (release-6.5.10.md, release-7.1.6.md, release-7.5.2.md, release-8.1.0.md)
• Missing に particle after IndexLookup in release-7.4.0.md's cost-model bullet
• Duplicated と/で particle in release-7.5.3.md's REMOVE PARTITIONING bullet (sibling release-8.2.0.md already had it correct)
• の→における particle fix for the Longlong overflow-in-predicates bullet across 4 files (release-6.5.10.md, release-7.1.6.md, release-7.5.2.md, release-8.1.1.md), matching the already-correct sibling in release-8.2.0.md and the established corpus convention for "type error in X" bullets

Each fix was verified against the corresponding EN source in release-8.5, using the issue/PR number as an anchor and cross-checking sibling occurrences of the same backported bug across release branches.

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

• 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):

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

Summary by CodeRabbit

• Documentation
  • Corrected Japanese wording and grammar across multiple release-note documents.
  • Clarified descriptions for TiDB bug fixes involving Longlong overflow, synchronous statistics loading, and ALTER TABLE ... REMOVE PARTITIONING.
  • Improved wording in the cost-model improvement entry related to IndexLookup.
  • No product functionality, behavior, or public interfaces were changed.

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Team

Run ID: ac41dc87-76e9-4a69-9372-0f800a839f2a

📥 Commits

Reviewing files that changed from the base of the PR and between 32de109 and fc61251.

📒 Files selected for processing (6)

• releases/release-6.5.10.md
• releases/release-7.1.6.md
• releases/release-7.4.0.md
• releases/release-7.5.2.md
• releases/release-7.5.3.md
• releases/release-8.1.1.md

Included review availability: Your plan provides up to 4 included reviews per hour; 1 remains after this review.

---

📝 Walkthrough

Walkthrough

The PR corrects Japanese wording in TiDB release notes for versions 6.5.10 through 8.1.1. It changes nine text lines across six release-note documents. No functional or structural changes are included.

Changes

Release note corrections

Layer / File(s)	Summary
Japanese release-note wording updates releases/release-6.5.10.md, releases/release-7.1.6.md, releases/release-7.4.0.md, releases/release-7.5.2.md, releases/release-7.5.3.md, releases/release-8.1.1.md	Corrects Japanese grammar and wording in TiDB bug-fix and improvement descriptions, including Longlong overflow, statistics loading, IndexLookup, and ALTER TABLE ... REMOVE PARTITIONING entries.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Merge Risk: ⚪ Minimal · up to fc612

This change corrects Japanese release-note wording only and introduces no product behavior changes or outstanding merge-readiness risk.

Suggested reviewers: qiancai

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the Japanese localization changes and the primary issue: dropped or duplicated particles in backported release-note bullets.
Description check	✅ Passed	The description is detailed and relevant. It explains each wording correction, affected files, verification method, AI involvement, and target Japanese 8.5 documentation branch. The related-link field…
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 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-09-03 03:38:04.672246993 +0000 UTC m=+1336919.843341099: ☑️ agreed by qiancai.

[coderabbitai]

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.