release notes, perf-tuning: fix gPRC typo to gRPC (#23604)

[ti-chi-bot]

This is an automated cherry-pick of #23604

What is changed, added or deleted? (Required)

Fixes a recurring misspelling of "gRPC" as "gPRC" across several release notes and the performance tuning guide:

• releases/release-2.0.6.md
• releases/release-4.0.16.md
• releases/release-5.0.6.md
• releases/release-5.1.4.md
• releases/release-6.1.0.md
• releases/release-6.1.3.md
• performance-tuning-methods.md (3 occurrences)

Found while reviewing CodeRabbit feedback on JA translation PR #23599 — the JA translations correctly mirrored this EN typo, so fixing it at the source here instead of diverging the translation.

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

• master (the latest development version)

What is the related PR or file link(s)?

N/A

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 multiple instances of the “gPRC” typo to “gRPC” across performance tuning documentation and release notes.
  • Improved wording by hyphenating “rate-limiting” where appropriate.
  • No functional or behavior changes.

[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 icemap 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: c4154248-8df1-438b-bcb8-fb0b90c4b2ab

📥 Commits

Reviewing files that changed from the base of the PR and between f5faab8 and e89059d.

📒 Files selected for processing (7)

• performance-tuning-methods.md
• releases/release-2.0.6.md
• releases/release-4.0.16.md
• releases/release-5.0.6.md
• releases/release-5.1.4.md
• releases/release-6.1.0.md
• releases/release-6.1.3.md

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

---

📝 Walkthrough

Walkthrough

This documentation-only change corrects gPRC to gRPC in performance tuning guidance and release notes. It also changes “rate limiting” to “rate-limiting” in two release notes.

Changes

Documentation terminology corrections

Layer / File(s)	Summary
Performance tuning terminology performance-tuning-methods.md	Corrects three gPRC typos in metric and optimization descriptions.
Release note terminology releases/release-2.0.6.md, releases/release-4.0.16.md, releases/release-5.0.6.md, releases/release-5.1.4.md, releases/release-6.1.0.md, releases/release-6.1.3.md	Corrects gPRC typos and hyphenates “rate limiting” in the affected release notes.

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

Merge Risk: ⚪ Minimal · up to e8905

This change corrects gRPC terminology and minor grammar in performance guidance and release notes without changing product behavior. The documentation updates preserve their existing meaning and are ready to merge.

Suggested reviewers: qiancai

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the affected release notes and performance-tuning documentation and states that the gPRC typo is corrected to gRPC.
Description check	✅ Passed	The description explains the documentation-only changes, lists the affected files, identifies the applicable version, and provides the related PR context. The description is mostly complete, although …
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 documentation-only changes, lists the affected files, identifies the applicable version, and provides the related PR context. The description is mostly complete, although it omits the AI agent involvement section and does not select v8.5 despite the stated release-8.5 cherry-pick objective.

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

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