From 2a4a36aa581c8ff5efe0146c5e4153a1ff7ef183 Mon Sep 17 00:00:00 2001
From: Varad Dixit <143983431+Hatkeshiator@users.noreply.github.com>
Date: Sun, 27 Jul 2025 01:02:40 +0530
Subject: [PATCH] fix minor spelling mistake in contributing guidelines

---
 CONTRIBUTING.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index dd351c31bd..896faae861 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -4,12 +4,12 @@
    If additional reviewers gave their ack, a proper attribution
    header may be added.
 
-2. Commit messages should explain what's really done here and their
-   headlines need a short an precise subject. See history for examples.
+2. Commit messages should explain what's really done here, and their
+   headlines need a short and precise subject. See history for examples.
 
    Keep in mind that history is also a piece of documentation.
 
-3. Once release is out, bugfixes should be submitted separately, against
+3. Once a release is out, bugfixes should be submitted separately, against
    the affected release branch(es) as well as master (so multiple pull requests)
 
 4. If new functions or types are introduced, these should be documented