Capitalize Mercurial

Author: Mariatta

pep-0581.rst

@@ -69,7 +69,7 @@ Issues with bpo / Roundup
 
 - Less than five people maintain bpo. Some of them are core developers.
 
-- It is in mercurial. Without any CI available, it puts heavy burden on existing
+- It is in Mercurial. Without any CI available, it puts heavy burden on existing
   (few) maintainers in terms of reviewing, testing, and applying patches.
 
 - At its current state, it is not equipped to accept lots of contributions from
@@ -90,7 +90,7 @@ Issues with bpo / Roundup
   REST API  [#roundup-rest-api]_. Last activity was in 2016.
 
 - 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
+  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
   little traction [#nosy-list]_.
@@ -128,7 +128,7 @@ we already know how to do.
 
 In order to really improve Roundup / bpo, it needs to first migrate to GitHub,
 add CI and bots. As I understand it, there is hesitation because upstream Roundup
-is still im mercurial. Someone more familiar with Roundup / bpo needs
+is still im Mercurial. Someone more familiar with Roundup / bpo needs
 to champion this effort. (I'm not volunteering, I'm sorry).
 
 I believe the effort of creating and maintaining GitHub integrations and bots
@@ -248,14 +248,14 @@ added to the nosy list. We need to replicate this functionality.
 A GitHub account should not be a requirement
 --------------------------------------------
 
-Back when it was discussed about moving the CPython codebase from mercurial
+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.
 
 If bpo is made readonly, we'll need to come up with a different solution.
 
 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
+[#gh-1505]_ where we had one contributor who submitted patch to Mercurial, and
 refused to create a GitHub account. Because of this, our bot is unable to detect
 whether the have signed CLA. Another person had volunteered to upload his
 patch to GitHub. But we still require both people to sign the CLA.