Update Grid docs to show example of wrapping behavior to clarify for …

[KristinLBradley]

UPDATE: Opened a new ticket to explore solution to consumer's actual layout issue: https://hashicorp.atlassian.net/browse/HDS-5013

(Will probably close or amend this PR accordingly)

---

📌 Summary

If merged, this PR will update Layout::Grid docs to include an example of wrapping behavior to clarify the behavior for consumers.

This arose from a consumer question shared by @shleewhite

Preview: https://hds-website-git-kristin-update-grid-docs-to-sh-cb97ad-hashicorp.vercel.app/layouts/grid#card-layouts

---

👀 Component checklist

• [ ] Percy was checked for any visual regression
• [ ] A changelog entry was added via Changesets if needed (see templates here)

💬 Please consider using conventional comments when reviewing this PR.

📋 PCI review checklist

• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
• If applicable, I've worked with GRC to document the impact of any changes to security controls.
  Examples of changes to controls include access controls, encryption, logging, etc.
• If applicable, I've worked with GRC to ensure compliance due to a significant change to the in-scope PCI environment.
  Examples include changes to operating systems, ports, protocols, services, cryptography-related components, PII processing code, etc.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
hds-showcase	✅ Ready (Inspect)	Visit Preview	Jun 23, 2025 8:04pm
hds-website	✅ Ready (Inspect)	Visit Preview	Jun 23, 2025 8:04pm

[didoo]

This arose from a consumer question shared by @shleewhite

Was it a private DM or a publick Slack message? In that case, would it be possible to link the original request/conversation for future reference?

[KristinLBradley]

This arose from a consumer question shared by @shleewhite

Was it a private DM or a publick Slack message? In that case, would it be possible to link the original request/conversation for future reference?

@didoo

@shleewhite messaged me on Slack about it. I think a consumer had slacked her first directly.

I've since opened a new ticket to examine a solution to what seems to be the consumer's real issue so I will likely close the PR.

[shleewhite]

@didoo @KristinLBradley it was Anna, our intern, who brought up the concern.