summaryrefslogtreecommitdiffstats
path: root/Doc
diff options
context:
space:
mode:
authorAntoine <43954001+awecx@users.noreply.github.com>2019-08-24 04:09:43 (GMT)
committerMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>2019-08-24 04:09:43 (GMT)
commite17f201cd9293f16593cc507d86f2c0e17b8f2c9 (patch)
tree7bdab5c70d6fa6923f49aab02e23d3eb27342c7b /Doc
parent0a18ee4be7ba215f414bef04598e0849504f9f1e (diff)
downloadcpython-e17f201cd9293f16593cc507d86f2c0e17b8f2c9.zip
cpython-e17f201cd9293f16593cc507d86f2c0e17b8f2c9.tar.gz
cpython-e17f201cd9293f16593cc507d86f2c0e17b8f2c9.tar.bz2
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
Diffstat (limited to 'Doc')
-rw-r--r--Doc/bugs.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/bugs.rst b/Doc/bugs.rst
index 1e044ad..a17f04d 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.