From 884db352d888acf6a069da66ebf91022046c51e8 Mon Sep 17 00:00:00 2001
From: Rahim Afroz <108648650+afroz01@users.noreply.github.com>
Date: Wed, 13 Mar 2024 19:32:09 -0400
Subject: [PATCH] Update how-to-use-git-version-control-system.md

---
 src/content/lesson/how-to-use-git-version-control-system.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/lesson/how-to-use-git-version-control-system.md b/src/content/lesson/how-to-use-git-version-control-system.md
index 9db25aae7..5d90136e6 100644
--- a/src/content/lesson/how-to-use-git-version-control-system.md
+++ b/src/content/lesson/how-to-use-git-version-control-system.md
@@ -20,7 +20,7 @@ GIT is a great technology, please take the time to learn it. DON’T procrastina
 
 GIT is more than just a "set of commands" that you have to learn. Throughout the years, we have learned that the best way to teach GIT is by understanding the concepts and meaning of the technology first, rather than just giving you a list of commands to use.
 
-## Why Bother to use GIT?
+## Why bother to use GIT?
 
 Being the only developer in a project is a [utopia](http://www.thefreedictionary.com/Utopic). Normally, you collaborate with other developers, and, without GIT, that becomes a big problem. That’s why we need a *repository* of information to centralize and manage changes. With a *repository*, we are addressing the following: