i18n(ja): add missing particle after Markdown links (wo before verbs, wa for subject)#23273
i18n(ja): add missing particle after Markdown links (wo before verbs, wa for subject)#23273yahonda wants to merge 2 commits into
Conversation
|
Skipping CI for Draft Pull Request. |
ti-chi-bot
Bot
added
do-not-merge/work-in-progress
|
[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 |
ti-chi-bot
Bot
added
the
size/XXL
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request systematically improves the Japanese documentation by correcting grammatical particles, specifically ensuring the proper use of 'を参照してください' and 'を使用することをお勧めします' across numerous files. The reviewer's feedback is excellent and highly actionable, identifying several remaining typos (such as stray numbers '5', '1', '17'), grammatical awkwardness, missing particles, inconsistent terminology (e.g., 'storage' vs. 'ストレージ'), and minor formatting issues. All suggested changes are accompanied by ready-to-commit code blocks to ensure high-quality, natural Japanese documentation.
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.
…ingcap#23273) 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>
|
Thanks for the thorough review. To keep this PR focused on its single purpose (adding the missing particle after Markdown links), the 34 review findings have been addressed in separate PRs by kind, per our PR-splitting strategy:
These sibling PRs share some files with this one and will be rebased after the earlier PRs merge. |
7cfd082 to
6244b84
Compare
…ingcap#23273) 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>
a0f87a4 to
84b240b
Compare
qiancai
added
translation/no-need
…は for subject) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- join-queries.md: restructure "connected to TiDB using TiDBClient"
- vector-search-auto-embedding {gemini,huggingface,nvidia-nim}.md:
fix double-wo (を…を) → で for "with Auto Embedding"
- clinic-introduction.md: "サポートを受ける…を実行します" → "サポートを受けてください"
- dev-guide-choose-driver-or-orm.md: drop redundant "を実行します" after predicate anchor
- tidb-monitoring-api.md: "デプロイする…を実行します" → "デプロイしてください"
- dev-guide-third-party-tools-compatibility.md: clarify "expected behavior"
subject, restore mysql-connector-j anchor, add missing を (×3)
- dev-guide-use-stale-read.md: add は for NOW(), fix NOW(3) precision phrasing
- dm-manage-source.md: "the worker to be unbound" → バインド解除対象のワーカー,
drop redundant "を実行します" after predicate anchors
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
84b240b to
452ea4b
Compare
…ingcap#23273) 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>
2 participants
What is changed, added or deleted? (Required)
This PR adds missing particles immediately after Markdown links in the Japanese documentation, where machine-translated text dropped the particle between a link and the following word.
Main fix — missing を (object marker) before a verb (2088 cases):
[link text](url)使用して→[link text](url)を使用してScope: only the code where a link is the direct object of a transitive verb —
使用 / 実行 / 参照 / 報告 / 取得 / 指定 / 削除 / 確認 / 作成followed by an active conjugation (して / すると / する / します / した / しない / できる / できない). Compound nouns such as[link]クラスタ/[link]機能(which need no particle) and passiveされforms are not touched.Also — missing は (topic marker) after a link that is the sentence subject (1 case):
[Hibernate](https://hibernate.org/orm/)人気のオープンソースJava ORMです。→…)は人気の…All changes are 1-for-1 line replacements (particle insertion only) — no content changes. No double-
をintroduced (verified).Note: this PR may conflict with other in-flight i18n PRs that touch the same files; if so, it will be rebased after those are merged.
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?