Fix typo in article

_posts/2021-11-17-Case-insensitive-pcre2-regex-and-unicode-case-folding.md

@@ -42,7 +42,7 @@ Another character looking almost identical to the character we're looking for, m
 
 Normally when debugging regexes I use tools like regex101, but it gives the same result and not any info on why. I have been looking for official documentation about PCRE2 regexes [as PHP uses PCRE (PCRE2 starting from 7.3)](https://www.php.net/manual/en/book.pcre.php){:target="_blank" rel="noreferrer noopener"}, but have not stumbled on any good in-depth documentation before. When looking at [pcre.org](http://pcre.org){:target="_blank" rel="noreferrer noopener"}, I did find a link to [Philip Hazels' PCRE2 repository](https://github.com/PhilipHazel/pcre2){:target="_blank" rel="noreferrer noopener"}, which is apparently the official source now. At an astonishing star count of 72, I reckon this has to be one of the least starred repositories for the amount of developers counting on it.
 
-Looking through the few issues I found a very interesting one: ["Caseless ASCII matching"](https://github.com/PhilipHazel/pcre2/issues/11){:target="_blank" rel="noreferrer noopener"}, talking about a particular interesting feature in unicode: "Case folding", with a [link to a list af characters that can be 'folded'](http://www.unicode.org/Public/12.1.0/ucd/CaseFolding.txt){:target="_blank" rel="noreferrer noopener"}. Including a line saying `00B5; C; 03BC; # MICRO SIGN`. Our mystery character!
+Looking through the few issues I found a very interesting one: ["Caseless ASCII matching"](https://github.com/PhilipHazel/pcre2/issues/11){:target="_blank" rel="noreferrer noopener"}, talking about a particular interesting feature in unicode: "Case folding", with a [link to a list of characters that can be 'folded'](http://www.unicode.org/Public/12.1.0/ucd/CaseFolding.txt){:target="_blank" rel="noreferrer noopener"}. Including a line saying `00B5; C; 03BC; # MICRO SIGN`. Our mystery character!
 
 With the underlying issue now found, we can now fix the problem. When we get the code point using the mb_ord function and convert it to hex, we can see the difference in the characters: