summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEzio Melotti <ezio.melotti@gmail.com>2011-04-03 16:20:21 +0300
committerEzio Melotti <ezio.melotti@gmail.com>2011-04-03 16:20:21 +0300
commitb5ff3e4ce5f16ac9af5c682c6e8156393745f329 (patch)
treefa347e3d2f4f997bc44a4586754678be84465200
parentd05595697d70bef1c5cf66484e1d1102d510152e (diff)
downloadcpython-git-b5ff3e4ce5f16ac9af5c682c6e8156393745f329.tar.gz
Fix typo noticed by Sandro Tosi.
-rw-r--r--Doc/library/profile.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/library/profile.rst b/Doc/library/profile.rst
index c5e5dd5a6a..82cc2eb3c9 100644
--- a/Doc/library/profile.rst
+++ b/Doc/library/profile.rst
@@ -48,7 +48,7 @@ compatibility layer on top of the internal :mod:`_lsprof` module.
The profiler modules are designed to provide an execution profile for a given
program, not for benchmarking purposes (for that, there is :mod:`timeit` for
- resonably accurate results). This particularly applies to benchmarking
+ reasonably accurate results). This particularly applies to benchmarking
Python code against C code: the profilers introduce overhead for Python code,
but not for C-level functions, and so the C code would seem faster than any
Python one.