Correct "can not" to "cannot" in messages, comments, etc. #24124
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.
Both are correct, but "cannot" is preferred and far more common: https://www.merriam-webster.com/grammar/cannot-vs-can-not-is-there-a-difference
In some cases it is a user-facing message, such as certain XAML errors:
maui/src/Controls/src/Xaml/MarkupExtensions/ReferenceExtension.cs
Line 36 in 4856f37
And if you run into this type of error, you see it in Visual Studio. And it looks weird.
@spadapet , @jfversluis , @jonathanpeppers , @Redth - tagging all of you because you were participating in my discussion of this in a recent meeting. Very easy PR to review!
Notes:
can not
in the repo because they are quoting other things like bug titles, so I left them as-is.