PEP 836: Review suggestions

[hugovk]

• Change is either:
  • To a Draft PEP
  • To an Accepted or Final PEP, with Steering Council approval
  • To fix an editorial issue (markup, typo, link, header, etc)
• PR title prefixed with PEP number (e.g. PEP 123: Summary of changes)

Some suggestions:

• Code formatting for main branch
• Replace footnotes with inline links -- save our readers a click and take them directly to the webpage
• Prefix internal refs with PEP number to avoid clash with other PEPs
• Wording

[read-the-docs-community]

Documentation build overview

📚 pep-previews | 🛠️ Build #33428591 | 📁 Comparing 09db52b against latest (6377bc2)

  🔍 Preview build  

1 file changed

± pep-0836/index.html

[Fidget-Spinner]

Nice simplification. Thanks!