diff --git a/blog/wasmcloud-1.0-vendor-neutral-apps/index.mdx b/blog/wasmcloud-1.0-vendor-neutral-apps/index.mdx
index 4817a8f9..511e911e 100644
--- a/blog/wasmcloud-1.0-vendor-neutral-apps/index.mdx
+++ b/blog/wasmcloud-1.0-vendor-neutral-apps/index.mdx
@@ -15,7 +15,7 @@ draft: false
 WebAssembly is bringing us closer than ever to a world of "write once, run anywhere." From developer platforms to the browser to embedded devices, Wasm gives us a way to write portable, efficient, sandboxed code. The **[WebAssembly System Interface (WASI)](https://github.com/WebAssembly/WASI/)** and the **[Component Model](https://github.com/WebAssembly/component-model)** extend the power of WebAssembly with standard APIs for core functionalities like HTTP, CLI, I/O, and more—as well as a specification for compiling Wasm applications as interoperable, composable **components**.
 
 Now, wasmCloud 1.0 brings the Component Model and the standard APIs of WASI 0.2 to production-grade distributed computing. By embracing community standards, wasmCloud ensures that your business logic is truly vendor-neutral. Components built for wasmCloud 1.0 run anywhere that supports WASI 0.2, and any component you've built to target WASI 0.2 is ready to run distributedly with wasmCloud.
-<!--truncate-->
+{/* truncate */}
 # Flexibility for platforms and applications
 
 [WASI 0.2 includes these APIs](https://github.com/WebAssembly/WASI/tree/main/preview2#wasi-preview-2-contents), all available for use with wasmCloud 1.0: