Fix incorrect documentation examples for UI components #468
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes multiple issues in the documentation where component usage examples were invalid or did not match the actual component implementations.
Several documented examples contained incorrect JSX syntax, wrong prop names, and mismatches between expected and actual data structures, which made the components difficult to use or caused runtime errors when followed.
Related Issue
Closes #456
Motivation and Context
Accurate documentation is critical for usability and onboarding new contributors. Incorrect examples can lead to confusion, broken implementations, and wasted developer time.
This change ensures that all documented UI components:
Screenshots (In case of UI changes):
Not applicable — documentation-only changes.
Types of changes
Checklist: