From 09b2495a1e7e33ad50965f2b39936d0e47f535f6 Mon Sep 17 00:00:00 2001 From: Arash Partow Date: Mon, 1 Jan 2024 00:00:00 +0000 Subject: [PATCH] Fix awkward sentence --- fast/hints.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/fast/hints.md b/fast/hints.md index 96191b8..7ecaf2b 100644 --- a/fast/hints.md +++ b/fast/hints.md @@ -225,10 +225,10 @@ often wrong: because performance is lost all over the place. It will be difficult to figure out how to get started on performance improvements. 2. If you are developing a library that will be used by other people, the - people who will run into performance problems will be likely to be people - who cannot easily make performance improvements (they will have to - understand the details of code written by other people/teams, and have to - negotiate with them about the importance of performance optimizations). + people who will run into performance problems will likely be people who + cannot easily make performance improvements (they will have to understand + the details of code written by other people/teams, and have to negotiate + with them about the importance of performance optimizations). 3. It is harder to make significant changes to a system when it is in heavy use. 4. It is also hard to tell if there are performance problems that can be solved