chore: fix spelling errors

[jsoref]

No description provided.

[oracle-contributor-agreement]

Thank you for your pull request and welcome to our community! To contribute, please sign the Oracle Contributor Agreement (OCA).
The following contributors of this PR have not signed the OCA:

• PR author: jsoref
• 2119212+jsoref@users.noreply.github.com (@jsoref)

To sign the OCA, please create an Oracle account and sign the OCA in Oracle's Contributor Agreement Application.

When signing the OCA, please provide your GitHub username. After signing the OCA and getting an OCA approval from Oracle, this PR will be automatically updated.

If you are an Oracle employee, please make sure that you are a member of the main Oracle GitHub organization, and your membership in this organization is public.

[jsoref]

[behnazh-w]

@jsoref Thanks a lot for the PR. This is awesome. Can you please approve the Contributor Agreement?

[jsoref]

No. Because the app is 💩.

It doesn't let me get a keyboard to select macaron (on Android).

This is on top of taking forever and a day to load.

Oddly, it let me type-search my country of residence.

[jsoref]

Or

[jsoref]

I was able to sign it using a desktop browser, but please get someone to fix the flow so that it doesn't require one.

[behnazh-w]

@jsoref Sorry to hear about your bad experience with the OCA app. I have escalated the issue to the team that is in charge of the app.

[jsoref]

Fwiw, I actually hit a bunch of other errors including things that looked like capacity issues or general outages.

There's no particular indication of what to actually expect going forward. At this time, my thing just says "Under review".

[oracle-contributor-agreement]

Thank you for signing the OCA.

[behnazh-w]

@jsoref Looks like your commits are not signed. Can you please sign them and also include the Signed-off-by: line?

[jsoref]

Do you mean GPG signed (they all have signed-off-by -- I meticulously fixed all of them)? That's a bridge too far (the number of hoops and stumbling blocks for this project is absurd). I have an expired signature from 2018 and this is the first project to demand that since it expired.

I have an ssh signing key added in 2022 that I'd be willing to use.

Plus, you merged #613 w/o requiring that.

None of these changes should even require concern about (c) as they're all trivial.

[behnazh-w]

We have turned on a check on GitHub to verify commit signatures. As long as that check passes, it's good. Note that the check has passed for your other PR:

But the commits on this PR are missing the verified green tick for some reason.

[jsoref]

I think the check just needs to be rerun.

It also should be improved so that you can easily determine what it's actually complaining about.

[jsoref]

Oh, your docs are wrong. That commit was signed w/ an ssh signature:

Sure, I can do that here. But you should fix the docs to clarify what it actually tolerates (either "whatever github tolerates" or "gpg / ssh" if it's specifically picky)

[behnazh-w]

Sure, I can do that here. But you should fix the docs to clarify what it actually tolerates (either "whatever github tolerates" or "gpg / ssh" if it's specifically picky)

Thanks for the suggestion. I have created an issue for it.

[behnazh-w]

@jsoref The commits are now signed and the GitHub check passes, thanks. There is only one comment left by @benmss that needs to be addressed.

[spavlusieva]

hi @jsoref, We apology for the inconvenience you've experienced while signing an OCA, and are working on fixing these issues.