[Python-checkins] Fix funny typo in Doc/bugs. (GH-15412)

[Miss Islington (bot)]

https://github.com/python/cpython/commit/7784d4bb155f0f527301b29f29b5469ba8a7b5d4
commit: 7784d4bb155f0f527301b29f29b5469ba8a7b5d4
branch: 3.8
author: Miss Islington (bot) <31488909+miss-islington at users.noreply.github.com>
committer: GitHub <noreply at github.com>
date: 2019-08-23T21:16:28-07:00
summary:

Fix funny typo in  Doc/bugs. (GH-15412)


Fix typo in description of link to mozilla bug report writing guidelines.

Though the URL is misleading, we're indeed trying to write bug _reports_, not to add bugs.

Automerge-Triggered-By: @ned-deily
(cherry picked from commit e17f201cd9293f16593cc507d86f2c0e17b8f2c9)

Co-authored-by: Antoine <43954001+awecx at users.noreply.github.com>

files:
M Doc/bugs.rst

diff --git a/Doc/bugs.rst b/Doc/bugs.rst
index 1e044ad2033d..a17f04d26fa4 100644
--- a/Doc/bugs.rst
+++ b/Doc/bugs.rst
@@ -80,7 +80,7 @@ taken on the bug.
       Article which goes into some detail about how to create a useful bug report.
       This describes what kind of information is useful and why it is useful.
 
-   `Bug Writing Guidelines <https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines>`_
+   `Bug Report Writing Guidelines <https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines>`_
       Information about writing a good bug report.  Some of this is specific to the
       Mozilla project, but describes general good practices.