Merge pull request #128 from thiyagu-sada/tech-doc-updates

Tech doc updates

LGTM great stuff thanks @thiyagu-sada !

Author: eformat

docs/1-the-manual-menace/1-the-basics.md

@@ -48,6 +48,10 @@ oc new-project ${TEAM_NAME}-ci-cd
 ```
 ![new-project](./images/new-project.png)
 
+<p class="warn">
+    ⛷️ <b>NOTE</b> ⛷️ - If you are working as a team and are using the same TEAM_NAME, you may receive a message saying this project already exists. One of your team mates would have already created this project. It's all good!
+  </p>
+
 ### Helm 101
 > Helm is the package manager for Kubernetes. It provides a way to create templates for the Kubernetes YAML that defines our application. The Kubernetes resources such as `DeploymentConfig`, `Route` & `Service` can be processed by supplying `values` to the templates. In Helm land, there are a few ways to do this. A package containing the templates and their default values is called a `chart`. 
 

docs/1-the-manual-menace/3-ubiquitous-journey.md

@@ -28,13 +28,16 @@ All of these traits lead to one outcome - the ability to build and release quali
 2. Put your TEAM_NAME (`<TEAM_NAME>`) as the group name, select **Public** for Visibility level, and hit Create group. This is so we can easily share code and view other teams' activity.
 ![gitlab-create-group](images/gitlab-create-group.png)
 
-3. Now lets create the git repository that we are going to use for <span style="color:purple;" >GIT</span>Ops purposes. The `tech-exercise` will serve as a mono-repo holding both our tooling configuration and the application definitions and some other stuff. In the real world, you may want to separate these into different repos! Anyways, hit `New project` button on the right hand side
+3. If you are working as a team, you must add your team members to this group. This will give them permissions to work on the projects created in this group. Select "Members" from the left panel and invite your team members via "Invite member" option. Make sure to choose "Maintainer" or "Owner" role permission. You can ignore this step if your are not working as a team.
+![gitlab-group-add-members](images/gitlab-group-add-members.png)
+
+4. Now lets create the git repository that we are going to use for <span style="color:purple;" >GIT</span>Ops purposes. The `tech-exercise` will serve as a mono-repo holding both our tooling configuration and the application definitions and some other stuff. In the real world, you may want to separate these into different repos! Anyways, hit `New project` button on the right hand side
 ![gitlab-new-project](images/gitlab-new-project.png)
 
-4. On the new view, use `tech-exercise` as Project Name, select **Internal** for Visibility level, then hit Create project. Make sure the project is in the group you created previously and not the username's.
+5. On the new view, use `tech-exercise` as Project Name, select **Internal** for Visibility level, then hit Create project. Make sure the project is in the group you created previously and not the username's.
 ![gitlab-new-project](images/gitlab-new-project-2.png)
 
-5. Let's push our code to the GitLab server. Back in your CodeReady Workspace, open a terminal if you have not got one open.
+6. Let's push our code to the GitLab server. Back in your CodeReady Workspace, open a terminal if you have not got one open.
 
     ```bash
     cd /projects/tech-exercise