Skip to content

Commit 1d04349

Browse files
authored
Refactor headings in installation.md for clarity
Updated headings for consistency in installation documentation.
1 parent b813100 commit 1d04349

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

website/docs/getting-started/installation.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -114,11 +114,11 @@ Visit https://docs.litmuschaos.io to find more info.
114114

115115
> **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.
116116
117-
## **Install Litmus using kubectl**
117+
## Install Litmus using kubectl
118118

119119
In this method the users need to install mongo first via helm and then apply the installation manifest. Follow the instructions [here](https://github.com/litmuschaos/litmus/tree/master/chaoscenter#installation-steps-for-litmus-300-beta9).
120120

121-
### **Install mongo**
121+
### Install mongo
122122

123123
```bash
124124
helm repo add bitnami https://charts.bitnami.com/bitnami
@@ -172,9 +172,9 @@ For advanced installation visit [here](../user-guides/chaoscenter-advanced-insta
172172

173173
---
174174

175-
## **Verify your installation**
175+
## Verify your installation
176176

177-
#### **Verify if the frontend, server, and database pods are running**
177+
#### Verify if the frontend, server, and database pods are running
178178

179179
- Check the pods in the namespace where you installed Litmus:
180180

@@ -217,7 +217,7 @@ For advanced installation visit [here](../user-guides/chaoscenter-advanced-insta
217217

218218
---
219219

220-
## **Accessing the ChaosCenter**
220+
## Accessing the ChaosCenter
221221

222222
To setup and login to ChaosCenter expand the available services just created and copy the `PORT` of the `litmusportal-frontend-service` service
223223

0 commit comments

Comments
 (0)