Fix typos

[am11]

No description provided.

[ghost]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

null

Author:	am11
Assignees:	-
Labels:	area-Meta, community-contribution
Milestone:	-

[danmoseley]

Just curious did you use tooling for this? As it would have to understand how to split identifier names.

[am11]

I am repeating this method: #72314 (comment). In the current .typos.toml file, I have captured most of the false-positives (like Tigger) or ignorable words (like parm).

The capturing part is done by the typos utility. However, the fixing of typos is done manually as the tool quite frequently make mistakes with auto-correction and we may allow some words in certain contexts (like XML/Regex tests are using literature from books verbatim), but the same word can be fixed in other places. Then there are some paths which I revert before pushing the change to GitHub (eng/common, *.xlf, src/native/external etc.). I have pushed libunwind fixes upstream libunwind/libunwind#397, which we will pick up with next version upgrade (without needing to modify src/native/external/libunwind proactively).

[radical]

Please make sure to run runtime-wasm, and runtime-extra-platforms .

[radical]

/azp run runtime-wasm, runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[am11]

These failures seem unrelated to PR change. Example of a flaky test #67138 (comment) which failed here. Other legs timed out running tests.

[jkotas]

Thanks