From f87416c022572b48e6667368b4ea9dc1d7c59bff Mon Sep 17 00:00:00 2001
From: Balazs Kezes <3j4b0y1i@anonaddy.me>
Date: Sat, 3 Aug 2024 09:38:49 +0200
Subject: [PATCH] Fix typo

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index b4e5847..e55f73d 100644
--- a/README.md
+++ b/README.md
@@ -70,7 +70,7 @@ The MAJOR.YYMMDD.PATCH versioning scheme has 3 components:
 
 The MAJOR part of the version number is manually incremented whenever an incompatible change is being made or otherwise a manual update is desired.
 
-MAJOR version is 0 is special though: the 6 month compatibility guarantee doesn't apply there.
+MAJOR version 0 is special though: the 6 month compatibility guarantee doesn't apply there.
 It's meant to be used for development versions.
 It might make sense for the v0 branch to not follow YYMMDD for the middle part of the version but something like YYMMDDHHMMSS.
 E.g. a continuous build tool might be making v0 versions after each commit and then a weekly cronjob just stamps a v1 version tag on the latest green v0 version.