summaryrefslogtreecommitdiffstats
path: root/Lib/heapq.py
diff options
context:
space:
mode:
authorMartin Panter <vadmium+py@gmail.com>2016-04-15 02:14:19 (GMT)
committerMartin Panter <vadmium+py@gmail.com>2016-04-15 02:14:19 (GMT)
commit6245cb3c015a5b9febef4d6ef30d3acfc762a79d (patch)
tree3e0a3907968edb89a7d24a051dab35c9a43f5dee /Lib/heapq.py
parent7d82d0366bb6c1b175cf54cf87778bba2451b0f4 (diff)
downloadcpython-6245cb3c015a5b9febef4d6ef30d3acfc762a79d.zip
cpython-6245cb3c015a5b9febef4d6ef30d3acfc762a79d.tar.gz
cpython-6245cb3c015a5b9febef4d6ef30d3acfc762a79d.tar.bz2
Correct “an” → “a” with “Unicode”, “user”, “UTF”, etc
This affects documentation, code comments, and a debugging messages.
Diffstat (limited to 'Lib/heapq.py')
-rw-r--r--Lib/heapq.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/Lib/heapq.py b/Lib/heapq.py
index 07af37e..0b3e89a 100644
--- a/Lib/heapq.py
+++ b/Lib/heapq.py
@@ -54,7 +54,7 @@ representation for a tournament. The numbers below are `k', not a[k]:
In the tree above, each cell `k' is topping `2*k+1' and `2*k+2'. In
-an usual binary tournament we see in sports, each cell is the winner
+a usual binary tournament we see in sports, each cell is the winner
over the two cells it tops, and we can trace the winner down the tree
to see all opponents s/he had. However, in many computer applications
of such tournaments, we do not need to trace the history of a winner.