i18n(ja): fix dropped particles and unclosed parenthesis found by CodeRabbit - #23782
i18n(ja): fix dropped particles and unclosed parenthesis found by CodeRabbit#23782yahonda wants to merge 2 commits into
Conversation
…eRabbit Found on PR pingcap#23778 (zero-width-space removal), but unrelated to that fix's scope, so applied here as a separate PR per the user's request to keep the ZWSP diff easy to read. - 14 dev-guide-sample-application-*.md + dev-guide-wordpress.md: missing を particle before the .env/env.sh destination file in the 'copy and paste the corresponding connection string' step instruction. CodeRabbit flagged only 1 site (nextjs.md); a corpus grep for the identical shared template sentence found the same defect repeated across 13 more sibling guide pages sharing this instruction (48 sites total). - tidb-cloud/tidbx-instance-move-faq.md: unclosed parenthesis around the support-contact mailto link. - tiproxy/tiproxy-configuration.md: missing と particle before '組み合わせて使用できます'. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Skipping CI for Draft Pull Request. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (16)
Included review availability: Your plan provides up to 4 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe pull request corrects Japanese wording and invisible-character issues in connection instructions across sample application guides. It also fixes one malformed Markdown link and one TiProxy documentation phrase. No code or configuration changes are included. ChangesConnection instruction corrections
FAQ link correction
TiProxy wording correction
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This change corrects Japanese connection instructions, a support mailto link, and TiProxy wording without altering product behavior or configuration. No current merge-readiness risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 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 |
|
[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 |
…his PR PR pingcap#23778 (zero-width-space removal) touches the exact same lines this PR already modifies for the missing-particle/parenthesis fix. Removing the zero-width space here too avoids a same-line merge conflict regardless of which PR merges first. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
What is changed, added or deleted? (Required)
Fixes 3 defect classes found by CodeRabbit on PR #23778 (zero-width-space removal) that were unrelated to that PR's scope, split here to keep that diff focused:
.env/env.shdestination file name in the "copy and paste the corresponding connection string" step instruction, shared across 14develop/dev-guide-sample-application-*.mdpages +develop/dev-guide-wordpress.md(48 sites total -- CodeRabbit flagged only 1 site, a corpus grep for the identical shared template sentence found the same defect repeated across all sibling guide pages using this instruction).tidb-cloud/tidbx-instance-move-faq.md: unclosed parenthesis around a support-contact mailto link.tiproxy/tiproxy-configuration.md: missing と particle before 組み合わせて使用できます.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?
Summary by CodeRabbit
.envandenv.shfiles.