From eaa4742315610d974be497d12121ab00826f618d Mon Sep 17 00:00:00 2001
From: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Date: Fri, 1 Sep 2023 19:44:48 +0100
Subject: [PATCH] PEP 520: Resolve dangling hyphens (#3358)

---
 pep-0520.txt | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/pep-0520.txt b/pep-0520.txt
index d3090f0ef..978456b90 100644
--- a/pep-0520.txt
+++ b/pep-0520.txt
@@ -37,8 +37,8 @@ This allows introspection of the original definition order, e.g. by
 class decorators.
 
 Additionally, this PEP requires that the default class definition
-namespace be ordered (e.g. ``OrderedDict``) by default.  The long-
-lived class namespace (``__dict__``) will remain a ``dict``.
+namespace be ordered (e.g. ``OrderedDict``) by default.  The
+long-lived class namespace (``__dict__``) will remain a ``dict``.
 
 
 Motivation
@@ -185,10 +185,10 @@ the well-worn precedent found in Python.  Per Guido::
 
 Also, note that a writeable ``__definition_order__`` allows dynamically
 created classes (e.g. by Cython) to still have ``__definition_order__``
-properly set.  That could certainly be handled through specific class-
-creation tools, such as ``type()`` or the C-API, without the need to
-lose the semantics of a read-only attribute.  However, with a writeable
-attribute it's a moot point.
+properly set.  That could certainly be handled through specific
+class-creation tools, such as ``type()`` or the C-API, without the need
+to lose the semantics of a read-only attribute.  However, with a
+writeable attribute it's a moot point.
 
 
 Why not "__attribute_order__"?