infrastructure.md

Signed-off-by: andoriyaprashant <[email protected]>

Author: andoriyaprashant

website/docs/concepts/infrastructure.md

@@ -14,15 +14,7 @@ With the latest release of LitmusChaos 3.0.0 the term **Chaos Delegate/Agent** h
 
 An environment represents where you are installing your chaos infrastructure and acts as an additional level of abstraction for the same. You categorize each environment as prod or non-prod.
 
-## Types of Chaos Infrastructures
-
-In Litmus, chaos infrastructures can be classified into two types:
-
-- **Self Chaos Infrastructures:** A Chaos Infrastructure that is connected to the same cluster and namespace where the ChaosCenter is deployed. It can be used to target the workloads executing on that cluster only.
-
-- **External Chaos Infrastructures:** A Chaos Infrastructure that is connected to a remote Kubernetes cluster. ChaosCenter can be operated in a cross-cloud manner, which allows connecting multiple External Chaos Infrastructure 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.
-
-### Access types
+## Access types
 
 Chaos infrastructure can be created in two modes:
 

website/versioned_docs/version-3.12.0/concepts/infrastructure.md

@@ -14,15 +14,7 @@ With the latest release of LitmusChaos 3.0.0 the term **Chaos Delegate/Agent** h
 
 An environment represents where you are installing your chaos infrastructure and acts as an additional level of abstraction for the same. You categorize each environment as prod or non-prod.
 
-## Types of Chaos Infrastructures
-
-In Litmus, chaos infrastructures can be classified into two types:
-
-- **Self Chaos Infrastructures:** A Chaos Infrastructure that is connected to the same cluster and namespace where the ChaosCenter is deployed. It can be used to target the workloads executing on that cluster only.
-
-- **External Chaos Infrastructures:** A Chaos Infrastructure that is connected to a remote Kubernetes cluster. ChaosCenter can be operated in a cross-cloud manner, which allows connecting multiple External Chaos Infrastructure 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.
-
-### Access types
+## Access types
 
 Chaos infrastructure can be created in two modes: