Skip to content

docs: fix crossOrigin wording - #97462

Merged
aurorascharff merged 1 commit into
vercel:canaryfrom
Rezakarimzadeh98:fix/next-crossorigin-docs
Nov 7, 2026
Merged

aurorascharff merged 1 commit into
vercel:canaryfrom
Rezakarimzadeh98:fix/next-crossorigin-docs

Conversation

@Rezakarimzadeh98

@Rezakarimzadeh98 Rezakarimzadeh98 commented Aug 17, 2026 •

Copy link
Copy Markdown
Contributor

What?

Fix the crossOrigin docs so the wording matches what the option does, and so a missing space is not glued to the next/head link.

Why?

  • The page said the option adds an attribute in all <script> tags. It adds the attribute to those tags.
  • head)components had no space, so "components" was stuck to the link.
  • The page summary still said "a crossOrigin tag on the script tags", which is the same awkward wording.

Docs only. No runtime change.

How?

  • Use "to" instead of "in".
  • Add the missing space before "components".
  • Say "attribute" instead of "tag" in the summary.

@Rezakarimzadeh98
Rezakarimzadeh98 marked this pull request as ready for review August 17, 2026 12:45
Copilot AI lite review requested due to automatic review settings August 17, 2026 12:45

Copilot AI 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.

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.

@github-actions

github-actions Bot commented Aug 19, 2026 •

Copy link
Copy Markdown
Contributor

Tests Passed

Commit: bac08ae
View workflow run

@github-actions

github-actions Bot commented Aug 19, 2026 •

Copy link
Copy Markdown
Contributor

Stats skipped

Commit: 1430708
View workflow run

@Rezakarimzadeh98

Copy link
Copy Markdown
Contributor Author

Friendly follow-up on this docs-only PR. If there is any wording preference to align with before merge, I can update immediately.

@Rezakarimzadeh98

Copy link
Copy Markdown
Contributor Author

Still happy to adjust wording if maintainers want a different phrasing β€” docs-only and CI green.

@github-actions github-actions Bot added the Documentation Related to Next.js' official documentation. label Nov 1, 2026
@Rezakarimzadeh98

Copy link
Copy Markdown
Contributor Author

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.

@Rezakarimzadeh98

Copy link
Copy Markdown
Contributor Author

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

Thanks for your contribution!! ❀️

@aurorascharff
aurorascharff force-pushed the fix/next-crossorigin-docs branch from 1d0ee05 to bac08ae Compare November 7, 2026 22:14
@aurorascharff
aurorascharff merged commit 09bd26a into vercel:canary Nov 7, 2026
55 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation Related to Next.js' official documentation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants