- Fix several markups

- Fix wrong link

Author: Mariatta

pep-0581.rst

@@ -44,13 +44,13 @@ currently available in Roundup / bpo.
 - Core developers don't have to maintain it, giving us more time to focus on
   the development of Python.
 
-- We can automatically close issues when a PR has been merged [#close-github-issue].
+- We can automatically close issues when a PR has been merged [#close-github-issue]_.
 
 - With more than 28 million users, an open source contributor is more likely
   to already have an account, and familiar with GitHub interface, making it
   easier to start contributing.
 
-- Email notifications contain metadata [#email-meta], integrated with GMail, and
+- Email notifications contain metadata [#email-meta]_, integrated with GMail, and
   allows you to systematically filter emails.
 
 - Email address can remain hidden by choice.
@@ -78,10 +78,10 @@ Issues with bpo / Roundup
 - Email address is exposed. There is no choice to mask it.
 
 - There is no REST API available. There is an open issue in Roundup for adding
-  REST API  [#roundup-rest-api]. Last activity was in 2016.
+  REST API  [#roundup-rest-api]_. Last activity was in 2016.
 
 - I personally don't want to receive email each time someone added themselves as "nosy"
-  An issue has been filed in upstream roundup since 2012 with little traction [#nosy-list].
+  An issue has been filed in upstream roundup since 2012 with little traction [#nosy-list]_.
 
 - Creating an account has been a hassle. We've had reports when people have
   trouble creating accounts or logging in.
@@ -129,8 +129,8 @@ Migration Plan
 Backup of GitHub data
 ---------------------
 
-This effort has been started and being tracked as an issue in core-workflow [#backup-github].
-We're using GitHub Migrations API [#gh-migrations-api] to download GitHub data
+This effort has been started and being tracked as an issue in core-workflow [#backup-github]_.
+We're using GitHub Migrations API [#gh-migrations-api]_ to download GitHub data
 for CPython on daily basis. The archives will be dropped in an S3 bucket.
 
 Thanks to Ernest W. Durbin III for working on this.
@@ -159,13 +159,15 @@ Type: behavior, crash, compile error, resource usage, security, performance, enh
 Components: 2to3, Argument Clinic, asyncio, Build, Cross-build, ctypes, ...
 Priority: release blocker, deferred blocker, critical, high, normal, low
 
-We will create the corresponding labels:
+We will create the corresponding labels::
 
-type-behavior, type-crash, type-compile error, type-resource usage, ...
-components-2to3, components-argument clinic, components-asyncio, ...
-priority-release blocker, priority-deferred blocker, priority-critical, ...
+   type-behavior, type-crash, type-compile error, type-resource usage, ...
 
-In addition, we'll create "needs triage" label.
+   components-2to3, components-argument clinic, components-asyncio, ...
+
+   priority-release blocker, priority-deferred blocker, priority-critical, ...
+
+In addition, we'll create ``needs triage`` label.
 
 Create issue template
 ---------------------
@@ -182,7 +184,7 @@ The above values are pre-filled in the template. Issue creator will remove texts
 that do not apply to their issue.
 
 Based on the above metadata, bedevere-bot can apply the necessary labels to the issue.
-If issue creator did not supply the above metadata, the bot will apply "needs triage"
+If issue creator did not supply the above metadata, the bot will apply ``needs triage``
 label. At that point it will require a core developer to properly label the issue.
 
 Updates to bedevere
@@ -235,13 +237,13 @@ 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
+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-1501] 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.
@@ -282,10 +284,10 @@ References
 .. [#roundup-rest-api] Roundup issue 2550734 Expose roundup via a RESTful interface
    (http://issues.roundup-tracker.org/issue2550734)
 
-.. [#gh-1501] CPython GitHub Pull request 1505
+.. [#gh-1505] CPython GitHub Pull request 1505
    (https://github.com/python/cpython/pull/1505)
 
-.. [#github-cpython1] Python-committers email
+.. [#github-cpython-1] Python-committers email
    (https://mail.python.org/pipermail/python-committers/2015-December/003642.html)
 
 .. [#github-cpython-2] Python-committers email