releases: fix typos and a mistranslation-derived wording issue in release notes

[yahonda]

What is changed, added or deleted? (Required)

Fixes 3 defects in English release notes found while reviewing Japanese translation PRs #23598/#23599:

• INFORMSTION_SCHEMA -> INFORMATION_SCHEMA in releases/release-5.4.3.md
• OPRDERBY -> ORDER BY in releases/release-6.5.7.md, releases/release-7.1.4.md, releases/release-7.5.1.md (same bullet, duplicated across 3 files for issue #49377)
• releases/release-5.0.6.md: "scanning stock data" -> "scanning existing data". The Chinese source (docs-cn) uses 存量数据, an economics term meaning "stock" as opposed to "flow/incremental" data; the literal English rendering "stock data" reads as financial stock-market data to English readers and is misleading. Confirmed against the linked issue (CDC cloud: [CDC:ErrMetaListDatabases][tikv:9006]GC life time is shorter than transaction duration, transaction starts at 2021-08-05 16:54:32.127 +0800 CST, GC safe point is 2021-08-05 17:25:38.127 +0800 CST"] tiflow#2470), which describes a resumed changefeed's initial/backlog scan hitting a GC-related failure — "existing data" (as opposed to newly-incoming/incremental data) matches that context.

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

• v9.0 (Development milestone)
• v8.5 (LTS)
• v8.1 (DMR)
• v7.5 (LTS)
• v7.1 (LTS)
• v6.5 (LTS)
• v6.1 (LTS)
• v5.4

Summary by CodeRabbit

• Documentation
  • Corrected terminology and typos across release notes, including “scanning existing data,” INFORMATION_SCHEMA, and ORDER BY.
  • Clarified descriptions of fixes involving TiKV garbage collection during long scans and invalid LIMIT/ORDER BY clauses in nested UNION queries.

[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

[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

[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: 7b9ddbba-967b-44fb-834c-ad36c4aca81d

📥 Commits

Reviewing files that changed from the base of the PR and between aa389a3 and 1e65cb2.

📒 Files selected for processing (5)

• releases/release-5.0.6.md
• releases/release-5.4.3.md
• releases/release-6.5.7.md
• releases/release-7.1.4.md
• releases/release-7.5.1.md

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

---

📝 Walkthrough

Walkthrough

The release notes update one TiCDC description and correct terminology in four TiDB bug-fix entries. No code or public declarations change.

Changes

Release note corrections

Layer / File(s)	Summary
Release note text updates releases/release-5.0.6.md, releases/release-5.4.3.md, releases/release-6.5.7.md, releases/release-7.1.4.md, releases/release-7.5.1.md	The notes replace “scanning stock data” with “scanning existing data”, correct INFORMSTION_SCHEMA to INFORMATION_SCHEMA, and correct OPRDERBY to ORDER BY.

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

Merge Risk: ⚪ Minimal · up to 1e65c

This updates release-note wording and corrects typos without changing product behavior. No current merge-readiness risk remains.

Suggested reviewers: qiancai

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the release-note typo and wording corrections across the changed files.
Description check	✅ Passed	The description explains all three change categories and identifies the affected release-note files. It also selects the applicable v8.5 version. Optional template sections, including related links an…
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

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