fix misspellings in source code

[WilliamLeara]

Description

No functional change here. Fix misspellings in code comments. Using "Global" as package, since the fixes are spread throughout the code base.

• Breaking change?

No, not a breaking change.

• Impacts security?

No impact to security.

• Includes tests?

No test code included nor required

How This Was Tested

N/A, this is just fixing misspellings in code comments

Integration Instructions

N/A, this is just fixing misspellings in code comments

[tianocore-pr-automation]

Pull Request Formatting Issues

⚠️ Provide a more detailed pull request description using the PR template (current: 78 characters).

Address these issues and the validation will automatically re-run when you update your pull request.

[ardbiesheuvel]

Thanks for the patch. Please split this up per-package into individual patches (but keep all patches under this PR)

[mikebeaton]

Please split this up per-package into individual patches (but keep all patches under this PR)

At the same time, please could you also update the commit wording slightly - you say "Fix misspellings, particularly in code comments.", but all your changes are in code comments, so you can just say "Fix misspellings in code comments."

[os-d]

Approved (with the assumption this will be broken up in per package commits, per Ard's request). In general, spelling fix PRs are more helpful if we can get to enabling the spell check plugin to not run in AuditMode (i.e. fail the build on spelling mistakes). If you plan to do more, I would recommend focusing on a package and getting all the spelling errors fixed there and disabling AuditMode in .ci.yaml.

But, certainly no complaints for fixing some up, thanks!