Merge pull request #2134 from za4g/patch-1

Update how-to-use-git-version-control-system.md

src/content/lesson/how-to-use-git-version-control-system.md

@@ -81,7 +81,7 @@ You can **move the head** if you want. It does not necessarily have to always be
 
 Heads mark the beginning of a revision history. In GIT, we call the "revision history" a "branch", and it is possible to have several revision histories.
 
-By default, every repository has one branch called Master, with its corresponding HEAD that points to the last commit of that branch.
+By default, every repository has one branch called Main (earlier known as Master), with its corresponding HEAD that points to the last commit of that branch.
 
 For example: Let’s say that you are starting to develop the "Login" feature/functionality of a website. You can create a new "branch" of the repository called "login" so that your commits are not part of the main revision history of the project. Once you are comfortable with your code, you can then *merge* your branch and delete your head. This will reset the main HEAD of the master branch to the last commit you made and add your new code to the main branch (master) of the repository.