Update index.md

content/news/2023-10-21-bevy-0.12/index.md

@@ -24,7 +24,7 @@ Since our last release a few months ago we've added a _ton_ of new features, bug
 
 <div class="release-feature-authors">authors: @hymm, @james7132</div>
 
-Bevy uses the [tracing](https://crates.io/crates/tracing) library to measure systems running time among other things. This is useful for determining where bottlenecks in frame time are and measuring performance improvements, and can be visualized using the [tracy](https://github.com/wolfpld/tracy) tool. However, using tracing's spans has a significant overhead to it. A large part of the per-span overhead is due to allocating the string description of the span. By caching the spans for systems, commands, and parallel iteration, we have significantly reduced the CPU time overhead when using tracing. In the PR that introduces caching the system spans, the many foxes stress test went from 5.35 ms to 4.54 ms. In the PR that adds caching for the parallel iteration spans, the many cubes stress test went from 8.89 ms to 6.8 ms.
+Bevy uses the [tracing](https://crates.io/crates/tracing) library to measure system running time (among other things). This is useful for determining where bottlenecks in frame time are and measuring performance improvements. These traces can be visualized using the [tracy](https://github.com/wolfpld/tracy) tool. However, using tracing's spans has a significant overhead to it. A large part of the per-span overhead is due to allocating the string description of the span. By caching the spans for systems, commands, and parallel iteration, we have significantly reduced the CPU time overhead when using tracing. In the PR that introduced system span caching, our "many foxes" stress test went from 5.35 ms to 4.54 ms. In the PR that added caching for the parallel iteration spans, our "many cubes" stress test went from 8.89 ms to 6.8 ms.
 
 ![tracing overhead](tracing-overhead-reduction.png)