added notes on running nodejs on Windows

01 Setup.md

@@ -35,6 +35,8 @@ Locate the green **Clone or Download** button and click this. You will see the o
 
 ![The Clone Button](exercises/.images/clone01.png)
 
+Make sure the url begins with `https://`, if it begins with `git` you need to click in the small **Use HTTPS** link!
+
 Launch the **terminal** app (Mac and Linux users) or Bash Shell (Windows 10 users). Now use this to navigate to the directory where you want to store the lab materials. You should use the following bash commands:
 
 1. `ls` is used to see the contents of the current directory.
@@ -64,14 +66,56 @@ If you are using Windows 10 you will need to carry out some additional steps bef
 
 This will open a new Git Bash shell in the project directory.
 
-## 3 Pushing the Changes to GitHub
+## 3 Installing NodeJS
+
+Next we need to install and configure NodeJS. If you are using MacOS or Linux the first task is to install the Node Version Manager tool. You can find detailed [instructions](https://nodesource.com/blog/installing-node-js-tutorial-using-nvm-on-mac-os-x-and-ubuntu/).
+
+Once installed you may need to restart your computer. Now check it was installed correctly:
+
+```bash
+$ command -v nvm
+  nvm
+```
+
+Now we can install the latest version of NodeJS:
+
+```bash
+nvm install node
+node -v
+```
+
+If you are running Windows 10 you need to [download the installer](https://nodejs.org/en/) for the **Current** version of NodeJS (12.10 at the time of writing).
+
+## 4 Running a Web Server
+
+Use the terminal to navigate to the `exercises/01_setup/` directory and try running the `index.js` script:
+
+```shell
+$ cd exercises/01_setup/
+$ node index.js
+  Error: Cannot find module 'koa'
+```
+
+If you are using Windows 10 you will need to use the command prompt instead and navigate to the `01_setup/` directory.
+
+Notice you get an error, we need to install the missing module using the _Node Package Manager_ tool. We can then try to run the script again:
+
+```shell
+$ npm install koa
+$ node index.js
+  app listening on port 8080
+```
+
+Now we have the server up and running so the final task is to view the web page using the web browser. Simply open the Chrome browser and navigate to localhost:8080 where you should see a message. If this works you are ready to start the lab exercises.
+
+## 5 Pushing the Changes to GitHub
 
 As you work through the lab activities two things are likely to happen:
 
 1. You make changes to the code that you want to push to the forked copy of your repository.
 2. You will need to pull any bug fixes from the original repository.
 
-### 3.1 Configuring the Repository
+### 5.1 Configuring the Repository
 
 Before you start interacting with the GitHub server you need to configure the local repository. Open the Bash Shell and run the following commands:
 
@@ -82,7 +126,9 @@ git config user.email 'doej@coventry.ac.uk'
 
 remember to replace the values with you own name and your university email (but without the uni part).
 
-### 3.2 Pushing Changes
+### 5.2 Pushing Changes
+
+**NOTE: You only need to carry out this step when you have make changes to the code! This will normally need to take place each time you complete a "Test Your Understanding" section.**
 
 As you save your changes you will see a blue circle against the **Source Control** tab that indicates how many files have been changed, we need to get these changed files up to GitHub. Start by opening the tab, you will see a list of all the files you have changed.
 
@@ -98,9 +144,9 @@ Now you should click on the **Sync** icon (shown below) to push the new commit u
 
 At this point you should be able to refresh your GitHub repository page to see the changes.
 
-### 3.3 Pulling from Upstream
+### 5.3 Pulling from Upstream
 
-As changes are made to the master repository you will want to merge these into your forked repository. Before you can do this you will need to add a link to the upstream repository. Open a bash shell:
+As new materials and resources are added to the original repository (and bugs fixed) you will want to merge these into your forked repository. Before you can do this you will need to add a link to the upstream repository. Open a bash shell:
 
 ```bash
 git remote add upstream https://github.coventry.ac.uk/web/foundation.git
@@ -116,43 +162,3 @@ git merge upstream/master
 ```
 
 Don't worry if you don't understand what is happening, this will be explained in a future lab.
-
-## 4 Installing NodeJS
-
-Next we need to install and configure NodeJS. If you are using MacOS or Linux the first task is to install the Node Version Manager tool. You can find detailed [instructions](https://nodesource.com/blog/installing-node-js-tutorial-using-nvm-on-mac-os-x-and-ubuntu/).
-
-Once installed you may need to restart your computer. Now check it was installed correctly:
-
-```bash
-$ command -v nvm
-  nvm
-```
-
-Now we can install the latest version of NodeJS:
-
-```bash
-nvm install node
-node -v
-```
-
-If you are running Windows 10 you need to [download the installer](https://nodejs.org/en/) for the **Current** version of NodeJS (12.10 at the time of writing).
-
-## 5 Running a Web Server
-
-Use the terminal to navigate to the `exercises/01_setup/` directory and try running the `index.js` script:
-
-```shell
-$ cd exercises/01_setup/
-$ node index.js
-  Error: Cannot find module 'koa'
-```
-
-Notice you get an error, we need to install the missing module using the _Node Package Manager_ tool. We can then try to run the script again:
-
-```shell
-$ npm install koa
-$ node index.js
-  app listening on port 8080
-```
-
-Now we have the server up and running so the final task is to view the web page using the web browser. Simply open the Chrome browser and navigate to localhost:8080 where you should see a message. If this works you are ready to start the lab exercises.