Update keeping-your-fork-synced-with-this-repository.md

Created by: blaringblazehs

added some better lines for the text

additional-material/git_workflow_scenarios/keeping-your-fork-synced-with-this-repository.md

 # Keeping your fork synced with this repository
 
-First, the flow for a full sync should be understood. In this schema, there are 3 different repos: my public repo on Github `github.com/Roshanjossey/first-contributions/`, your fork of the repo on GitHub `github.com/Your-Name/first-contributions/` and your local machine's repo from which you are suppose to work. This kind of cooperation is typical for open source projects and called `Triangle Workflows`.
+First, the flow for a full sync should be understood, which is important. In this schema, there are 3 different repos: my public repo on Github `github.com/Roshanjossey/first-contributions/`, your fork of the repo on GitHub `github.com/Your-Name/first-contributions/` and your local machine's repo from which you are suppose to work. This kind of cooperation is typical for open source projects and called `Triangle Workflows`.
 
 <img style="float;" src="../../assets/triangle_workflow.png" alt="triangle workflow" />
 
-To keep your two repos up-to-date with my public repo, our first move is to fetch and merge the public repo with your local machine's repo.
+To keep your two repos up-to-date with my public repo, so first we have to  fetch and merge the public repo with your local machine's repo.
 Our second move will be to push your local repo to your GitHub fork. As you've seen earlier, it's only from your fork that you can ask for a "pull request". So your GitHub fork is the last repo to be updated.
 
 Now, let's see how to do it:
@@ -37,4 +37,4 @@ git push origin master
 ```
 Notice here you're pushing to the remote named `origin`.
 
-At this point, all your repositories are up-to-date. Well done! You should do this, everytime your GitHub repo tells you that you are a few commits behind.
+So by now or at this point, all your repositories are up-to-date. Well done! You should do this, everytime your GitHub repo tells you that you are a few commits behind.