fix typos

diff --git a/posts/05-05-2026-how-i-read-500-page-books-in-a-weekend.html b/posts/05-05-2026-how-i-read-500-page-books-in-a-weekend.html
index 35095fbfc71c0e006eb965fba1c4cd08023f5d42..61660e9201fa6dcea5400459c28b02e95f875e19 100644 (file)
--- a/posts/05-05-2026-how-i-read-500-page-books-in-a-weekend.html
+++ b/posts/05-05-2026-how-i-read-500-page-books-in-a-weekend.html
@@ -32,8 +32,8 @@
     <p>
     Another point is that most of the times, if a programming book is 500 pages long, chances are most of its
     contents is not 100% relevant. The book I'm reading right now for example is full with the author's "humor."
-    Humor in programming books is welcome, at least by me, in sparse quantities. If I wanted to laugh I'd listen to 
-    audios of americans speaking french instead.
+    Humor in programming books is welcomed, at least by me, in sparse quantities. If I wanted to laugh I'd listen to 
+    audios of americans trying to speak French instead.
     </p>
     <p>
     So yeah, the key to reading programming books fast is reading so many of them that you can skim/skip a lot.