spelling and grammer corrected

github-windows-vs2017-tutorial.md

@@ -22,24 +22,21 @@ Fork this repo by clicking on the fork button on the top of this page. This will
 
 GitHub keeps track of the relationship between your repo and the one you forked it from.  You can think of your repo as a working copy.
 
-Most top-level GitHub repos (i.e. ones not forked from any other repo) have a small core team of people who can directly commit changes.  All other contributors must fork the repo and make changes in the fork, then create a Pull Request 
-to ask for their changes to be merged back into the top-level repo. If the top-level repo administrator likes the changes they will be merged and you will gain instant fame and fortune!  More on how to do that later.
+Most top-level GitHub repos (i.e. ones not forked from any other repo) have a small core team of people who can directly commit changes.  All other contributors must fork the repo and make changes in the fork, then create a Pull Request to ask for their changes to be merged back into the top-level repo. If the top-level repo administrator likes the changes they will be merged and you will gain instant fame and fortune!  More on how to do that later.
 
 ## Clone your repository
 
 <img align="right" width="300" src="assets/clone.png" alt="clone this repository" />
 
-The next step is to clone your repo down to your machine so you can begin making changes. Visual Studio needs the URL of your repo, so click the clone button and then 
-click the copy to clipboard icon.
+The next step is to clone your repo down to your machine so you can begin making changes. Visual Studio needs the URL of your repo, so click the "clone" button and then click the "copy to clipboard" icon.
 
-**CAREFUL:** One mistake new contributors often make is to clone the repo you forked *from* rather than cloning your repo.  Check your browser's address bar and make sure you are cloning your repo.
+**CAREFUL:** One mistake that new contributors often make is to clone the repo you forked *from* rather than cloning your repo.  Check your browser's address bar and make sure you are cloning your repo.
 
 It is now time to jump in to Visual Studio 2017!  You will be working in the Team Explorer tab for most of this tutorial.  If it is not open by default, click `View > Team Explorer` to open it.
 
 <img src="assets/vs2017-01-clone1.png" alt="Team Explorer" />
 
-Team Explorer has many views and there are navigation buttons located at the top to help you find the different areas.  To clone a repo, you need to be on the Connect view, which should be the
-default.  If you do not see the clone button, click the green plug at the top.
+Team Explorer has many views and there are navigation buttons located at the top to help you find the different areas.  To clone a repo, you need to be on the Connect view, which should be the default.  If you do not see the 'clone' button, click the green plug at the top.
 
 Click the `Clone` option under **Local Git Repositories** and paste the URL to your repo in the text box.  This should be the URL you copied to your clipboard from GitHub previously.
 
@@ -85,19 +82,18 @@ Switch back to Team Explorer and navigate to the Changes view.
 
 <img src="assets/vs2017-09-commit1.png" alt="Changes" />
 
-Enter the information you want posted with your commits and click `Save`. Visual Studio will remember it for future commits.
+Enter the information you want to post with your commit and click `Save`. Visual Studio will remember it for future commits.
 
 <img src="assets/vs2017-10-commit2.png" alt="Git user information" />
 
 **NOTE:** Visual Studio uses a hidden folder called `.vs` to store your personal settings and preferences.  The contents of this folder **should not be saved in Git**.
 If it has not been ignored already, you may need to tell Git to ignore this folder so it does not send it up to the repo.
 
-This folder has already been ignored in this repo, so you should not have to perform this step...it is just here for your reference on future projects.
+This folder has already been ignored in this repo, so you should not have to perform this step...it is just here for your reference for future projects.
 
 <img src="assets/vs2017-11-commit3.png" alt="Ignore vs folder" />
 
-Now you should see a list of changed files and a textbox to type a commit comment.  Comments should be brief but thorough.  There is nothing worse than reading through commit comments and
-seeing this: `"I updated some stuff"`. Take a few seconds to outline your commit.  Your team will thank you later, and you might even thank yourself!
+Now you should see a list of changed files and a textbox to type a commit comment.  Comments should be in brief but thorough.  There is nothing worse than reading through commit comments and seeing this: `"I updated some stuff"`. Take a few seconds to outline your commit.  Your team will thank you later, and you might even thank yourself!
 
 Click `Commit All and Push` to perform a local commit and push your changes back up to your repo, all in one step.
 
@@ -117,10 +113,9 @@ You can view your changes by opening the `Branch: master` dropdown and selecting
 
 ## Submit your changes for review
 
-At this point you have completed your change but it still only resides in your repo.  This step will show you how to submit a request to the administrator of the top-level repo to merge your
-change.
+At this point you have completed your change but it still only resides in your repo.  This step will show you how to submit a request to the administrator of the top-level repo to merge your change.
 
-In your repo on GitHub you'll see the `Compare & pull request` button next to the new branch notification. Click that button.
+In your repo on GitHub you'll see the `Compare & pull request` button next to the new branch notification. Click on that button.
 
 <img src="assets/compare-and-pull.png" alt="create a pull request" />
 
@@ -132,11 +127,11 @@ Soon I'll be merging all your changes into the master branch of this project. Yo
 
 ## Where to go from here?
 
-Congrats!  You just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor!
+Congrats!  You have just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor!
 
 Celebrate your contribution and share it with your friends and followers by going to [web app](https://roshanjossey.github.io/first-contributions/#social-share).
 
-You could join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY).
+You can join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY).
 
 Now let's get you started with contributing to other projects. We've compiled a list of projects with easy issues you can get started on. Check out [the list of projects in web app](https://roshanjossey.github.io/first-contributions/#project-list).