chore: fix typos across codebase

[sukrucildirr]

Fixed typos across codebase.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[TallTed]

fixes incorrect fix (twice) for typo

[sukrucildirr]

fixes incorrect fix (twice) for typo

Thanks, sir.

[abhvious]

Thank you for these fixes. Embarrassing that we didn't run a spellcheck.

Can both of you please sign the CLA in comment #15 (comment) ?

[abhvious]

Should be "approach"

[abhvious]

Remove the .html files from the pr. These files are automatically generated by doxygen.

[sukrucildirr]

Remove the .html files from the pr. These files are automatically generated by doxygen.

Removed the .html files from the pull request and signed the CLA.

[TallTed]

@abhvious — I signed the CLA with my primary google account address, but that address is not what I primarily use for GitHub contributions. Google claims my primary address as used here is associated with another Google Account, but I have no way to learn what account that is, nor dissociate it (if that association is incorrect), etc. I'm stonewalled. Which means that my tiny, human language contributions, block @sukrucildirr's larger contribution. Sad.

[sukrucildirr]

@abhvious — I signed the CLA with my primary google account address, but that address is not what I primarily use for GitHub contributions. Google claims my primary address as used here is associated with another Google Account, but I have no way to learn what account that is, nor dissociate it (if that association is incorrect), etc. I'm stonewalled. Which means that my tiny, human language contributions, block @sukrucildirr's larger contribution. Sad.

Thank you for your kind words. Maybe you can find it in the settings.

[TallTed]

@google-admin @abhvious — Both of my relevant email addresses ([email protected] and [email protected]) are associated with my GitHub ID (@TallTed). I apparently cannot associate the second email address with my primary GoogleID (the first email address) because it is already associated with another GoogleID (which I am not offered any way to know). This, combined with there being no way to remove myself from this PR, makes it impossible for my (tiny!) contribution here to be auto-approved by @google-cla; hence, this blocks @sukrucildirr's (larger) contribution. It might be time to rethink some aspects of how Google manages FOSS contributions!

[sukrucildirr]

@google-admin @abhvious — Both of my relevant email addresses ([email protected] and [email protected]) are associated with my GitHub ID (@TallTed). I apparently cannot associate the second email address with my primary GoogleID (the first email address) because it is already associated with another GoogleID (which I am not offered any way to know). This, combined with there being no way to remove myself from this PR, makes it impossible for my (tiny!) contribution here to be auto-approved by @google-cla; hence, this blocks @sukrucildirr's (larger) contribution. It might be time to rethink some aspects of how Google manages FOSS contributions!

No problem, sir. Let’s wait for the final check from @abhvious .