From c03489b23483484cf1dd5b2876ca104e4b2222d2 Mon Sep 17 00:00:00 2001 From: "C.A.M. Gerlach" Date: Fri, 21 Jan 2022 01:39:13 -0600 Subject: [PATCH] PEP 1: Further tweak phrasing of PEP delegate description --- pep-0001.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pep-0001.txt b/pep-0001.txt index 6f178f95df9..1ec85fa8f45 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -282,8 +282,8 @@ notifying the PEP author(s) and giving them a chance to make revisions. The final authority for PEP approval is the Steering Council. However, whenever a new PEP is put forward, any core developer that believes they are suitably experienced to make the final decision on that PEP may offer to serve as -the PEP-Delegate for that PEP, and not declined by the Steering Council, -they will then have the authority to approve or reject that PEP. +the PEP-Delegate for it. If the Steering Council assents to their offer, the +PEP-Delegate will then have the authority to approve or reject that PEP. The term "PEP-Delegate" is used under the Steering Council governance model for the PEP's designated decision maker,