diff --git a/peps/pep-2026.rst b/peps/pep-2026.rst
index 913e062d1..63626d75d 100644
--- a/peps/pep-2026.rst
+++ b/peps/pep-2026.rst
@@ -220,7 +220,7 @@ For example:
    removal in Python 3.15
 
 However, once aware of CalVer, it is immediately obvious from the warning how
-long you have to to take action:
+long you have to take action:
 
    DeprecationWarning: 'ctypes.SetPointerType' is deprecated and slated for
    removal in Python 3.26
@@ -494,7 +494,7 @@ commands. ``python`` can map to either ``python2`` or ``python3``.
 These would need revisiting if the major version changed, and started changing annually.
 
 Four years after Python 2.7's end-of-life, we could recommend ``python`` only
-maps to the the latest Python 3+ version.
+maps to the latest Python 3+ version.
 But what would ``python3`` map to when Python 26.0 is out?
 This would introduce additional complexity and cost.