i18n(ja): fix Run button mistranslated as a physical-movement verb - #23525
i18n(ja): fix Run button mistranslated as a physical-movement verb#23525yahonda wants to merge 1 commit 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 |
|
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 |
The Run icon/button in the SQL editor was mistranslated as a literal verb meaning to run/dash physically, instead of the noun-form button label used consistently elsewhere in the same files ([実行]). Fixed 6 occurrences across 3 files; a 4th file with the same icon (tidb-cloud-quickstart.md) already had the correct 「実行」 form and needed no change.
d805f44 to
6a77423
Compare
What is changed, added or deleted? (Required)
The Run icon/button in the SQL editor (used in the "run a single statement" instruction, right after an inline SVG run icon) was mistranslated as 走る (the verb "to run/dash" in the physical sense), instead of the noun-form button label
[実行]used consistently for the same button elsewhere in the same files.Fixed 6 occurrences across 3 files:
tidb-cloud/data-service-get-started.md,tidb-cloud/data-service-manage-endpoint.md,tidb-cloud/explore-data-with-chat2query.md. A 4th file with the same inline SVG icon,tidb-cloud/tidb-cloud-quickstart.md, already had the correct「実行」form and needed no change.Verified against EN:
click <svg>...</svg>**Run**.at each corresponding position.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?