Skip to content

docs: rewrite duplicate-prone link text with concise phrasing - #7752

Open
chida09 wants to merge 2 commits into
mainfrom
docs/fix-duplicate-link-wording
Open

chida09 wants to merge 2 commits into
mainfrom
docs/fix-duplicate-link-wording

Conversation

@chida09

@chida09 chida09 commented Jul 19, 2026

Copy link
Copy Markdown
Member

#7741

AI used

  • I did not use AI to create this PR.
  • (If there is no check above) I checked the generated content before submitting.

Description

Replace verbose "Xをもっと知りたい場合は、[こちら]をご覧ください" pattern with concise "詳しくは[X]をご覧ください" (ja) / "For more details, see [X]." (en).

This eliminates word duplication that occurs when the link text matches surrounding text (e.g. "レイヤースタイル…[レイヤースタイル]"). Follows the link text pattern used in ja.react.dev documentation.

Companion PR to #7745 — that PR handles non-duplicating cases; this one addresses the cases that require sentence restructuring.

Current behavior (updates)

Link sentences use the verbose pattern "Xをもっと知りたい場合は、[こちら]をご覧ください", which causes word duplication when the link text is replaced with a descriptive label matching the surrounding text.

New behavior

All affected sentences are rewritten to the concise pattern "詳しくは[X]をご覧ください" / "For more details, see [X]."

Is this a breaking change (Yes/No):

No

Additional Information

  • 8 files changed (4 ja/en pairs)
  • URLs unchanged — only surrounding text modified

Replace "Xをもっと知りたい場合は、[こちら]をご覧ください" with
"詳しくは[X]を参照してください" (ja) and "For more details, see [X]." (en)
to avoid word duplication while keeping meaningful link text.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Jul 19, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
yamada-ui Building Building Preview, Comment Jul 19, 2026 1:01am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants