Spelling

[jsoref]

Discussion

#8279

Testing

• Make sure all existing tests in the repository pass after your change. -- They do (although, many of them required fixes in Fix workflows for forks #8275 for me to validate)
• If you fixed a bug or added a feature, add a new test to cover your code. -- This can be done by applying a variant of jsoref@spell-check, but I'd prefer to leave that outside the scope of this PR

API Changes

I believe there's one API change included:
jsoref@10eacae

I've included it in the hopes that it isn't an API and, thus, can be changed. If it's an API and can't be changed, it's trivial for me to drop it (just as I'm more than happy to drop any other changes).

[jsoref]

The changes are all manual (more or less), and anything that isn't a simple replacement is very manual (especially things like neither).

Splitting is more or less possible -- it's easy for me to group commits together, or split by directory. It's fairly painful for me to split by part of speech if a word is used in more than one part of speech (and gets prohibitive as the word count grows -- it's error prone, and as a human, I make mistakes like everyone else), but it's certainly not a problem for me to peel off individual commits or group commits together into separate PRs -- I just need direction. For smaller repositories, I can split by "code" vs "comment" -- although I really don't like to do it as it isn't particularly safe -- it's much cleaner to split by directory or possibly file extension.

The only thing that's fully automated is identifying potential problems. I can certainly run the tooling on any repository if people are interested. Sometimes I rely on Google Sheets for word corrections, although of late, I've just been using Google Chrome suggestions.

[egilmorez]

I think jsoref fixed or backed out content related to my neither/nor suggestions (not easy to immediately discover that due to the massive size of this PR), so I think I'm happy to approve. Thanks!

[jsoref]

Do I need to worry about the changeset bot?

Note that https://github.com/firebase/firebase-js-sdk/actions/runs/9639724064/job/26582355096?pr=8280 is failing (I can't remember the state of this, I split most other CI failures into other PRs...)