i18n(ja): restore literal FLUSH STATUS command name instead of a katakana transliteration - #23528
Conversation
…kana transliteration The link anchor text was transliterated into katakana (フラッシュステータス) instead of keeping the literal SQL statement name FLUSH STATUS, unlike every other reference to this command across the corpus (TOC entries, sql-statement-overview.md), which all keep it as literal SQL syntax.
|
[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 |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
…stead of katakana paraphrases
What is changed, added or deleted? (Required)
In
status-variables.md, the link anchor text for theFLUSH STATUSSQL statement was transliterated into katakana (フラッシュステータス) instead of keeping the literal SQL statement name, unlike every other reference to this command across the corpus (TOC entries,sql-statements/sql-statement-overview.md), which all keep it as literal SQL syntaxFLUSH STATUS.Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?