Repository navigation
docs: fix crossOrigin wording - #97462
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the crossOrigin documentation wording in the Next.js config reference to make the description clearer and more grammatically correct, without changing runtime behavior.
Changes:
- Reword βadd β¦ in all
<script>tagsβ to βadd β¦ to all<script>tagsβ for clarity. - Fix missing spacing in the Pages Router wording around
next/headβcomponentsβ.
π‘ Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Tests PassedCommit: bac08ae |
Stats skippedCommit: 1430708 |
|
Friendly follow-up on this docs-only PR. If there is any wording preference to align with before merge, I can update immediately. |
|
Still happy to adjust wording if maintainers want a different phrasing β docs-only and CI green. |
|
Closing this one-line docs tweak. The functional getStaticPaths fix stays open in #97740. Happy to reopen this wording change if a maintainer wants it. |
|
Reopened. On current canary the page still says the option adds the attribute in the script tags, and "components" is glued to the next/head link. The summary line had the same wording ("a crossOrigin tag on the script tags"). This now says the option adds a crossOrigin attribute to those tags, and the missing space is restored. |
aurorascharff
left a comment
There was a problem hiding this comment.
Thanks for your contribution!! β€οΈ
1d0ee05 to
bac08ae
Compare
What?
Fix the
crossOrigindocs so the wording matches what the option does, and so a missing space is not glued to thenext/headlink.Why?
<script>tags. It adds the attribute to those tags.head)componentshad no space, so "components" was stuck to the link.Docs only. No runtime change.
How?