Update headers.md

[zerosoul]

colspan -> colSpan

🎯 Changes

✅ Checklist

• I have followed the steps in the Contributing guide.
• I have tested this code locally with pnpm test:pr.

Summary by CodeRabbit

• Documentation
  • Updated guides to use colSpan instead of colspan for Nested Grouped Headers properties and rendered attributes. Examples and bullet points now reflect the correct casing, clarifying how to configure grouped headers and reducing confusion.

[changeset-bot]

⚠️ No Changeset found

Latest commit: ccd9660

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

Documentation updated to rename the header property from "colspan" to "colSpan" in Nested Grouped Headers Properties within docs/guide/headers.md.

Changes

Cohort / File(s)	Summary
Docs: Header property rename docs/guide/headers.md	Updated references from "colspan" to "colSpan" in Nested Grouped Headers Properties and corresponding rendered attribute descriptions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A nibble of docs, a hop through span,
I tweak my ears: it’s colSpan, not colspan.
Small carrots of casing, crisp and bright,
Headers aligned, everything just right.
Thump-thump! I sign the change with delight. 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description leaves the 🎯 Changes section empty and omits the required Release Impact section, so it does not follow the repository’s template or clearly document what was changed and how it affects releases.	Please fill in the 🎯 Changes section with a brief description of renaming “colspan” to “colSpan” and add the 🚀 Release Impact section to indicate whether this is a docs-only change or requires a changeset for published code.
Title Check	❓ Inconclusive	The title “Update headers.md” references the file being changed but does not summarize the specific change of renaming the header property from colspan to colSpan, making it overly generic rather than clearly conveying the main update.	Consider revising the title to explicitly describe the change, for example “Rename colspan to colSpan in headers.md,” so that readers immediately understand the purpose of the update.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 02c203a and ccd9660.

📒 Files selected for processing (1)

• docs/guide/headers.md (1 hunks)

🔇 Additional comments (1)

docs/guide/headers.md (1)

57-58: Casing now matches the actual header property.

Using colSpan aligns with the API and DOM attribute casing. Looks good.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}