Title change done.
I can remove the space change if you like? It was just inconsistent, so I changed it. I made the PR referenced above against 3.9, and was just trying to find the corrections from that PR and bring them to 3.8 (so that they actually change in the 3.8 docs), as like you'd said I'd expected it to carry back.

@toonarmycaptain

Title change done.

Thanks.

I can remove the space change if you like? It was just inconsistent, so I changed it.

You can wait for additional feedback on that, but generally speaking we try to avoid making changes purely for the sake of consistency. This is significantly more important for changes to the source code, but it also applies to documentation or news changes. That's why I @ mentioned a couple of core developers that were especially experienced with reST, to check if the number of spaces makes a difference there.

One small unnecessary change may not seem like a big deal, but it can really add up over time. PR review time comes at a premium, especially for a project ran almost entirely by voluntary efforts. It improves our workflow significantly when PRs have a more focused scope and avoid any unneeded changes.

That being said, there's no harm at all in waiting for a second opinion; we have to wait on approval from a core developer before it can be merged.

That being said, there's no harm at all in waiting for a second opinion; we have to wait on approval from a core developer before it can be merged.

No problem, no need to bother the core devs unnecessarily! I just left it up to you as you were reviewing.

Looking at https://docs.python.org/3.8/whatsnew/changelog.html#python-3-8-1-final, and this SO question, there's one space in my browser, not three, so it appears as if the extra whitespace is collapsed either when used to generate the HTML or when the HTML is rendered.

Thanks!