summaryrefslogtreecommitdiffstats
path: root/Doc
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>1998-04-02 19:36:25 (GMT)
committerFred Drake <fdrake@acm.org>1998-04-02 19:36:25 (GMT)
commit3a18f3ba38a817c17d11534a1681f3345df9e70f (patch)
tree9ca3a2284b931d39ee423b9d48024e757826170f /Doc
parent5204b4a9842fa3a5db54a60994e84a9fe0e1206c (diff)
downloadcpython-3a18f3ba38a817c17d11534a1681f3345df9e70f.zip
cpython-3a18f3ba38a817c17d11534a1681f3345df9e70f.tar.gz
cpython-3a18f3ba38a817c17d11534a1681f3345df9e70f.tar.bz2
Hyphenate "built-in" for consistency.
Diffstat (limited to 'Doc')
-rw-r--r--Doc/lib/libprofile.tex2
-rw-r--r--Doc/libprofile.tex2
2 files changed, 2 insertions, 2 deletions
diff --git a/Doc/lib/libprofile.tex b/Doc/lib/libprofile.tex
index b7a1c1e..debb332 100644
--- a/Doc/lib/libprofile.tex
+++ b/Doc/lib/libprofile.tex
@@ -520,7 +520,7 @@ There are two fundamental limitations on this profiler. The first is
that it relies on the Python interpreter to dispatch \dfn{call},
\dfn{return}, and \dfn{exception} events. Compiled \C{} code does not
get interpreted, and hence is ``invisible'' to the profiler. All time
-spent in \C{} code (including builtin functions) will be charged to the
+spent in \C{} code (including built-in functions) will be charged to the
Python function that invoked the \C{} code. If the \C{} code calls out
to some native Python code, then those calls will be profiled
properly.
diff --git a/Doc/libprofile.tex b/Doc/libprofile.tex
index b7a1c1e..debb332 100644
--- a/Doc/libprofile.tex
+++ b/Doc/libprofile.tex
@@ -520,7 +520,7 @@ There are two fundamental limitations on this profiler. The first is
that it relies on the Python interpreter to dispatch \dfn{call},
\dfn{return}, and \dfn{exception} events. Compiled \C{} code does not
get interpreted, and hence is ``invisible'' to the profiler. All time
-spent in \C{} code (including builtin functions) will be charged to the
+spent in \C{} code (including built-in functions) will be charged to the
Python function that invoked the \C{} code. If the \C{} code calls out
to some native Python code, then those calls will be profiled
properly.