From 60da23c99ef6f8fa94bdb7a1a9db9057e16cbd84 Mon Sep 17 00:00:00 2001
From: Anshul Zilpe <147277311+aNsHuL5217@users.noreply.github.com>
Date: Mon, 8 Dec 2025 21:23:00 +0530
Subject: [PATCH] Update CONTRIBUTING.md

Co-authored-by: Pablo Brasero <36066+pablobm@users.noreply.github.com>
---
 CONTRIBUTING.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0c6b1f89d..0ced8a1c4 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -197,7 +197,8 @@ For simple commits the one line summary is often enough and the body of the comm
 If you have forked on GitHub then the best way to submit your patches is to push your changes back to GitHub and open a Pull Request on GitHub.
 
 If your pull request is small, for example one or two commits each containing only a few lines of code, then it is easy for the maintainers to review.
-Please ensure your commit history is clean. Avoid including "fixup" commits. If you have added a fixup commit (for example to fix a rubocop warning, or because you changed your own new code) please combine the fixup commit into the commit that introduced the problem. `git rebase -i` is very useful for this.
+
+Please ensure your commit history is clean and avoid including "fixup" commits. If you have added a fixup commit (for example to fix a rubocop warning, or because you changed your own new code) please combine the fixup commit into the commit that introduced the problem. `git rebase -i` is very useful for this.
 
 > [!IMPORTANT]
 > If you are creating a larger pull request, then please help the maintainers with making the reviews as straightforward as possible:
-- 
2.39.5