Thanks for this, @TheGiraffe3.

I would definitely like to merge the specific spelling corrections in this PR.

And I also love the idea of adding some tooling to catch spelling mistakes!

I don't love the idea of leaning so hard on GitHub actions though, because it's hard to run workflows like this locally, so you don't end up seeing the test failures until its in CI. It's not necessarily a show-stopper, but it would be nice to have something that we could run locally too. Ideally something that integrates with mkdocs so that it throws errors when running build --strict. For example mkdocs-spellcheck
looks promising, though I've not tried it. Looks like we'd be able to configure ignored words directly within mkdocs.yml, which would be convenient. Another approach would be finding a separate python-based markdown linting tool and adding a local script to run it. I wouldn't be surprised if there might even be some tools that perform more elaborate grammar checking. If we could get a local spell-checking solution set up, then we'd still add a GitHub action that runs that script to ensure that PRs with spelling errors fail.

As a side-note: If we could use such a tool to enforce some of our other markdown code standards that would be nice too. I did some research a while back into potentially adopting mdformat to auto-format our markdown. I ran into a snag. I could be worth picking this work back up though.

If you'd be up for taking a stab at getting a docs spell-checker working locally too, then that would be really nice. If not, I can understand. Let me know. This PR definitely adds value as-is so I'm inclined to merge it if you're not up for digger deeper into the local spell-checking use-case.