minor corrections to zerokit-performance blog (#173)

* minor corrections to zerokit-performance blogs

- Added truncate line back
- Updated published
- Corrected publication date to 7-25 (and updated the file name to reflect this).
- tested locally.

* minor corrections

corrected extension for mdx for proper abstract display, and some minor typo fixes.

rlog/2025-07-25-zerokit-performance.mdx

@@ -1,8 +1,8 @@
 ---
 title: 'Zerokit optimizations: A performance journey'
-date: 2025-07-05 18:30:00
+date: 2025-07-25 18:30:00
 authors: benph
-published: false
+published: true
 slug: 2025-zerokit-perf
 categories: research
 
@@ -24,6 +24,7 @@ culling of redundant resource use. A story of cripplingly
 slow performance meets engineering talent, we arrive at a
 place where Zerokit comes through, fast and efficient, ready
 to face the world.
+{/* truncate */}
 
 ## Background
 
@@ -57,7 +58,7 @@ get rid of redundant operations and data taking up precious
 resources, and make the remaining operations go
 [<u>*Blazingly Fast™*.</u>](https://old.reddit.com/r/rust/comments/1avf1d8/blazingly_fast_memory_vulnerabilities_written_in/)
 
-Introducing the the star of the show for part 1: The main
+Introducing the star of the show for part 1: The main
 point of having this tree is to generate proofs so that
 peers can verify the claims being made. That doesn’t require
 the whole Merkle tree, just a single path, from leaf to
@@ -67,7 +68,7 @@ operated, relegating the tree itself to an off-network
 reference. This reduced the burden imposed on the network
 significantly. Updating the data on the tree has similarly
 reduced, with the exception being that the siblings of each
-node were retained. This is called the **Stateless**
+node were retained. This is called the **stateless**
 approach.
 
 Well, stateless in the context of proof generation and
@@ -165,7 +166,7 @@ leaving us with a single champion that cannot be denied, but
 which technology will claim this mantle? May the bits be
 _ever_ in your favor...
 
-## Benchmarking with Rusts `criterion` Crate
+## Benchmarking with Rust's criterion crate
 
 Rust, much like Nim, offers unadulterated, fine-grained, and
 direct control over performance, but with Rust, this control
@@ -177,7 +178,7 @@ that effectively "pair programs with you" to help avoid
 common pitfalls, includeing those of the performance
 veriety.
 
-The [<u>Criterion</u>](https://crates.io/crates/criterion) crate is
+The [<u>criterion</u>](https://crates.io/crates/criterion) crate is
 considered the go-to library for micro-benchmarking within
 the Rust ecosystem, and is generally regarded as an
 invaluable tool for obtaining high-quality telemetry.