i18n(ja): reword support-entries as a UX flow term

[yahonda]

What is changed, added or deleted? (Required)

tidb-cloud/releases/release-notes-2023.md: EN "support entries" (referring to UI entry points to the support feature, e.g. a menu icon) had been borrowed literally as katakana (サポートエントリ / サポート エントリ, also inconsistently spaced across the file's 2 occurrences). This reads ambiguously in Japanese since エントリ commonly means "a data record" in IT usage, not "an access point." Reworded both sites to サポート導線, an established Japanese UX term for a user's path/route to a feature — this also resolves the spacing inconsistency between the two occurrences.

1 file changed, 2 sites.

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
  • Updated Japanese terminology in the 2023 TiDB Cloud release notes for support navigation references.
  • No functional changes or product behavior impact.

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

Warning

Review limit reached

Next included review available in 9 minutes.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: d61867ea-6aee-4bdf-a83a-e7ae61420f70

📥 Commits

Reviewing files that changed from the base of the PR and between 482ce0e and 34dcf62.

📒 Files selected for processing (1)

• tidb-cloud/releases/release-notes-2023.md

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 2e579b3d-e629-4ad5-93d9-034b0203fad6

📥 Commits

Reviewing files that changed from the base of the PR and between a349332 and 482ce0e.

📒 Files selected for processing (1)

• tidb-cloud/releases/release-notes-2023.md

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

---

📝 Walkthrough

Walkthrough

The 2023 TiDB Cloud release notes replace two Japanese support-entry terms with “サポート導線” in the July 25 and July 4 console change entries.

Changes

Release note terminology updates

Layer / File(s)	Summary
Update support pathway wording tidb-cloud/releases/release-notes-2023.md	The July 25 and July 4 console change entries use “サポート導線” instead of the previous support-entry terms.

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

Merge Risk: ⚪ Minimal · up to 482ce

This PR makes a localized Japanese terminology correction in release notes with no actionable merge-blocking risk remaining after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the terminology change from support-entry wording to a UX flow term.
Description check	✅ Passed	The description explains the two terminology changes, affected file, rationale, target Japanese TiDB 8.5 documentation branch, and AI involvement. Optional reference links are blank, but the required …
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.

Full details: Description check

Explanation

The description explains the two terminology changes, affected file, rationale, target Japanese TiDB 8.5 documentation branch, and AI involvement. Optional reference links are blank, but the required content is complete.

Full details: Docstring Coverage

Explanation

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 files. (1 skipped: 1 unsupported.)

✨ 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 overvenus 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-08-28 08:23:06.888209816 +0000 UTC m=+835622.059303962: ☑️ agreed by qiancai.