diff --git a/articles/firefox-wasm-tail-call-benchmark/page.mmd b/articles/firefox-wasm-tail-call-benchmark/page.mmd
index 5a98ebf..7c6324b 100644
--- a/articles/firefox-wasm-tail-call-benchmark/page.mmd
+++ b/articles/firefox-wasm-tail-call-benchmark/page.mmd
@@ -13,14 +13,14 @@ of interfaces. It gets pretty funny, I can't even run ZX Spectrum emulator writt
 A lot of software targeting the web has their own languages and interpreters (such as Godot and GDScript) and in realtime simulation intensive cases overheads do matter.
 
 One of things that is often suggested for solving interpreter performance is `tail calling`.
-And it works emperically on native platforms. ![Check this post](https://mort.coffee/home/fast-interpreters/).
+And it works emperically on native platforms. [Check this post](https://mort.coffee/home/fast-interpreters/).
 
-And so I wondered, could it work for Wasm platform? Firefox recently ![pushed support](https://bugzilla.mozilla.org/show_bug.cgi?id=1846789) for ![experimental spec](https://github.com/WebAssembly/tail-call/blob/main/proposals/tail-call/Overview.md) of it, after all.
+And so I wondered, could it work for Wasm platform? Firefox recently [pushed support](https://bugzilla.mozilla.org/show_bug.cgi?id=1846789) for [experimental spec](https://github.com/WebAssembly/tail-call/blob/main/proposals/tail-call/Overview.md) of it, after all.
 
 ### Results ###
 
 I based the test interpreter on `fast-interpreters` post linked above.
-Sources are available on ![github](https://github.com/quantumedbox/wasm-tail-call-interpreter-benchmark). It does nothing, but increments until 100000000,
+Sources are available on [github](https://github.com/quantumedbox/wasm-tail-call-interpreter-benchmark). It does nothing, but increments until 100000000,
 which is relevant case for nothing, but instruction decoding, which we are testing here.
 
 First, native: