Add review feedback from @JelleZijlstra and @AA-Turner

pep-0001.txt

@@ -281,17 +281,17 @@ 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 (BDFL-Delegate) for that PEP, and they will then have the
+the PEP-Delegate for that PEP, and they will then have the
 authority to approve (or reject) that PEP. 
 
-The terms, PEP-Delegate (preferred term under the Steering Council governance 
-model) and BDFL-Delegate, may be used interchangeably in discussion.
 The term "PEP-Delegate" will be used under the Steering
 Council governance model. The PEP's designated decision maker,
 the "PEP-Delegate" with the Steering Council's support, is
-recorded in the "BDFL-Delegate" field in the PEP's header. For consistency with
+recorded in the "PEP-Delegate" field in the PEP's header. For
 PEPs written prior to the Steering Council's governance model, the field name,
-"BDFL-Delegate" will still be kept but the field means "PEP-Delegate".
+"BDFL-Delegate" will still be kept.
+The terms, PEP-Delegate (preferred term under the Steering Council governance 
+model) and BDFL-Delegate, may be used interchangeably in discussion.
 
 Individuals offering to serve as PEP-Delegate should notify the Steering
 Council, PEP authors and PEP sponsor of their intent to self-nominate.