Deploying to gh-pages from @ db2915c 🚀

blog/memflow-0.2.0/index.html

@@ -131,11 +131,11 @@ <h3>1. OS layers and modularity</h3>
 mismatch of plugin's <code>rustc</code> version and the one of the user's code. While the layout has remained
 stable most of the time, the tides started to shift a few years ago, as more effort was put into
 trait objects on the compiler front.</p>
-<p>For 0.2, we knew we could not keep the status quo, so, we built <code>cglue</code>. The crate allows for
-simple and flexible ABI safe code generation, suited for the needs of <code>memflow</code>. Throughout the
-(very long) beta period, we received 0 crash reports stemming from ABI instability, while 0.1 had
-such cases. Therefore, we can conclude that it was a good investment that already made memflow more
-stable.</p>
+<p>For 0.2, we knew we could not keep the status quo, so, we built
+<a href="https://github.com/h33p/cglue"><code>cglue</code></a>. The crate allows for simple and flexible ABI safe code
+generation, suited for the needs of <code>memflow</code>. Throughout the (very long) beta period, we received
+0 crash reports stemming from ABI instability, while 0.1 had such cases. Therefore, we can conclude
+that it was a good investment that already made memflow more stable.</p>
 <p>In <code>0.2.0-betaX</code> series, you may have encountered &quot;invalid ABI&quot; errors, well, fear not, because in
 stable series, we commit to not breaking the ABI across entirety of <code>0.2</code> series, so this problem
 should be a thing of the past for most users.</p>