Layout::Flex & Layout::Grid - API documentation for gap (HDS-5067)

[KristinLBradley]

📌 Summary

If merged, this PR updates the API documentation for the Flex & Grid component gap property. It's a follow-up of #2987

Previews:

• Flex gap API docs
• Grid gap API docs

Component updates PR: #2987 MERGED

🔗 External links

• Jira ticket: HDS-5067

---

👀 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	Jul 23, 2025 9:24am
hds-website	✅ Ready (Inspect)	Visit Preview	Jul 23, 2025 9:24am

The base branch was changed.

[KristinLBradley]

Fixed merge conflicts

[didoo]

@KristinLBradley I've pushed a small commit to fix a linting error

[didoo]

@KristinLBradley I have also removed some duplicate code (probably due to the conflict resolution)

[didoo]

@KristinLBradley there are extra commits in this PR, coming from https://github.com/hashicorp/design-system/pull/2987/commits. Probably the merge conflicts resolution was not correct:

I am going to create a new branch (with the same name), cherry pick only the correct commits, and force push

[didoo]

@KristinLBradley OK, I've force-pushed a clean branch. Can you double check that the commit and the code is what you expect to be? I have also approved, so if that's OK for you, feel free to merge

[didoo]

@KristinLBradley now that 4.2.11 has been released I think this one can be merged