Fix tool name capitalization for product names to prevent mistranslation#23043
Fix tool name capitalization for product names to prevent mistranslation#23043yahonda wants to merge 4 commits into
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Code Review
This pull request standardizes the capitalization of various component names (such as Syncer, Pump, Lightning, and TiFlash) across multiple documentation files. The review feedback provides actionable suggestions to further align the text with the style guide, including converting passive voice to active voice, writing in the second person ("you"), correcting grammatical issues, and ensuring consistent terminology (e.g., using "parameter" instead of "item" and capitalizing join types).
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
242fd24 to
49e188b
Compare
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
[LGTM Timeline notifier]Timeline:
|
What is changed, added or deleted? (Required)
Changed lowercase product names to proper capitalization in prose text to prevent mistranslation during localization (e.g., Japanese translation):
Note: 'syncer' is not changed as it is not maintained and should remain lowercase.
Command line references, file names, URLs, paths, and configuration values remain unchanged.
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?