From 5a782f4be4c339885c806597d6633dfd127a60f2 Mon Sep 17 00:00:00 2001
From: chadwhitacre <>
Date: Tue, 6 Oct 2020 10:25:51 +0000
Subject: [PATCH] [Imported from Trac: page Python3, version 26]

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

diff --git a/Python3.md b/Python3.md
index c8bb8fa..4524a9c 100644
--- a/Python3.md
+++ b/Python3.md
@@ -102,7 +102,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 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.
+1. Port *only* the test module. This involves many Python 3 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.
 2. Then, port the corresponding module.
 
 ## Other notes