fix: update the images again

this better fucking work

Author: willtheorangeguy

src/content/blog/switching-from-utterances-to-giscus.md

@@ -21,14 +21,14 @@ A while ago, I stumbled upon [utterances](https://utteranc.es/), which easily al
 
 Here is what it looks like on this blog:
 
-![Blog post with utterances comments](/assets/imgs/blog/utterances)
+![Blog post with utterances comments](/assets/imgs/blog/utterances.jpg)
 
 This was super easy and I was happy to (hopefully) drive more engagement thanks to the comments. The only annoying part was that I was going to have a ton of open issues acting as comments for the blog posts... Luckily, a few days ago, I came across another blog (which I unfortunately don't remember - otherwise I would have linked it here) and saw that they were using [giscus](https://giscus.app/).
 
 giscus is clearly heavily inspired by utterances, and their website is pretty much the same thing, so you can follow the same easy steps to add it to your site or blog. The benefit of using giscus? It uses GitHub Discussions for the comments, meaning you won't have any unnecessary open GitHub Issues. I also think this is a better platform for blog comments, since Discussions allows for a more forum-like commenting and discussion experience. Another benefit is that giscus is [still under active development](https://github.com/giscus/giscus/commits/main/), whereas utterances was [last updated two years ago](https://github.com/utterance/utterances/commits/master/). Regardless, both are still open source on GitHub and great options to use!
 
 Here is what the comment section currently looks like with giscus:
 
-![Blog post with giscus comments](/assets/images/blog/giscus.jpg)
+![Blog post with giscus comments](/assets/imgs/blog/giscus.jpg)
 
 Oh - giscus also has support for reactions!