diff --git a/docs/how-to-setup-freecodecamp-locally.md b/docs/how-to-setup-freecodecamp-locally.md
index 232a856b00..f419f73257 100644
--- a/docs/how-to-setup-freecodecamp-locally.md
+++ b/docs/how-to-setup-freecodecamp-locally.md
@@ -254,7 +254,7 @@ Follow these steps:
 
     **Note:** If you have any outstanding pull-request that you made from the `master` branch of your fork previously, you will lose them. You should get it merged by a moderator, prior following this. To avoid this, you should always work on a branch.
 
-    Its recommended that you do this as often as possible, to avoid conflicts later:
+    This step **will sync the latest changes** from the main repository of freeCodeCamp. It is important that you rebase as often as possible, to avoid conflicts later.
 
     ```shell
     git fetch upstream
@@ -298,7 +298,7 @@ Follow these steps:
 
 5. Once you are happy with the changes you should optionally run freeCodeCamp locally to preview the changes.
 
-6. Make sure you fix any errors, and check the formating of your changes. We have style guide for the Guide articles and Coding challenges.
+6. Make sure you fix any errors, and check the formatting of your changes. We have style guide for the Guide articles and Coding challenges.
 
 7. Next, check and confirm the files you are updating
 
@@ -385,7 +385,7 @@ Follow these steps:
 
     Keep these short, not more than 50 characters. You can always add additional information in the description of the commit message.
 
-    This does not take any additional time than a unconventional message like 'update file' or 'add index.md'
+    This does not take any additional time than an unconventional message like 'update file' or 'add index.md'
 
     You can learn more about why you should use conventional commits [here](https://www.conventionalcommits.org/en/v1.0.0-beta.2/#why-use-conventional-commits).