Move period in mutable-heap-number.md (#793)

canac · web-flow · commit 3bfcf6ce7652 · 2025-04-14T12:07:05.000+02:00
diff --git a/src/blog/mutable-heap-number.md b/src/blog/mutable-heap-number.md
@@ -71,5 +71,5 @@ These changes significantly speed up the peculiar `Math.random` function:
 
 ![`async-fs` benchmark results on a Mac M1. Higher scores are better.](/_img/mutable-heap-number/result.png)
 
-The combined effect of these optimizations is a remarkable `~2.5x` speedup on the `async-fs` benchmark. This, in turn, contributes to a `~1.6%` improvement in the overall JetStream2 score .This demonstrates that seemingly simple code can create unexpected performance bottlenecks, and that small, targeted optimizations can have large impact not just for the benchmark.
+The combined effect of these optimizations is a remarkable `~2.5x` speedup on the `async-fs` benchmark. This, in turn, contributes to a `~1.6%` improvement in the overall JetStream2 score. This demonstrates that seemingly simple code can create unexpected performance bottlenecks, and that small, targeted optimizations can have large impact not just for the benchmark.
 

Original file line number	Diff line number	Diff line change
@@ -71,5 +71,5 @@ These changes significantly speed up the peculiar `Math.random` function:
`71`	`71`
`72`	`72`	![`async-fs` benchmark results on a Mac M1. Higher scores are better.](/_img/mutable-heap-number/result.png)
`73`	`73`
`74`		-The combined effect of these optimizations is a remarkable `~2.5x` speedup on the `async-fs` benchmark. This, in turn, contributes to a `~1.6%` improvement in the overall JetStream2 score .This demonstrates that seemingly simple code can create unexpected performance bottlenecks, and that small, targeted optimizations can have large impact not just for the benchmark.
	`74`	+The combined effect of these optimizations is a remarkable `~2.5x` speedup on the `async-fs` benchmark. This, in turn, contributes to a `~1.6%` improvement in the overall JetStream2 score. This demonstrates that seemingly simple code can create unexpected performance bottlenecks, and that small, targeted optimizations can have large impact not just for the benchmark.
`75`	`75`