One more minor change.

Author: ZeroIntensity

peps/pep-0842.rst

@@ -217,8 +217,7 @@ as dynamic as Python, the way people consume APIs is also dynamic.
 
 The fundamental issue here is that Python has no way to express which names
 in a module are "private" or "public". Prefixing is an option, but given the
-reasons above, it's not always a bulletproof (or nice) solution for library
-authors.
+reasons above, it's not always a bulletproof solution for library authors.
 
 Currently, the other convention for expressing which names are public is
 done through a module's ``__all__`` variable. This has two major downsides: