PEP 544: Update Example

[1chooo]

• 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)

Related issue: #3312

---

📚 Documentation preview 📚: https://pep-previews--3783.org.readthedocs.build/

[1chooo]

@levkivskyi, @ambv Could you please review this pull request? If there are no issues, could you merge it and allow contributions to the python/peps?

[ilevkivskyi]

I think there are stricter rules to change Accepted/Final PEPs, so will need to find a second person to merge this. The change itself LGTM.

[JelleZijlstra]

This kind of change that doesn't change the contents is fine to merge.