From f382d9641f3e736d4a894431ee0fd7f5a6a5d218 Mon Sep 17 00:00:00 2001 From: Justin Su Date: Mon, 22 Sep 2025 18:40:48 -0400 Subject: [PATCH] Fix "usueful" typo --- docs/vmprof.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/vmprof.rst b/docs/vmprof.rst index d6d88556..524c404e 100644 --- a/docs/vmprof.rst +++ b/docs/vmprof.rst @@ -191,7 +191,7 @@ As most statistical profilers, the core idea is to have a signal handler which periodically inspects and dumps the stack of the running program: the most frequently executed parts of the code will be dumped more often, and the post-processing and visualization tools have the chance to show the end user -usueful info about the behavior of the profiled program. This is the very same +useful info about the behavior of the profiled program. This is the very same approach used e.g. by `gperftools`_. However, when profiling an interpreter such as CPython, inspecting the C stack