i18n(ja): fix mistranslated KILL heading and inconsistent high-concurrency term in release notes - #23513
Conversation
|
Skipping CI for Draft Pull Request. |
|
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 |
|
[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 |
a796a65 to
37ad49d
Compare
…rency term in release notes
- privilege-management.md: restore the literal SQL statement name
`### KILL {#kill}`, which had been mistranslated as the verb 殺す
("to kill" as in murder). The body text and
sql-statements/sql-statement-kill.md already use `KILL` as-is, so
this heading was the odd one out.
- 6 release notes files: fix 高同時読み取りシナリオ/高同時シナリオ to
高同時実行読み取りシナリオ/高同時実行シナリオ. These translate the
English "high-concurrency read scenarios" / "high concurrent
scenarios", and 高同時実行 (not bare 高同時) is the natural, standard
translation for "high concurrency" used everywhere else in the docs.
37ad49d to
e502637
Compare
[LGTM Timeline notifier]Timeline:
|
What is changed, added or deleted? (Required)
privilege-management.md: restore the literal SQL statement name### KILL {#kill}, which had been mistranslated as the verb 殺す ("to kill" as in murder). The body text andsql-statements/sql-statement-kill.mdalready useKILLas-is, so this heading was the odd one out.release-8.1.0.md,release-6.5.10.md,release-7.1.6.md,release-7.5.2.md,release-3.0.0-rc.3.md,release-2.1.13.md): fix 高同時読み取りシナリオ/高同時シナリオ to 高同時実行読み取りシナリオ/高同時実行シナリオ. These translate the English "high-concurrency read scenarios" / "high concurrent scenarios", and 高同時実行 (not bare 高同時) is the natural, standard translation for "high concurrency" used everywhere else in the docs.Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?