[Dhairya-007]

Six mechanical slips in three Draft PEPs, one commit per PEP:

PEP 653

• "determined in a efficient fashion" → "an efficient"
• "one of None, True or False ," → stray space before the comma

PEP 748

• "represented by a Objective-C uint16_t enum" → "an Objective-C"
• "directly corresponds to an registered IANA id" → "a registered"
• "which allow to disable certificate validation" → "which allow disabling",
  the only one of the six that is a wording change rather than a character

PEP 786

• "it is a obstacle to ergonomics" → "an obstacle"

As with #5223, I kept this to Draft PEPs, since CONTRIBUTING.rst advises
against mass-correcting minor typos on older PEPs and welcomes copyediting of
Draft and Active ones. No markup or meaning changes.

I checked and left alone the cases where the article is already right, including
"a universal computing platform", "a unified", "a usable", "a usability hazard",
"a US zip code" and "A Unified TLS API", which all take "a" because the vowel is
pronounced as a consonant, plus "even though A and B were never explicitly
installed" in PEP 771, where A and B are package names.

python3 check-peps.py passes on all three files.

[read-the-docs-community]

Documentation build overview

📚 pep-previews | 🛠️ Build #35738578 | 📁 Comparing 21884d6 against latest (dfc3d95)

  🔍 Preview build  

8 files changed · ± 8 modified

± Modified

• pep-0001/index.html
• pep-0653/index.html
• pep-0720/index.html
• pep-0748/index.html
• pep-0776/index.html
• pep-0786/index.html
• pep-0818/index.html
• pep-0824/index.html

[Dhairya-007]

@StanFromIreland would you mind taking a look? Same scope as #5223 — Draft PEPs only.