diff --git a/src/posts/2023-10-18-obligations.dj b/src/posts/2023-10-18-obligations.dj
index ba4a535c..5ee49beb 100644
--- a/src/posts/2023-10-18-obligations.dj
+++ b/src/posts/2023-10-18-obligations.dj
@@ -48,7 +48,7 @@ So, if you, as an open-source maintainer, publish your software and gain users,
 yourself: "do I actually want to have users?". It is totally fine if the answer is "no"! It is a
 safe default answer and what governs most of the git repositories out there.
 
-Never the less, if the answer to the users question is "no", you should make it clear in your Readme
+Never the less, if the answer to question of users is "no", you should make it clear in your Readme
 that it is a hobby, non-production-ready project which isn't intended to be used by anyone but you.
 Usually, it's enough to just not have a readme at all, or have a very short readme which makes it
 obvious that the project isn't supported.