Skip to content

i18n(ja): miscellaneous review fixes (bit-shift description)#23274

Draft
yahonda wants to merge 9 commits into
pingcap:i18n-ja-release-8.5from
yahonda:fix-ja-misc-review-fixes
Draft

i18n(ja): miscellaneous review fixes (bit-shift description)#23274
yahonda wants to merge 9 commits into
pingcap:i18n-ja-release-8.5from
yahonda:fix-ja-misc-review-fixes

Conversation

@yahonda

@yahonda yahonda commented Jul 15, 2026

Copy link
Copy Markdown
Member

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 by n positions"), and add the missing after 1<<n.
  • sql-tuning-best-practice.md: repair the garbled operator list and push-down description — TableFullScan_18Selection_19TiKV(StreamAgg_9で…TableFullScan_18Selection_19StreamAgg_9)はTiKV(cop[tikv])にプッシュダウンされ….
  • external-storage-uri.md: remove the duplicated IAM in IAMIAM (3 occurrences).
  • br/br-pitr-manual.md, br/br-snapshot-manual.md: translate the leftover English word storageストレージ; 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 …を使用します。3 SHOW TABLE STATUS一部の……を使用します。これは、SHOW TABLE STATUSが一部の….
  • Remaining files: add missing particles and remove stray trailing punctuation (, .) 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.

  • Might cause conflicts after applied to another branch

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:

-…発生します。1パラメータ`gc.max_write_bytes_per_sec`使用すると、…
+…発生します。`gc.max_write_bytes_per_sec`パラメータを使用すると、…

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).

@ti-chi-bot

ti-chi-bot Bot commented Jul 15, 2026

Copy link
Copy Markdown

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@ti-chi-bot ti-chi-bot Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 15, 2026
@ti-chi-bot

ti-chi-bot Bot commented Jul 15, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign kissmydb for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot Bot added missing-translation-status This PR does not have translation status info. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 15, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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`桁シフトします

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

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
  1. 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)

@ti-chi-bot ti-chi-bot Bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. area/develop This PR relates to the area of TiDB App development. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 15, 2026
@yahonda
yahonda force-pushed the fix-ja-misc-review-fixes branch from 8e3296d to 44d59a1 Compare July 16, 2026 00:38
@qiancai qiancai added translation/no-need No need to translate this PR. and removed missing-translation-status This PR does not have translation status info. labels Jul 16, 2026
@yahonda
yahonda force-pushed the fix-ja-misc-review-fixes branch from 44d59a1 to 3ad44d0 Compare July 16, 2026 09:07
yahonda and others added 5 commits July 21, 2026 10:10
…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>
@yahonda
yahonda force-pushed the fix-ja-misc-review-fixes branch from 3ad44d0 to 4e48177 Compare July 21, 2026 01:14
@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7fbb4c40-f81b-46dd-99e6-9ea434a5aabb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
@yahonda
yahonda force-pushed the fix-ja-misc-review-fixes branch from 5ec0e0b to 240f92a Compare July 21, 2026 06:03
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
@yahonda
yahonda force-pushed the fix-ja-misc-review-fixes branch from 240f92a to 1266df1 Compare July 21, 2026 07:08
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
yahonda added a commit to yahonda/docs that referenced this pull request Jul 21, 2026
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/develop This PR relates to the area of TiDB App development. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. translation/no-need No need to translate this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants