update

Signed-off-by: Smriti Satya <smriti.satyanarayana@harness.io>
litmuschaos · Feb 18, 2025 · baa3bde · baa3bde
1 parent 84391cd
commit baa3bde
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/website/versioned_docs/version-3.12.0/getting-started/resources.md b/website/versioned_docs/version-3.12.0/getting-started/resources.md
@@ -36,4 +36,4 @@ In Litmus, you can classify chaos infrastructure into two types:
 
 - **Self chaos infrastructure:** A chaos infrastructure that is connected to the same cluster and namespace where the ChaosCenter is deployed. You can use this to target the workloads executing on that cluster only.
 
-- **External chaos infrastructure:** A chaos infrastructure connected to a remote Kubernetes cluster. You can operate ChaosCenter in a cross-cloud manner, connecting multiple external chaos infrastructures to the same ChaosCenter with the help of the [litmusctl](../litmusctl/installation.md) CLI. Once connected you can manage, monitor, observe, and induce chaos from the ChaosCenter to the respective external chaos infrastructures.
+- **External chaos infrastructure:** A chaos infrastructure connected to a remote Kubernetes cluster. You can operate ChaosCenter in a cross-cloud manner, connecting multiple external chaos infrastructures to the same ChaosCenter with the help of the [litmusctl](../litmusctl/installation.md) CLI. Once connected you can manage, monitor, observe, and induce chaos from the ChaosCenter to the respective external chaos infrastructures.