diff --git a/pep-0367.txt b/pep-0367.txt
index 89ca58778..168db7a1e 100644
--- a/pep-0367.txt
+++ b/pep-0367.txt
@@ -122,10 +122,10 @@ Should ``super`` actually become a keyword?
 
 With this proposal, ``super`` would become a keyword to the same extent that
 ``None`` is a keyword. It is possible that further restricting the ``super``
-name may simplify implementation, however some are against the actual keyword-
-ization of super. The simplest solution is often the correct solution and the
-simplest solution may well not be adding additional keywords to the language
-when they are not needed. Still, it may solve other open issues.
+name may simplify implementation, however some are against the actual
+keyword-ization of super. The simplest solution is often the correct solution
+and the simplest solution may well not be adding additional keywords to the
+language when they are not needed. Still, it may solve other open issues.
 
 
 Closed Issues
@@ -513,10 +513,10 @@ super(self, \*args) or __super__(self, \*args)
 This solution only solves the problem of the type indication, does not handle
 differently named super methods, and is explicit about the name of the
 instance. It is less flexible without being able to enacted on other method
-names, in cases where that is needed. One use case this fails is where a base-
-class has a factory classmethod and a subclass has two factory classmethods,
-both of which needing to properly make super calls to the one in the base-
-class.
+names, in cases where that is needed. One use case this fails is where a
+base-class has a factory classmethod and a subclass has two factory
+classmethods, both of which needing to properly make super calls to the one
+in the base-class.
 
 super.foo(self, \*args)
 -----------------------