From 034b0f9c4124637402ed43ac1391f3e256984df0 Mon Sep 17 00:00:00 2001
From: acammies <acammies@redhat.com>
Date: Tue, 17 Apr 2018 16:25:26 +0200
Subject: [PATCH] more additions but mainly small fixes all over

---
 exercises/0-rogue-cluster/README.md                    |    4 ++--
 exercises/2-attack-of-the-pipelines/README.md          |    4 ++--
 exercises/3-revenge-of-the-automated-testing/README.md |    1 +
 3 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/exercises/0-rogue-cluster/README.md b/exercises/0-rogue-cluster/README.md
index 61e32ab..3d92289 100644
--- a/exercises/0-rogue-cluster/README.md
+++ b/exercises/0-rogue-cluster/README.md
@@ -22,6 +22,6 @@
  - Learners have access to LDAP bind credentials to be able to auth against gitlab 
  - 
  
-## User privaleges 
- - Learners will require privaleges to run SCC containers ie GitLab
+## User privileges 
+ - Learners will require privileges to run SCC containers ie GitLab
  - 
diff --git a/exercises/2-attack-of-the-pipelines/README.md b/exercises/2-attack-of-the-pipelines/README.md
index ab0d3a2..8e872b0 100644
--- a/exercises/2-attack-of-the-pipelines/README.md
+++ b/exercises/2-attack-of-the-pipelines/README.md
@@ -106,7 +106,7 @@
     * The server hosting it live reloads; so as you make changes to your code; the app will live update
     * The Data you see in the screen is dummy / stubbed data. This is served up when there is no backend connection found
 
-2. The app is a todolist manager built in Vue.js. Play around with the App. You will notice when you add todos they appear and clear as expected. If you refresh the page you'll loose all additions. This is because there is persistence
+2. The app is a todolist manager built in Vue.js. Play around with the App. You will notice when you add todos they appear and clear as expected. If you refresh the page you'll lose all additions. This is because there is persistence
 
 3. The structure of the `todolist-fe` is as follows.
 ```bash
@@ -431,7 +431,7 @@
 
 5. Name this job `dev-todolist-fe-build` and select `Freestyle Job`. All our jobs will take the form of `<ENV>-<APP_NAME>-<JOB_PURPOSE>`. ![freestyle-job](../images/exercise2/freestyle-job.png)
 
-5. The page that loads is the Job Configuration page andi t can be returned to at anytime from Jenkins. Let's start configuring our job. To conserve space; we will make sure Jenkins only keeps the last builds artifacts. Tick the `Discard old builds` checkbox and set `Max # of builds to keep with artifacts` to 1 as below ![keep-artifacts](../images/exercise2/keep-artifacts.png)
+5. The page that loads is the Job Configuration page and it can be returned to at anytime from Jenkins. Let's start configuring our job. To conserve space; we will make sure Jenkins only keeps the last builds artifacts. Tick the `Discard old builds` checkbox and set `Max # of builds to keep with artifacts` to 1 as below ![keep-artifacts](../images/exercise2/keep-artifacts.png)
 
 5. Our NodeJS build needs to be run on the `jenkins-slave-npm` we created earlier. Specify this in the box labelled `Restrict where this project can be run` ![label-jenkins-slave](../images/exercise2/label-jenkins-slave.png)
 
diff --git a/exercises/3-revenge-of-the-automated-testing/README.md b/exercises/3-revenge-of-the-automated-testing/README.md
index 158be6c..a9464eb 100644
--- a/exercises/3-revenge-of-the-automated-testing/README.md
+++ b/exercises/3-revenge-of-the-automated-testing/README.md
@@ -82,6 +82,7 @@
 ![todoitem-fail-test](../images/exercise3/bdd-bananas.png)
 
 
+
 ### Part 1 - Tests in our Pipeline
 
 > _In this exercise we will improve the pipeline created already by adding some unit tests for the frontend & backend along with some end to end tests (e2e) to validate the full solution_

--
Gitblit v1.9.3