From 916e73c59adff46a2c0d1eaec74c3979c1f56efa Mon Sep 17 00:00:00 2001
From: itamarst <>
Date: Fri, 11 Sep 2020 18:11:53 +0000
Subject: [PATCH] [Imported from Trac: page Python3, version 16]

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

diff --git a/Python3.md b/Python3.md
index d7e3b64..4b8b78b 100644
--- a/Python3.md
+++ b/Python3.md
@@ -92,7 +92,7 @@ Leaking Future objects (newints, new dicts, new bytes) in module API can break e
 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:
 
-1. Port _only_ the test module. This involves many fixes 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.
+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.
 
 ## Other notes