PEP 540: correcting english errors

pep-0540.txt

@@ -60,12 +60,12 @@ These users expect that Python 3 "just works" with any locale and don't
 bother them with encodings. From their point of the view, the bug is not
 their locale but is obviously Python 3.
 
-Since Python 2 handles data as bytes, it's more rare in Python 2
+Since Python 2 handles data as bytes, it's rarer in Python 2
 compared to Python 3 to get Unicode errors. It also explains why users
 also perceive Python 3 as the root cause of their Unicode errors.
 
 Some users expect that Python 3 just works with any locale and so don't
-bother of mojibake, whereas some developers are working hard to prevent
+bother with mojibake, whereas some developers are working hard to prevent
 mojibake and so expect that Python 3 fails early before creating
 mojibake.
 
@@ -241,7 +241,7 @@ the ASCII encoding.
 
 The problem is that operating system data like filenames are decoded
 using the ``surrogateescape`` error handler (PEP 383). Displaying a
-filename to stdout raises an Unicode encode error if the filename
+filename to stdout raises a Unicode encode error if the filename
 contains an undecoded byte stored as a surrogate character.
 
 Python 3.6 now uses ``surrogateescape`` for stdin and stdout if the