Fix misspelled word #34439
Merged
Fix misspelled word #34439
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wadepickett
approved these changes
Jan 6, 2025
|
Approved, looks good, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #34438
Rick (and Wade, you're on as the MS author of one of the articles/samples) ...
The PU didn't backport the spelling fix (it's 10.0+), and the new Aspire 10.0 sample won't likely be created for some time. However, I think we should go ahead and fix this now for 9.0+ and not sweat versioning the change. It's not going to be particularly noticeable that we have it spelled correctly here, and it will avoid devs opening issues for us. 😆
Internal previews