i18n(ja): unify Load Base Split proper-noun naming

[yahonda]

What is changed, added or deleted? (Required)

The Load Base Split feature's own page (configure-load-base-split.md)
uses スプリット in its title and body, but 4 cross-references to the
same feature name used 分割 instead:

• TOC.md
• tikv-configuration-file.md
• releases/release-6.2.0.md
• releases/release-5.0.0.md

This PR unifies these noun-phrase references (link text, feature name
mentions) to スプリット to match the feature's own page.

Left untouched: release-5.0.0.md's separate "データが分割できない"
(data cannot be split) generic verb phrase in the same heading — unlike
the noun-phrase usage, スプリットできない reads awkwardly as a verb
conjugation, so it stays as 分割 there.

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

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated Japanese terminology for load-based splitting to use “ロードベーススプリット” consistently across the table of contents, configuration documentation, and release notes.
  • Link destinations and functionality 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 qiancai 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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 4a66943e-b370-4ff1-9152-07db507bd03c

📥 Commits

Reviewing files that changed from the base of the PR and between 7236ee2 and 55305ad.

📒 Files selected for processing (3)

• TOC.md
• releases/release-5.0.0.md
• tikv-configuration-file.md

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

---

📝 Walkthrough

Walkthrough

The Japanese terminology for load-based split was updated in the table of contents, release notes, and TiKV configuration documentation. Links, anchors, and surrounding content remain unchanged.

Changes

Japanese terminology update

Layer / File(s)	Summary
Update load-based split terminology TOC.md, releases/release-5.0.0.md, releases/release-6.2.0.md, tikv-configuration-file.md	Updated Japanese references from 「ロードベース分割」 to 「ロードベーススプリット」. Existing links, anchors, and surrounding content remain unchanged.

Priority: ⬇️ Low

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

Change: Other

Suggested reviewers: qiancai

Merge Risk: ⚪ Minimal · up to 55305

The terminology updates preserve links, anchors, and surrounding content, so the change is mergeable.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the Japanese internationalization change and the unification of Load Base Split terminology.
Description check	✅ Passed	The description explains the terminology changes, lists the affected files, identifies the applicable documentation version, records AI involvement, and includes the required template sections. The op…
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]

[LGTM Timeline notifier]

Timeline:

• 2026-09-15 13:33:39.243541324 +0000 UTC m=+125665.181198908: ☑️ agreed by qiancai.