Simplify link

_posts/2024-10-21-legacy-security-manager-in-haskell.html

@@ -53,7 +53,7 @@ <h3 id="03ee8805b5a44e77b92f9f6d132513bf">
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;printf&nbsp;<span style="color:#a31515;">&quot;Saving&nbsp;Details&nbsp;for&nbsp;User&nbsp;(%s,&nbsp;%s,&nbsp;%s)&quot;</span>&nbsp;username&nbsp;fullName&nbsp;array</pre>
     </p>
     <p>
-        Notice how the Haskell code seems to suffer slightly from the <a href="https://wiki.c2.com/?ArrowAntiPattern=&ref=blog.codinghorror.com">Arrow code smell</a>, which is a problem that the C# code actually doesn't exhibit. The reason is that when using Haskell in an 'imperative style' (which you can, after a fashion, with <code>do</code> notation), you can't 'exit early' from a an <code>if</code> check. The problem is that you can't have <code>if</code>-<code>then</code> without <code>else</code>.
+        Notice how the Haskell code seems to suffer slightly from the <a href="https://wiki.c2.com/?ArrowAntiPattern">Arrow code smell</a>, which is a problem that the C# code actually doesn't exhibit. The reason is that when using Haskell in an 'imperative style' (which you can, after a fashion, with <code>do</code> notation), you can't 'exit early' from a an <code>if</code> check. The problem is that you can't have <code>if</code>-<code>then</code> without <code>else</code>.
     </p>
     <p>
         Haskell has other language features that enable you to get rid of Arrow code, but in the spirit of the exercise, this would take us too far away from the original C# code. Making the code prettier should be a task for the refactoring exercise, rather than the starting point.