Small polish to Git Prep doc

Author: emiliom

resources/prep/git.md

@@ -42,7 +42,6 @@ git config --global core.editor "nano -w"
 Steps 1-5 focus on the Git "centralized workflow". We present it here as an illustration, but **the workflow we recommend for use in OceanHackWeek is the Git Fork - Clone workflow, discussed in Step 6.**
 ```
 
-
 ### 1. Create a project repository
 
 On your own or someone in your project group (preferably one who has never done it before), create a repository for the project under the `oceanhackweek` organization, `https://github.com/oceanhackweek`
@@ -64,7 +63,7 @@ Each participant should clone the repository so they have their copy on their Ju
 git clone https://github.com/oceanhackweek/ohw22-proj-myprojectname.git
 ```
 
-This will create a new folder called `ohw22-proj-myprojectname`. Navigate to the new folder, `ohw22-proj-myprojectname`.
+This will create a new folder called `ohw22-proj-myprojectname`. Navigate (`cd`) to this new folder.
 
 ### 3. Update the README with your name
 
@@ -82,7 +81,6 @@ Make sure your change appears online.
 `git status` to observe the changes made into your repository. Pay attention to the colors. To see the changes in the files run `git diff`.
 ```
 
-
 ### 4. Update your local repository (local clone) with the changes of your collaborators
 
 ```bash
@@ -140,7 +138,6 @@ You can continue working on as usual.
 ... to avoid messing with complicated merges and keep your repo up-to-date.
 ```
 
-
 ### 6. Avoiding problems: forking workflow
 
 So far you collaborated using what is called a "centralized git workflow": i.e. every collaborator makes directly changes to the repo.
@@ -242,6 +239,7 @@ git revert HEAD
 Your files in the local repo will still be there.
 ```
 
+
 ## References and Resources
 
 Git and GitHub are very powerful tools but no doubt the learning curve is steep. Learning is an iterative process so below we list some resources which can help you be better prepared: