fixup! Add blog post about optimizations

_posts/2024-04-12-optimizations.md

@@ -251,12 +251,13 @@ are used. For more about those hints, see
 [Updating records in OTP 26](https://www.erlang.org/blog/more-optimizations/#updating-records-in-otp-26).
 
 In Erlang/OTP 27, there is a new hint called `inplace`. The compiler
-emits that hint if it has been verified that the previous value in
-that position in the record will never be accessed again. In other
+emits that hint when it has determined that nowhere in the runtime
+system is there another reference to the tuple except for the
+reference used for the `update_record` instruction. In other
 words, from the **compiler's** point of view, if the runtime system
 were to directly update the existing record without first copying it,
 the observable behavior of the program would not change. As soon will
-be seen, from **runtime system's** point of view, directly updating
+be seen, from the **runtime system's** point of view, directly updating
 the record is not always safe.
 
 This new optimization was implemented by Frej Drejhammar. It builds