diff --git a/src/_blog/ipfs-thing-2022-recap.md b/src/_blog/ipfs-thing-2022-recap.md
index 36b0bc1d..09131b88 100644
--- a/src/_blog/ipfs-thing-2022-recap.md
+++ b/src/_blog/ipfs-thing-2022-recap.md
@@ -32,7 +32,7 @@ The “choose your own adventure” format spanned 12 tracks, with over 60 prese
 
 1. **We’re poised for a Cambrian explosion of IPFS implementations and innovation.**  
    Since its creation in 2014, IPFS has grown to over 250,000 distributed nodes worldwide. It’s the foundation of [Filecoin](https://filecoin.io/), [NFT.storage](https://nft.storage/), all of the existing IPFS HTTP [gateways](https://ipfs.github.io/public-gateway-checker/), hundreds of peer-to-peer applications from [Audius](https://audius.co/) to [WeatherXM](https://weatherxm.com/), and more. Nearly all of this was built with [Kubo](https://github.com/ipfs/kubo/) (formerly go-ipfs), the earliest IPFS implementation. However, the ubiquity of Kubo also exposed the downsides of a single reference implementation.
-2. **Projects like Estuary, Elastic IPFS, and Capyloon in the past year have shown us the necessity for multiple IPFS implementations.   
+2. **Projects like Estuary, Elastic IPFS, and Capyloon in the past year have shown us the necessity for multiple IPFS implementations.  
    **Throughout 2021-2022, a handful of new IPFS variants emerged. Each was tailored to a specific set of deployment, platform, or user needs: [Estuary](https://estuary.tech/) for midsized data storage bundled with Filecoin, [Elastic IPFS](https://nft.storage/blog/post/2022-07-06-elastic-ipfs/) for NFT.Storage and Web3.Storage needs such as horizontal scalability and no DHT re-providing, and [Capyloon](https://capyloon.org/) for mobile, to name a few. Unlocking the next phase of IPFS adoption will require an explosion in availability of choice for businesses and developers. The several new directions we’ve recently seen now need to scale up and mature, and we need dozens more implementations beyond their early steps. Future implementations might design for unique operating environments, compatibility with cloud-native tooling or fast-growing technologies such as WASM.
 3. **Building applications on IPFS requires a base set of capabilities.**