docs: Fixing controls check type issues

[jungpaeng]

What I did

The Storybook 7.0 documentation had controls that didn't work, so we fixed the documentation.

How to test

No testing is required.

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

[jonniebigodes]

@jungpaeng, thanks for taking the time to create this pull request and help us improve our documentation. We appreciate it. To help me review, can you do me a favour and update your branch based on the latest version of the next branch? As some minor changes are required. Let me know once you've done it, and we'll go from there.

Hope you have a great week.

Stay safe

[jungpaeng]

@jonniebigodes Hi, I updated based on the next branch of the current storybook.

[jonniebigodes]

@jungpaeng thanks for addressing the feedback so promptly. I've checked this, and it seems that there's something happening with the check control. I tested both variants (the current one documented and the way you're proposing), and both worked out the same way. With that, I'm more than ok to merge this for the time being, as it will make it more idiomatic.

Hope you have a great day.

Stay safe