Thanks! FWIW some people find fixing up typos to be contentious as it can be seen as churn. Feel free to loop me in as a reviewer on any CPython PRs for comment/docs typo fixes. They do improve our codebase overall and when done as this one is, across a bunch of files at once systematically, reduce the plethora of future random PRs from people over time fixing just one thing at a time.

@cclauss, just like elsewhere, we'll appreciate a manual [3.10] and [3.9] version of this PR to help us avoid future backport conflicts.

Thanks @cclauss for the PR, and @gpshead for merging it 🌮🎉.. I'm working now to backport this PR to: 3.9.
🐍🍒⛏🤖

Thanks @cclauss for the PR, and @gpshead for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10.
🐍🍒⛏🤖

Sorry, @cclauss and @gpshead, I could not cleanly backport this to 3.9 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker 8e8f7522171ef82f2f5049940f815e00e38c6f42 3.9

Sorry @cclauss and @gpshead, I had trouble checking out the 3.10 backport branch.
Please backport using cherry_picker on command line.
cherry_picker 8e8f7522171ef82f2f5049940f815e00e38c6f42 3.10

(apparently this one does need to be done manually, had to check :)

If a sweeping change worked across branches, I'd be super surprised :D

@gpshead Thanks for your guidance. There are four more PRs to review if you have time/interest. https://github.com/python/cpython/pulls/cclauss

@ambv I will go at the backports in my morning.

GH-28788 is a backport of this pull request to the 3.9 branch.

GH-28789 is a backport of this pull request to the 3.10 branch.

Thanks folks for the help!