From 3abdc54e4b02a355446d33a97ff9bc36354cc1f8 Mon Sep 17 00:00:00 2001
From: Kovid Goyal <kovid@kovidgoyal.net>
Date: Fri, 2 Feb 2024 20:51:11 +0530
Subject: [PATCH] ...

---
 docs/performance.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/performance.rst b/docs/performance.rst
index 0969039d9..2d9db3e8a 100644
--- a/docs/performance.rst
+++ b/docs/performance.rst
@@ -136,5 +136,5 @@ You can generate detailed per-function performance data using
 `gperftools <https://github.com/gperftools/gperftools>`__. Build |kitty| with
 ``make profile``. Run kitty and perform the task you want to analyse, for
 example, scrolling a large file with :program:`less`. After you quit, function
-call statistics will be printed to STDOUT and you can use tools like
-*KCachegrind* for more detailed analysis.
+call statistics will be displayed in *KCachegrind*. Hence, profiling is best done
+on Linux which has these tools easily available.