i18n(ja): unify inconsistent proxy account term in SQL Proxy Account doc - #23526
Conversation
…ount doc One of four 'No proxy account' entries used a different Japanese word (代理, a generic substitute/proxy term) than its three sibling entries and the rest of the document (プロキシ, matching the established SQL proxy account terminology used throughout).
|
[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 |
[LGTM Timeline notifier]Timeline:
|
What is changed, added or deleted? (Required)
tidb-cloud/sql-proxy-account.mdhas 4 "No proxy account" entries in the SQL proxy account role table. One of them (Organization Billing Manager) used a different Japanese term (代理アカウント, a generic substitute/proxy word) than its 3 sibling entries and the rest of the document (プロキシアカウント, matching the established SQL proxy account terminology used consistently everywhere else in this file). Unified it to プロキシアカウント.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?