📖 Spelling

[jsoref]

What kind of change does this PR introduce?

(Is it a bug fix, feature, docs update, something else?)

• PR title follows the guidelines defined in our pull request documentation

What is the current behavior?

The misspellings have been reported at
https://github.com/jsoref/scorecard/actions/runs/7565320059/attempts/1#summary-20600890152

What is the new behavior (if this is a feature change)?**

• Tests for the changes have been added (for bug fixes/features)

The action will report that the changes in this PR would make it happy:
https://github.com/jsoref/scorecard/actions/runs/7565320271/attempts/1#summary-20600890502

Which issue(s) this PR fixes

Special notes for your reviewer

I'm happy to drop any particular changes / changes to any particular files/paths or to split this as requested.

Does this PR introduce a user-facing change?

For user-facing changes, please add a concise, human-readable release note to
the release-note

(In particular, describe what changes users might need to make in their
application as a result of this pull request.)

• I'm concerned that the changes to jsonBranchProtectionSettings may be breaking. I think most of the other changes are harmless...

[jsoref]

Thanks @spencerschrock (this comment is mostly present so that it's easier to see the diff for the force push here in case there's another force push later).

[jsoref]

So, should this be 👻 ? 🐛 ? I think we're ruled out the things we think are ⚠️ worthy...
I don't think it's ✨ and while some of the changes are 📖, many aren't.

Is it 🌱 because it's "other"?

[spencerschrock]

So, should this be 👻 ? 🐛 ? I think we're ruled out the things we think are ⚠️ worthy... I don't think it's ✨ and while some of the changes are 📖, many aren't.

Is it 🌱 because it's "other"?

I was debating between :seedling: and :book:, so happy to accept either.
I usually merge typo fixes as :book: since they don't change any of the behavior, even if it's strictly not documentation.

[jsoref]

Sold. Note that it might be worthwhile to update the documentation to that effect (to some extent, projects should try to reduce "cognitive load" on external contributors).

Thanks for the fast iteration, I appreciate it.