refactoring installation doc (#43)

Signed-off-by: Raj Das <mail.rajdas@gmail.com>

Author: imrajdas

website/docs/agent-installation.md

@@ -61,42 +61,42 @@ To install the latest version of litmusctl follow the below steps:
 
 - Extract the binary
 
-```shell
-$ tar -zxvf litmusctl-<OS>-<ARCH>-<VERSION>.tar.gz
+```bash
+tar -zxvf litmusctl-<OS>-<ARCH>-<VERSION>.tar.gz
 ```
 
 - Provide necessary permissions
 
-```shell
-$ chmod +x litmusctl
+```bash
+chmod +x litmusctl
 ```
 
 - Move the litmusctl binary to /usr/local/bin/litmusctl
 
-```shell
-$ sudo mv litmusctl /usr/local/bin/litmusctl
+```bash
+sudo mv litmusctl /usr/local/bin/litmusctl
 ```
 
 ## Basic Commands
 
 litmusctl CLI command has the following structure:
 
-```shell
-$ litmusctl <command> <subcommand> <subcommand> [options and parameters]
+```bash
+litmusctl <command> <subcommand> <subcommand> [options and parameters]
 ```
 
 To get the version of the litmusctl CLI:
 
-```shell
-$ litmusctl version
+```bash
+litmusctl version
 ```
 
 ### Connecting an agent
 
 To connect Litmus Chaos agent:
 
-```shell
-$ litmusctl agent connect
+```bash
+litmusctl agent connect
 ```
 
 Next, you need to enter LitmusPortal details to login into your LitmusPortal account. Fields to be filled in:
@@ -107,7 +107,7 @@ Example, http://172.17.0.2:31696/
 **Username:** Enter your LitmusPortal username.
 **Password:** Enter your LitmusPortal password.
 
-```shell
+```bash
 🔥 Connecting LitmusChaos agent
 
 📶 Please enter LitmusChaos details --
@@ -119,7 +119,7 @@ Example, http://172.17.0.2:31696/
 
 Upon successful login, there will be a list of exiting projects displayed on the terminal. Select the desired project by entering the sequence number indicated against it.
 
-```shell
+```bash
 ✨ Projects List:
 1.  abc
 

website/docs/litmus-installation-cluster.md

@@ -32,14 +32,8 @@ The following steps will help you install litmus via helm.
 #### Step-1: Add the litmus helm repository
 
 ```bash
-root@demo:~# helm repo add litmuschaos https://litmuschaos.github.io/litmus-helm/
-"litmuschaos" has been added to your repositories
-```
-
-```bash
-root@demo:~# helm repo list
-NAME            URL
-litmuschaos     https://litmuschaos.github.io/litmus-helm/
+helm repo add litmuschaos https://litmuschaos.github.io/litmus-helm/
+helm repo list
 ```
 
 #### Step-2: Create the litmus namespace
@@ -49,14 +43,13 @@ litmuschaos     https://litmuschaos.github.io/litmus-helm/
 **Note**: The chaos control plane can be placed in any namespace, though it is typically placed in "litmus".
 
 ```bash
-root@demo:~# kubectl create ns litmus
-namespace/litmus created
+kubectl create ns litmus
 ```
 
 #### Step-3: Install the litmus chaos control plane
 
 ```bash
-root@demo:~# helm install chaos litmuschaos/litmus-2-0-0-beta --namespace=litmus --devel
+helm install chaos litmuschaos/litmus-2-0-0-beta --namespace=litmus --devel
 ```
 
 <span style={{color: 'green'}}><b>Expected Output</b></span>
@@ -74,7 +67,6 @@ Thank you for installing litmus-2-0-0-beta 😀
 Your release is named chaos and its installed to namespace: litmus.
 
 Visit https://docs.litmuschaos.io/docs/getstarted/ to find more info.
-
 ```
 
 > **Note:** Litmus uses Kubernetes CRDs to define chaos intent. Helm3 handles CRDs better than Helm2. Before you start running a chaos experiment, verify if Litmus is installed correctly.

website/docs/litmus-installation-namespace.md

@@ -32,14 +32,8 @@ The following steps will help you install litmus via helm.
 #### Step-1: Add the litmus helm repository
 
 ```bash
-root@demo:~# helm repo add litmuschaos https://litmuschaos.github.io/litmus-helm/
-"litmuschaos" has been added to your repositories
-```
-
-```bash
-root@demo:~# helm repo list
-NAME            URL
-litmuschaos     https://litmuschaos.github.io/litmus-helm/
+helm repo add litmuschaos https://litmuschaos.github.io/litmus-helm/
+helm repo list
 ```
 
 #### Step-2: Create the litmus namespace
@@ -49,14 +43,13 @@ litmuschaos     https://litmuschaos.github.io/litmus-helm/
 **Note**: The chaos control plane can be placed in any namespace, though it is typically placed in "litmus".
 
 ```bash
-root@demo:~# kubectl create ns litmus
-namespace/litmus created
+kubectl create ns litmus
 ```
 
 #### Step-3: Install the litmus chaos control plane
 
 ```bash
-root@demo:~# helm install chaos litmuschaos/litmus-2-0-0-beta --namespace=litmus --devel --set portalScope=namespace
+helm install chaos litmuschaos/litmus-2-0-0-beta --namespace=litmus --devel --set portalScope=namespace
 ```
 
 <span style={{color: 'green'}}><b>Expected Output</b></span>
@@ -85,7 +78,7 @@ Visit https://docs.litmuschaos.io/docs/getstarted/ to find more info.
 kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/litmus-portal/litmus-portal-crds.yml
 ```
 
-Output:
+<span style={{color: 'green'}}><b>Expected Output</b></span>
 
 ```bash
 customresourcedefinition.apiextensions.k8s.io/clusterworkflowtemplates.argoproj.io created
@@ -118,7 +111,7 @@ kubectl create ns ${LITMUS_PORTAL_NAMESPACE}
 kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/litmus-portal/litmus-portal-crds.yml
 ```
 
-Output:
+<span style={{color: 'green'}}><b>Expected Output</b></span>
 
 ```bash
 customresourcedefinition.apiextensions.k8s.io/clusterworkflowtemplates.argoproj.io created
@@ -141,7 +134,7 @@ ${LITMUS_PORTAL_NAMESPACE}-ns-scoped-litmus-portal-manifest.yml
 kubectl apply -f ${LITMUS_PORTAL_NAMESPACE}-ns-scoped-litmus-portal-manifest.yml -n ${LITMUS_PORTAL_NAMESPACE}
 ```
 
-Output:
+<span style={{color: 'green'}}><b>Expected Output</b></span>
 
 ```bash
 configmap/litmus-portal-admin-config created
@@ -160,22 +153,15 @@ service/mongo-service created
 
 **Verify if the frontend, server, and database pods are running**
 
-- Check the litmus CRDs:
+- Check the pods in litmus namespace:
 
   ```bash
-  $ kubectl get crds | grep litmus
-  chaosengines.litmuschaos.io                        2021-03-24T06:52:54Z
-  chaosexperiments.litmuschaos.io                    2021-03-24T06:52:54Z
-  chaosresults.litmuschaos.io                        2021-03-24T06:52:55Z
-  eventtrackerpolicies.eventtracker.litmuschaos.io   2021-03-24T06:52:55Z
-
+  kubectl get pods -n litmus
   ```
 
-- Check the pods in litmus namespace:
-
+  <span style={{color: 'green'}}><b>Expected Output</b></span>
+  
   ```bash
-  $ kubectl get pods -n litmus
-
   NAME                                    READY   STATUS  RESTARTS  AGE
   litmusportal-frontend-97c8bf86b-mx89w   1/1     Running 2         6m24s
   litmusportal-server-5cfbfc88cc-m6c5j    2/2     Running 2         6m19s
@@ -185,8 +171,12 @@ service/mongo-service created
 - Check the services running in litmus namespace:
 
   ```bash
-  $ kubectl get svc -n litmus
+  kubectl get svc -n litmus
+  ```
+
+  <span style={{color: 'green'}}><b>Expected Output</b></span>
 
+  ```bash
   NAME                            TYPE        CLUSTER-IP      EXTERNAL-IP PORT(S)                       AGE
   litmusportal-frontend-service   NodePort    10.100.105.154  <none>      9091:30229/TCP                7m14s
   litmusportal-server-service     NodePort    10.100.150.175  <none>      9002:30479/TCP,9003:31949/TCP 7m8s