i18n(ja): unify "plan cache" katakana term (remove stray space) in sql-prepared-plan-cache.md - #23297
Conversation
|
Skipping CI for Draft Pull Request. |
|
[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 Japanese translation of "plan cache" by removing the space (changing "プラン キャッシュ" to "プランキャッシュ") in the sql-prepared-plan-cache.md file. The review feedback correctly identifies several minor grammatical issues and typos in the Japanese text, such as missing particles ("を") and unnatural phrasing ("ページ目で" instead of "ページで"), which should be addressed to improve readability.
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.
834eaa8 to
dbfbe80
Compare
|
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:
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
f35f8d1 to
e672c61
Compare
10fa781 to
a28b596
Compare
The file mixed プラン キャッシュ (with a space) and プランキャッシュ (no space) for the same term. Normalizes all 10 spaced occurrences to the no-space form already used in the other 25 places in the file (and the repo-wide convention). The grammatically distinct プランのキャッシュ (4 occurrences) and the English "Plan Cache" (in metric names) are intentionally left unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by other open ja PRs. Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
a28b596 to
9164851
Compare
[LGTM Timeline notifier]Timeline:
|
What is changed, added or deleted? (Required)
Unifies the Japanese term for "plan cache" in
sql-prepared-plan-cache.md. The file mixedプラン キャッシュ(with a space) andプランキャッシュ(no space) for the same term. This normalizes all 10 spaced occurrences to the no-space form already used in the other 25 places in the file, which is also the repo-wide convention (331 vs 75).Intentionally left unchanged:
プランのキャッシュ("the plan's cache", 4 occurrences).Queries Using Plan Cache OPS).This is a Japanese (ja) translation-only fix; no English source content is changed. It follows up on a gemini-code-assist review comment on PR #23294.
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?
Note on scope
A few of the lines in this PR also carry a fix that belongs to one of the sibling ja PRs. Where a later sweep found damage on a line this PR already edits, the fix was applied here rather than duplicated into another PR — otherwise the two PRs would conflict. So a small number of lines go beyond the scope stated above, for example:
Here the stray
1(a translation-tool placeholder) and the word order were repaired alongside this PR's particle insertion.All fifteen ja PRs were verified to merge cleanly in any order (105 pairwise merges, 0 conflicts).