From 5bd7ac3a12ba2c33153438cb1dea9b34101ed1d0 Mon Sep 17 00:00:00 2001
From: chadwhitacre <>
Date: Tue, 22 Sep 2020 10:11:00 +0000
Subject: [PATCH] [Imported from Trac: page Python3, version 21]

---
 Python3.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Python3.md b/Python3.md
index 5b3911e..71ba157 100644
--- a/Python3.md
+++ b/Python3.md
@@ -99,7 +99,7 @@ Leaking Future objects (newints, new dicts, new bytes) in module API can break e
 ## When ports get harder due to spaghetti dependencies
 
 As the port progresses, the simple "port module + its test module" gets difficult, since everything ends up depending on everything else.
-Here's on way to approach this:
+Here's one way to approach this:
 
 1. Port _only_ the test module. This involves many Python 3fixes to lots of other modules, but they are not officially ported, they're just inched along just enough to make the tests pass. Since the test module is officially ported, regressions to the Python 3 port still are prevented.
 2. Then, port the corresponding module.