Improve clarity in documentation wording

## What
Improved clarity in documentation by refining sentence wording.

## Why
The updated wording removes redundancy and improves readability.

## Changes
- Minor wording improvement

## Notes
This is a documentation-only change. Verified manually.

Author: 24f2001045-DS

content/get-started/using-github/github-flow.md

@@ -41,7 +41,7 @@ On your branch, make any desired changes to the repository. For more information
 
 Your branch is a safe place to make changes. If you make a mistake, you can revert your changes or push additional changes to fix the mistake. Your changes will not end up on the default branch until you merge your branch.
 
-Commit and push your changes to your branch. Give each commit a descriptive message to help you and future contributors understand what changes the commit contains. For example, `fix typo` or `increase rate limit`.
+Commit and push your changes to your branch. Give each commit a descriptive message to help you and future contributors understand the changes it contains. For example, `fix typo` or `increase rate limit`.
 
 Ideally, each commit contains an isolated, complete change. This makes it easy to revert your changes if you decide to take a different approach. For example, if you want to rename a variable and add some tests, put the variable rename in one commit and the tests in another commit. Later, if you want to keep the tests but revert the variable rename, you can revert the specific commit that contained the variable rename. If you put the variable rename and tests in the same commit or spread the variable rename across multiple commits, you would spend more effort reverting your changes.