Hyphenate "built-in" for consistency.

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.

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.