Edit the README for tone and clarity

[willingc]

Addresses #7.

Edits content to improve clarity and usability by sprint leaders. Improves user friendliness of document's tone.

[the-knights-who-say-ni]

Hello, and thanks for your contribution!

Unfortunately we couldn't find an account corresponding
to your GitHub username at bugs.python.org (b.p.o).
If you don't already have an account at b.p.o, please
create one and make sure to
add your GitHub username. If you do already have an account at b.p.o then
please go there and under "Your Details" add your GitHub username.

And in case you haven't already, please make sure to sign the
PSF contributor agreement
(CLA); we can't legally look at your contribution until you have signed the
CLA.

Once you have done everything that's needed, please reply here and someone will
verify everything is in order.

[willingc]

Well, the tool caught that I did not have a GitHub address in my bugs.python.org account even though I do have a signed CLA. I've updated the bugs.python.org account to include my GitHub user name.

I will push a small change to my PR branch and see if this resolves the CLA not signed tag.

[willingc]

Ooh. Very cool. The tool did change to CLA signed tag on a push to the branch. Nicely implemented.

Perhaps consider changing the default error message when there is no GitHub address in the bugs.python.org account so that a contributor can resolve themselves and not require interaction from a developer.

[ncoghlan]

Hmm, this is outdated (it's Visual Studio Community edition now)

I'll fix that directly after merging.

[ncoghlan]

Couple of fix-ups suggested, but I'll do those myself post-merge.

[willingc]

Thanks @ncoghlan. Also thank you to who wrote the CLA tool. It worked out very well 😄