Fix asyncio policy docs about per interpreter semantics

[kumaraditya303]

No description provided.

[miss-islington]

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

[bedevere-bot]

GH-97619 is a backport of this pull request to the 3.11 branch.

[bedevere-bot]

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

[CAM-Gerlach]

It would seem to still be useful to qualify "global" somehow, though, in terms of what actual scope it is global in—per process? Per machine? Something else? Otherwise, it is not very meaningful and potentially even confusing on its own, as a non-expert reader might plausibly think it means anywhere from thread-global to machine-global, given "global" can mean different things in different contexts (Python keyword, C concept, and various others). Or, if you do mean to imply the same scope as Python's global keyword (which many readers may naively assume), then it should be marked up and linked as such to make that clear.

[CAM-Gerlach]

Also, meta sidenote—it looks like on the CPython repo, the default squash merge commit message is set to be the first commit in the PR, rather than the PR title, which leads to the commit message being the rather uninformative "Fixup policy docs" rather than the far more useful "Fix asycio policy docs about per interpreter semantics" PR title. Someone should probably change that...

[gvanrossum]

That's my fault, normally I edit the commit title when I merge it, but I was in a hurry (too many meetings today).

[CAM-Gerlach]

No worries, its easy to miss, and it should be fixed for the future to use the PR title by default now that Ezio set the appropriate repo settings