Better.

_posts/2024-06-13-a-faster-liquidsoap.md

@@ -81,7 +81,7 @@ In the past, we have tried to reduce the parts of it that are expected for most
 The type-checking phase is, by far, the most time-, cpu-, and memory-consuming. This is because there are **a lot** of things to check and
 we now have **a lot** of functions, methods, settings etc. 
 
-Also, over the recent years, our standard library has grown exponentially.
+Indeed, over the recent years, our standard library has grown exponentially.
 
 Initially, we had a tiny `utils.liq` containing only about `50` top-level functions (version `0.9.2`)
 These were mostly for convenience and backward compatibility.