diff --git a/docs/performance.md b/docs/performance.md
index e2cfbfa51..7585c4ad6 100644
--- a/docs/performance.md
+++ b/docs/performance.md
@@ -16,11 +16,11 @@ To find the right values, it's best to run load tests simulating real traffic.
 To configure the number of threads, use the `num_threads` option of the `php_server` and `php` directives.
 To change the number of workers, use the `num` option of the `worker` section of the `frankenphp` directive.
 
-### `max_threads` 
+### `max_threads`
 
 While it's always better to know exactly what your traffic will look like, real-life applications tend to be more
 unpredictable. The `max_threads` configuration is similar to FPM's `pm.max_children` and allows
-FrankenPHP to automatically spawn additional threads at runtime up to the specified limit. `max_threads` can help you 
+FrankenPHP to automatically spawn additional threads at runtime up to the specified limit. `max_threads` can help you
 figure out how many threads you need to handle your traffic and can make the server more resilient to latency spikes.
 If set to `auto`, the limit will be estimated based on the `memory_limit` in your `php.ini`. If not able to do so,
 `auto` will instead default to 2x `num_threads`.