From b85afac44d84b5cd8635a03c6b3011510a394780 Mon Sep 17 00:00:00 2001 From: csabella Date: Wed, 7 Jun 2017 17:37:59 -0400 Subject: [PATCH] Fix some small typos in PEP 512 (#287) --- pep-0512.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pep-0512.txt b/pep-0512.txt index 73be99ad3..61e5224a5 100644 --- a/pep-0512.txt +++ b/pep-0512.txt @@ -60,7 +60,7 @@ languishing on the issue tracker due to core developers not being able to work through the backlog fast enough to keep up with submissions. In turn, that led to a side-effect issue of discouraging outside contribution due to frustration from lack of attention, which -is dangerous problem for an open source project with no corporate +is a dangerous problem for an open source project with no corporate backing as it runs counter to having a viable future for the project. While allowing patches to be uploaded to bugs.python.org [#b.p.o]_ is potentially simple for an external contributor, it is as slow and @@ -314,7 +314,7 @@ tracker). The association between a pull request and an issue will be done based on detecting an issue number. If the issue is specified in either the -title or in the body of a message on a pull request then connection +title or in the body of a message on a pull request then a connection will be made on bugs.python.org [#b.p.o]_. Some visible notification -- e.g. label or message -- will be made to the pull request to notify that the association was successfully made. @@ -401,7 +401,7 @@ modernization, working with the ``Misc/NEWS`` file will be simplified. The planned approach is to use an individual file per news entry, -containing the text for the entry. In this scenario each feature +containing the text for the entry. In this scenario, each feature release would have its own directory for news entries and a separate file would be created in that directory that was either named after the issue it closed or a timestamp value (which prevents collisions). @@ -520,7 +520,7 @@ re-run the tests in case of test flakiness will be needed, whether it is from removing a "test failed" label, web interface for core developers to trigger another testing event, etc. -Inspiration or basis of the bot could be taken from pre-existig bots +Inspiration or basis of the bot could be taken from pre-existing bots such as Homu [#homu]_ or Zuul [#zuul]_. The name given to this bot in order to give it commands is an open