i18n(ja): miscellaneous review fixes (bit-shift description)#23274
i18n(ja): miscellaneous review fixes (bit-shift description)#23274yahonda wants to merge 9 commits into
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 updates the Japanese documentation for bitwise functions to clarify the description of the left-shift operator. The reviewer suggested a minor improvement to use 'ビット' (bits) instead of '桁' (digits) for better technical accuracy and consistency with the rest of the document.
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.
| `<<`演算子は左シフト演算を実行し、数値のビットを指定された位置数だけ左にシフトし、右側の空いたビットをゼロで埋めます。 | ||
|
|
||
| たとえば、次のステートメントでは、 `1<<n`使用して、バイナリ値`1` `n`位置左にシフトします。 | ||
| たとえば、次のステートメントでは、 `1<<n`を使用して、バイナリ値`1`を左に`n`桁シフトします。 |
There was a problem hiding this comment.
For bit-shift operations, it is technically more accurate to use 'ビット' (bits) instead of '桁' (digits/positions). This also ensures consistency with other terms used in the document (such as 'ビットをゼロで埋めます').
We recommend updating it as follows:
たとえば、次のステートメントでは、 `1<<n`を使用して、バイナリ値`1`を左に`n`ビットシフトします。References
- Technical accuracy and terminology consistency: Using 'ビット' (bits) instead of '桁' (digits) is technically more accurate for bitwise operations and consistent with the rest of the document. (link)
8e3296d to
44d59a1
Compare
44d59a1 to
3ad44d0
Compare
…issing を) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…nce end in release-4.0-ga Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…uning-best-practice (gemini review) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…, spaces, storage, IAM typo) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
3ad44d0 to
4e48177
Compare
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro 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 |
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
EN: "this method is not fully accurate" is a partial negation, but "完全に正確ではありません" reads as a full negation in Japanese (完全に modifying the negation itself). Insert は — 完全には正確ではありません — the standard Japanese device for scoping the negation. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
5ec0e0b to
240f92a
Compare
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- tidb-cloud/sql-concepts.md: 「30 千」 is not Japanese; EN says "30 thousand" -> 3 万. - dr-solution-introduction.md: "second-level RPO" was read as an ordinal (第 2 レベル) instead of a unit of time -> 秒単位の RPO. - notification-2023-09-26-console-maintenance.md: "Scale clusters" kept English word order (スケールクラスター) while every sibling bullet uses クラスターを…する. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
240f92a to
1266df1
Compare
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These lines are also touched by the other open ja PRs (pingcap#23272/pingcap#23273/pingcap#23274/pingcap#23275). Each PR previously applied only its own fix, so whichever merged second would conflict. Apply the union of the fixes (stray-digit removal + particle insertion) so every branch produces identical text and merges cleanly in any order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Miscellaneous Japanese fluency fixes found during review, kept separate from the release-notes PR (#23254).
29 changed lines across 22 files. Each is a 1-for-1 line replacement.
functions-and-operators/bit-functions-and-operators.md: fix the left-shift example —n`位置左に→左に`n`桁(EN: "shift ... to the left bynpositions"), and add the missingをafter1<<n.sql-tuning-best-practice.md: repair the garbled operator list and push-down description —(TableFullScan_18)Selection_19TiKV(StreamAgg_9で…→(TableFullScan_18、Selection_19、StreamAgg_9)はTiKV(cop[tikv])にプッシュダウンされ….external-storage-uri.md: remove the duplicatedIAMinIAMIAM(3 occurrences).br/br-pitr-manual.md,br/br-snapshot-manual.md: translate the leftover English wordstorage→ストレージ; addをbefore参照.br/br-snapshot-architecture.md: drop the duplicatedテーブルデータbefore the link.best-practices/uuid.md: repair次のようになりますab06…は36文字→(例えばab06…)は36文字.develop/dev-guide-aws-appflow-integration.md: add the missing topic marker after the leading link ([Amazon AppFlow](url)は、…).alert-rules.md,dr-secondary-cluster.md,develop/dev-guide-choose-driver-or-orm.md: remove the stray verb machine translation appended after link text ([サポートを受ける](/support.md)取得してください→[サポートを受けて](/support.md)ください).releases/release-4.0-ga.md: add missingを(hintを使用 / ストリーム集約を強制) and move the PR reference to the end of the sentence.releases/release-4.0.15.md: repair…を使用します。3SHOW TABLE STATUS一部の…→…を使用します。これは、SHOW TABLE STATUSが一部の….。,.) after reference links.Scope note: the stray-number removals are owned by #23275, so this PR no longer touches
data-type-date-and-time.md. Verified that no line changed here is also changed by #23275 (0 overlapping lines).Links that still lack
をin the touched lines are intentionally left to #23273, which covers particles after Markdown links.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).