Fix lint

content/english/posts/hello-world.md

@@ -40,7 +40,7 @@ cleanest blog theme out there, following Ludwig Mies van der Rohe's idea:
 
 It will be a success if more than two people actually starts reading what I
 write here, at least I want them to read this blog without having their
-eyes bleeding with an extravagant color combination. 
+eyes bleeding with an extravagant color combination.
 
 Last but not least, the website icon is literally the Team Fortress 2 dispenser
 (one of the games I love and one of the first game I started playing online as a
@@ -51,7 +51,10 @@ basically every website is a dispenser of bits, and it is only thanks to our
 beloved browsers we are able to actually "consume" what is distributed in the
 first place.
 
-{{< figure src="/content/hello-world/engiwithdispenser.png" alt="Engineer with his dispenser" caption="Engineer class with a dispenser. Thanks to [Team Fortress wiki](https://wiki.teamfortress.com) for providing the image I shamelessly downloaded from them" >}}
+{{< figure src="/content/hello-world/engiwithdispenser.png" alt="Engineer with
+his dispenser" caption="Engineer class with a dispenser. Thanks to [Team
+Fortress wiki](https://wiki.teamfortress.com) for providing the image I
+shamelessly downloaded from them" >}}
 
 I hope Valve will not sue me for taking that assed as my website favicon. I
 swear I will change it, a day. Pinky promise.
@@ -67,6 +70,7 @@ Since I like challenges and I also like to learn new stuff, I though that
 hosting the website in this way was boring. At the same time, I wanted to have a
 good uptime and to not meddle too much under the hood. My (dream) requirements
 were:
+
 * always up
 * good response time
 * possibility to host as much data as I want
@@ -100,9 +104,10 @@ simple motives:
    the slightest of loads
 2. in order to achieve a good response time, a CDN or some sort of caching is
    necessary (even if the application is stored in a distributed file system)
-   
-   
-{{< figure src="/content/hello-world/fleek.png" caption="Fleek website, that I used to automate my deployment on IPFS and my DNS update" alt="The fleek website screenshot" class="right" >}}
+
+{{< figure src="/content/hello-world/fleek.png" caption="Fleek website, that I
+used to automate my deployment on IPFS and my DNS update" alt="The fleek website
+screenshot" class="right" >}}
 
 Finally, in order to achieve full automation with DNS updates, I would have
 needed to implement and use NameCheap APIs (currently it is the DNS provider I
@@ -133,4 +138,7 @@ this website could be an automatic posting of every new article on a dedicated
 Mastodon bot, so that people can possibly discuss about my thoughts on the
 fediverse, a decentralized network.
 
-To conclude, the frequency of this blog will be...whenever I have time to post :grin: Of course I need content before posting something, and this require some time for myself for experimenting with new technologies and learning new stuff, so I do not expect very much posting, but only time will tell!
+To conclude, the frequency of this blog will be...whenever I have time to post
+:grin: Of course I need content before posting something, and this require some
+time for myself for experimenting with new technologies and learning new stuff,
+so I do not expect very much posting, but only time will tell!

package.json

@@ -4,7 +4,7 @@
     "description": "Personal Hugo website",
     "main": "none.js",
     "scripts": {
-        "lint": "markdownlint-cli2 content/posts/"
+        "lint": "markdownlint-cli2 content/"
     },
     "repository": {
         "type": "git",