bpo-40441: Fix plural typo in documentation

[alexpovel]

Just a simple typo fix, from https://bugs.python.org/issue40441.

https://bugs.python.org/issue40441

[remilapeyre]

Hi @alexpovel, thanks for improving the documentation. Please change the title of the Pull Request to "bpo-40441: Fix plural typo in documentation"

[nanjekyejoannah]

Thanks @alexpovel for your contribution. I hope you also noted @remilapeyre 's comment on how PR titles are written.

[alexpovel]

Thank you for your very swift response. I read and was aware of the naming scheme, however something tripped me up. When creating an issue in the issue tracker, one must (should?) give a link to a PR. As such, the link to a PR has to be known before creating an issue. So the PR cannot be titled correctly, because the issue tracker number is not known yet.

The same logic seems to apply to git commits, which is why my commit message did not have a bpo number (simple typo PRs do not require an issue in the first place, but I am interested in how to resolve this otherwise).

It seems like creating the issue, thus getting a number, then working on the issue, committing and then creating a PR, then afterwards adding a link to the PR is the way to go?

[remilapeyre]

It seems like creating the issue, thus getting a number, then working on the issue, committing and then creating a PR, then afterwards adding a link to the PR is the way to go?

Yes exactly, having the issue first also helps if some discussion is needed. Note that only the PR title has a specific naming scheme, you can write your commits anyway you want.