Capitalize Roundup

Author: Mariatta

pep-0581.rst

@@ -21,7 +21,7 @@ Rationale
 
 CPython's development moved to GitHub on February 2017. All other projects within
 The PSF's organization are hosted on GitHub and are using GitHub issues.
-CPython is still using Roundup as the issue tracker in bugs.python.org (bpo).
+CPython is still using Roundup as the issue tracker in bugs.python.org (bpo) [#bpo]_.
 
 Why GitHub
 ----------
@@ -75,7 +75,7 @@ Issues with bpo / Roundup
 - At its current state, it is not equipped to accept lots of contributions from
   people who aren't already familiar with the code base.
 
-- The upstream roundup is in Mercurial. There is an open discussion about
+- The upstream Roundup is in Mercurial. There is an open discussion about
   moving the source code of bpo to GitHub [#migrate-bpo]_. If the source code of
   bpo does move to GitHub, it will become difficult to update patches from upstream.
   But as long as it is in Mercurial, it is be difficult to maintain and onboard
@@ -92,7 +92,7 @@ Issues with bpo / Roundup
 - It sends a number of unnecessary emails and notifications, and it is difficult,
   if not impossible, to configure. An example is the nosy email, where we get
   email notification whenever someone added themselves as "nosy".
-  An issue has been filed in upstream roundup about this since 2012 with
+  An issue has been filed in upstream Roundup about this since 2012 with
   little traction [#nosy-list]_.
 
 - Creating an account has been a hassle. We've had reports when people have
@@ -249,10 +249,12 @@ A GitHub account should not be a requirement
 --------------------------------------------
 
 Back when it was discussed about moving the CPython codebase from Mercurial
-to GitHub [#github-cpython-1]_ and [#github-cpython-2]_, it was brought up we
-need to still allow uploading patches in bpo.
+to GitHub [#github-cpython-1]_ and [#github-cpython-2]_, it was brought up that we
+need to still allow uploading patches in bpo, and that a GitHub account shoould
+not be a requirement in order to contribute to Python.
 
-If bpo is made readonly, we'll need to come up with a different solution.
+If bpo is made readonly, we'll need to come up with a different solution to allow
+folks to contribute when they don't own a GitHub account.
 
 Related to this, since the migration to GitHub in 2017, I recall one case
 [#gh-1505]_ where we had one contributor who submitted patch to Mercurial, and
@@ -278,6 +280,9 @@ and ideas have been valuable.
 References
 ==========
 
+.. [#bpo] bugs.python.org
+   (https://bugs.python.org/)
+
 .. [#email-meta] About GitHub email notifications
    (https://help.github.com/articles/about-email-notifications/)