Update README

- Move create puppet group before creating your own user
- specify the control-repo url instead of leaving it to the user

Author: npwalker

.gitignore

@@ -1 +1,3 @@
 hieradata/nodes/example-puppet-master.yaml
+Gemfile.lock
+_site/*

README.md

@@ -47,25 +47,25 @@ When you finish the instructions below, you will have the beginning of a best pr
 
 2. After GitLab is installed you may sign into the web UI with the `root` user and password `5iveL!fe`
 
+2. In the GitLab UI, create a group called `puppet` ( this is case sensitive )
+ - http://doc.gitlab.com/ce/workflow/groups.html
+
 3. In the GitLab UI, make a user for yourself
 
 4. From your laptop or development machine, make an SSH key to link with your user.
  - Note: this is used for your laptop to communicate with your GitLab server to push code
  - https://help.github.com/articles/generating-ssh-keys/
  - http://doc.gitlab.com/ce/ssh/README.html
 
-5. In the GitLab UI, create a group called `puppet` ( this is case sensitive )
- - http://doc.gitlab.com/ce/workflow/groups.html
-
 7. In the GitLab UI, add your user to the `puppet` group
  - Make sure to give your user at least master permissions so you can complete the below steps
  - Read more about permissions:
     - https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/permissions/permissions.md
 
 8. In the GitLab UI, create a project called `control-repo` and set its Namespace to the `puppet` group
 
-10. On your laptop, clone this GitHub control repo
- - `git clone <repo URL>`
+10. On your laptop, clone this ramp up PuppetLabs-RampUpProgram control repo
+ - `git clone https://github.com/PuppetLabs-RampUpProgram/control-repo.git`
  - `cd control-repo`
 
 14. On your laptop, remove the origin remote