Repository navigation
.NET: Fix typos in XML doc comments and comments - #9846
sarankumar (sarankumar1325) wants to merge 1 commit into
Conversation
|
sarankumar (@sarankumar1325) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
1 similar comment
|
sarankumar (@sarankumar1325) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
|
sarankumar (@sarankumar1325), thanks for the contribution. Please reply with the appropriate comment (see #9846 (comment)) to agree with the Contributor License Agreement. Without that I cannot merge the PR. Thanks! |
Motivation & Context
The .NET sources contain a number of misspellings in public XML doc comments (which surface in IntelliSense and the generated API docs), in inline comments, and in one exception message (
Cannot deserialize EdgeId from JSON propery name ...).Description & Review Guide
EdgeIdConverterJsonExceptionmessage.Related Issue
N/A - trivial change: spelling fixes in comments, XML docs, and one exception message. The intended result isn't in dispute.
AI Assistance
AI assistance details: an AI assistant helped find the misspellings (codespell over
dotnet/src) and apply the fixes. I reviewed each changed line.Contribution Checklist
breaking changelabel (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.