Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit d2a296a

Browse files
committed
Issue 23005: Fix typos
1 parent 4ac7ed9 commit d2a296a

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

Doc/library/heapq.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -260,11 +260,11 @@ However, there are other representations which are more efficient overall, yet
260260
the worst cases might be terrible.
261261

262262
Heaps are also very useful in big disk sorts. You most probably all know that a
263-
big sort implies producing "runs" (which are pre-sorted sequences, which size is
263+
big sort implies producing "runs" (which are pre-sorted sequences, whose size is
264264
usually related to the amount of CPU memory), followed by a merging passes for
265265
these runs, which merging is often very cleverly organised [#]_. It is very
266266
important that the initial sort produces the longest runs possible. Tournaments
267-
are a good way to that. If, using all the memory available to hold a
267+
are a good way to achieve that. If, using all the memory available to hold a
268268
tournament, you replace and percolate items that happen to fit the current run,
269269
you'll produce runs which are twice the size of the memory for random input, and
270270
much better for input fuzzily ordered.

0 commit comments

Comments
 (0)