Fix typos

[algonell]

Fix typos in documentation, comments, etc.

[cpython-cla-bot]

All commit authors signed the Contributor License Agreement.

[bedevere-app]

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

[picnixz]

For the configure script and other files, you should instead use make regen-configure and make regen-all to be sure that all files are up-to-date.

[picnixz]

@algonell Maybe I wasn't clear enough but by make regen-all, I meant that you needed to run them locally. This will produce new files (namely, a new configure script will be generated automatically).

Note that you either need podman or docker to regenerate the configure script since it depends on a speciifc version of autoconf. If you have trouble with this, I can make it myself and open a pull request on your branch so that you can update it (but everytime you make a change to configure.ac, I'll need to re-generate the files).

On platforms with shell scripts (Linux/MacOS), you can do the following:

./Tools/build/regen-configure.sh     # create an up-to-date 'configure'
./configure                          # create an up-to-date 'Makefile'
make -j12 regen-all

Then, you can verify the result via git status. If everything worked well, you should have some new files to commit. Once you've committed them and pushed them, the CI should be green.

---

Slightly off-topic, but you don't need to merge main into your branch unless you have conflicts. This will notify people watching the PR (like me) and we think that there is a relevant commit to actually review again.

[algonell]

My bad, one of my cleanups (occurence -> occurrence) was in aclocal.m4 (which is generated).

Thank for your patience and the detailed explanation!

[picnixz]

It's fine, took me a while as well in the beginning to see that I needed to regen configure with a specific version of autoconf...

[vstinner]

LGTM

[vstinner]

Changes on Objects/mimalloc/ should be made upstream in the https://github.com/microsoft/mimalloc/ project.

[picnixz]

Out of curiosity, how do you look for spelling mistakes? do you use hunspell or aspell (or something else?)

[bedevere-app]

GH-123866 is a backport of this pull request to the 3.13 branch.

[bedevere-app]

GH-123867 is a backport of this pull request to the 3.12 branch.

[vstinner]

Usually, I dislike backporting such changes to stable branches. But since this change modifies many files, I prefer to backport it to reduce the risk of conflicts of future backports.

[vstinner]

Merged, thanks.

[algonell]

Out of curiosity, how do you look for spelling mistakes? do you use hunspell or aspell (or something else?)

@picnixz it's codespell

[terryjreedy]

"you don't need to merge main into your branch unless you have conflicts." One does if one wants to test a revised PR against current main on one's own machine before pushing to github. However, one should 'git merge upstream/main' and not force-push. And testing is not an issue for typos in comments and docstrings.