Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

Recognized GitHub username

We couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames:

@sydneypemberton1986

This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

I think the title should be, instead of "Clarify documentation using 'respectively' construct", something that says more clearly where the change was made. Something like "Ungroup items in collections.abc documentation for improved clarity".

@iritkatriel Thank you so much for the prompt review. I was tangling with the first time setup of a Python PR and I made some pretty bonehead errors there. I've addressed your feedback and am working on straightening out the CLA. I know I signed it but it's not getting associated with my account somehow.

Thank you for addressing the comments. I think the CLA can take a day or two. In the meantime, it would be tidier to squash the two commits into one, so that the commit log is clean.

Excellent. I will rebase them.

I have my Github username configured as @sydneypemberton1986 on my B.P.O account.
I'm not exactly sure what counts as my B.P.O. username when signing the CLA. I used the federated login with Google.
I've tried a few variations, maybe I just need to wait.

Edit: I now get a 500 on https://check-python-cla.herokuapp.com/ with @sydneypemberton1986, so, progress?

@sydneypemberton1986, looking at the user screen on bugs.python.org, I believe you need to remove the '@' at the beginning of the Github name for the bot to be able to match to it. Thanks!

Sorry, I can't merge this PR. Reason: Required status check "Travis CI - Pull Request" is expected..

I'm going to close and reopen this to retrigger Travis CI.

@sydneypemberton1986: Status check is done, and it's a success ✅ .

Sorry, I can't merge this PR. Reason: Required status check "Travis CI - Pull Request" is expected..

@sydneypemberton1986: Status check is done, and it's a success ✅ .

Thanks @sydneypemberton1986 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8, 3.9.
🐍🍒⛏🤖 I'm not a witch! I'm not a witch!

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

GH-21927 is a backport of this pull request to the 3.8 branch.

@sydneypemberton1986 thank you for the contribution and welcome to CPython! 🎉 🎉 🎉

@iritkatriel, @eamanu, and @rhettinger, thank you for the reviews!