diff --git a/pep-0411.txt b/pep-0411.txt
index 607ed732d..4e60695f0 100644
--- a/pep-0411.txt
+++ b/pep-0411.txt
@@ -26,7 +26,7 @@ On the other hand, the core development team explicitly states that no promises
 are made with regards to the the stability of the package's API, which may
 change for the next release.  While it is considered an unlikely outcome,
 such packages may even be removed from the standard library without a
-deprecation period if the concerns regarding their API or maintenante prove
+deprecation period if the concerns regarding their API or maintenance prove
 well-founded.
 
 
@@ -90,7 +90,7 @@ stable standard library.  Some reasons for not graduating are:
 * A much better alternative package may be found during the preview release.
 
 Essentially, the decision will be made by the core developers on a per-case
-basis.  The point to emphasize here is that a packages's inclusion in the
+basis.  The point to emphasize here is that a package's inclusion in the
 standard library as "provisional" in some release does not guarantee it will
 continue being part of Python in the next release.