Be more specific

README.md

@@ -11,3 +11,12 @@ All exercises in this repository practice a self-contained portion of the [CJE c
 ## Exercises
 
 All [exercises](./exercises) are numbered and live in dedicated directories starting with the name `exercise-`. You'll find instructions for each exercise in each folder. Solutions are available in the `solution` folder. Try to solve each exercise yourself before having a look at the solution.
+
+## Additional Resources
+
+* [CloudBees certification information](https://www.cloudbees.com/jenkins/certification)
+* [Certified Jenkins Engineer (CJE) 2018 study guide](https://www.previous.cloudbees.com/sites/default/files/cje-study-guide-2018.pdf)
+* [CJE video training by CloudBees University](https://standard.cbu.cloudbees.com/series/certified-jenkins-engineer-exam-prep)
+* [CJE video training and practice test by Linux Academy](https://linuxacademy.com/course/learn-jenkins-by-doing/)
+* [Best practices for writing Jenkins shared libraries](https://bmuschko.com/blog/jenkins-shared-libraries/)
+* [Step by step instructions on how to use the Jenkins Kubernetes plugin for different use cases](https://github.com/bmuschko/jenkins-with-kubernetes)

exercises/03-build-trigger-and-steps/instructions.md

@@ -6,7 +6,7 @@ In this exercise, you will configure the job to build based on a cron definition
 
 1. Add a default value for the build parameter named `MESSAGE` e.g. `Hello World!`.
 2. Create a build trigger that builds the project every minute.
-3. Add a build step that executes the shell command `echo "Message: $MESSAGE"`. The message is value of the parameter.
+3. Add a build step that executes the shell command `echo "Message: $MESSAGE"`. The message is value of the parameter. On Windows, you have to execute a Windows batch command.
 4. After a minute the first execution should have been triggered. Check the log output of the build and find the rendered message.
 5. Create another freestyle project named `downstream-job` in the same folder.
 6. Configure the initial job to execute the `downstream-job` if it was stable.

exercises/04-scm-configuration/instructions.md

@@ -1,10 +1,10 @@
 # Exercise 4
 
-In this exercise, you will create a new job that pulls the source code from a repository on GitHub. Upon triggering a build, the job will execute a Gradle build.
+In this exercise, you will create a new job that pulls the source code from a [repository on GitHub](https://github.com/bmuschko/gradle-initializr) named Gradle Initializr. Upon triggering a build, the job will execute a Gradle build.
 
 ## Configuring a GitHub Repository
 
 1. Create a new freestyle job named `gradle-initializr`.
-2. Configure Git as the SCM and use the repository URL `git@github.com:bmuschko/gradle-initializr.git`. Only build from the branch `master`.
-3. Add a build step to run the Gradle command `clean build` using the Wrapper.
+2. Configure Git as the SCM and use the repository URL `https://github.com/bmuschko/gradle-initializr.git`. Only build from the branch `master`.
+3. Add a build step "Invoke Gradle script" to run the Gradle command `clean build` using the Wrapper.
 4. Trigger a build and look at the output.