From 754b54a9f2e8d03f718d759966138ce9124120b6 Mon Sep 17 00:00:00 2001
From: James McKinney <26463+jpmckinney@users.noreply.github.com>
Date: Mon, 26 Aug 2024 13:07:29 -0400
Subject: [PATCH] python/performance: Remove newline for block comment

---
 docs/python/performance.rst | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/python/performance.rst b/docs/python/performance.rst
index 1312c65..06f2930 100644
--- a/docs/python/performance.rst
+++ b/docs/python/performance.rst
@@ -32,7 +32,7 @@ Once a hotspot is found, the solution might be to:
 
    -  `Scalene <https://pypi.org/project/scalene/>`__ for CPU, GPU and memory statistical profiling
    -  `Austin <https://github.com/P403n1x87/austin>`__ for CPU and memory statistical profiling, including running processes
-   -  `psrecord <https://pypi.org/project/psrecord/>`__ to chart CPU and memory usage, in a running process
+   -  `psrecord <https://pypi.org/project/psrecord/>`__ to chart CPU and memory usage, including running processes
    -  `psutil <https://pypi.org/project/psutil/>`__
 
 CPU
@@ -70,7 +70,6 @@ When evaluating memory usage in production, remember the differences between `he
 -  `filprofiler <https://pypi.org/project/filprofiler/>`__ to diagnose peak memory
 
 ..
-
    `memory-profiler <https://pypi.org/project/memory-profiler/>`__ is unmaintained. Use psrecord instead, unless profiling individual functions.
 
    These are maintained, but not developed: