fixup jco post (#88)

Author: yoshuawuyts

_posts/2024-02-19-jco-1.0.md

@@ -15,11 +15,7 @@ runtime. And by implementing the entirety of the WASI 0.2 API surface, those
 components can access the network, filesystem, and other system APIs available
 in the Node.js runtime.
 
-[^wasi-one-liner]: WebAssembly Components are an extension to WebAssembly to
-create strongly typed interfaces between different programs. WASI 0.2 is a
-re-work of the "WebAssembly System Interfaces" based on WebAssembly Components.
-The previous version of WASI was not based on components, and as a result was
-rather limited in what it could express.
+[^wasi-one-liner]: WebAssembly Components are an extension to WebAssembly to create strongly typed interfaces between different programs. WASI 0.2 is a re-work of the "WebAssembly System Interfaces" based on WebAssembly Components.  The previous version of WASI was not based on components, and as a result was rather limited in what it could express.
 
 <!--end_excerpt-->
 
@@ -121,10 +117,7 @@ IDL](https://marketplace.visualstudio.com/items?itemName=bytecodealliance.wit-id
 package to get editor support for WIT files. And with that, it's time to write
 our Rust code!
 
-[^cc-gen]: If you're from the future: `cargo-component` generated this file for
-us in this location. Since it is not yet advertised as "stable", the output
-location for WIT files may change. If no `wit/world.wit` file was generated for
-you, please check a different location to see whether it might be somewhere else.
+[^cc-gen]: If you're from the future: `cargo-component` generated this file for us in this location. Since it is not yet advertised as "stable", the output location for WIT files may change. If no `wit/world.wit` file was generated for you, please check a different location to see whether it might be somewhere else.
 
 ### Writing a Rust library