Rename Chaos Experiments docs

content/en/getting-started/faq.md

@@ -352,5 +352,5 @@ For more details, please take a look at our [Enterprise offering](https://locals
 ### How does the LocalStack Web Application communicate with the LocalStack container?
 
 The LocalStack Web Application connects to your LocalStack container running on your local machine and retrieves the information directly via the `localhost` without using the internet.
-Features such as Resource Browsers, IAM Policy Stream, Chaos Engineering dashboard, and others communicate directly with the LocalStack container using your browser.
+Features such as Resource Browsers, IAM Policy Stream, Chaos Experiments, and others communicate directly with the LocalStack container using your browser.
 None of the information is sent to the internet, or stored on any external servers maintained by LocalStack.

content/en/user-guide/chaos-engineering/_index.md

@@ -10,15 +10,16 @@ cascade:
 
 ## Introduction
 
-Chaos engineering via LocalStack is a method to enhance system resilience by deliberately introducing controlled disruptions.
+Chaos Engineering via LocalStack is a method to enhance system resilience by deliberately introducing controlled disruptions.
 This technique takes different forms depending on the team:
 
 - Software developers focus on application behavior and error response
 - Architects concentrate on the strength of system design
 - Operations teams investigate the dependability of infrastructure setup.
 
 Integrating chaos tests early in the development process helps identify and mitigate potential flaws, leading to systems that are more robust under stress and can withstand turbulent conditions.
-Chaos engineering in LocalStack encompasses the following features:
+
+Chaos Engineering in LocalStack encompasses the following features:
 
 - **Application behavior and error management** through Fault Injection Service (FIS) experiments.
 - **Robust architecture** tested via failover scenarios using the Chaos API.

content/en/user-guide/chaos-engineering/chaos-experiments/index.md

@@ -0,0 +1,32 @@
+---
+title: "Chaos Experiments"
+linkTitle: "Chaos Experiments"
+description: Chaos Experiments allows users to conduct chaos engineering experiments and test system reliability by injecting stress or failure in some part of a system.
+tags: ["Enterprise plan"]
+aliases:
+  - /user-guide/chaos-engineering/web-application-dashboard/
+  - /user-guide/chaos-engineering/chaos-application-dashboard/
+---
+
+## Introduction
+
+[Chaos Experiments](https://app.localstack.cloud/chaos) in LocalStack offer streamlined testing for cloud applications, enabling you to simulate server errors, service outages, regional disruptions, and network latency with ease, ensuring your app is ready for real-world challenges.
+
+{{< callout "note" >}}
+Chaos Experiments is offered as a **preview** feature and under active development.
+{{< /callout >}}
+
+Chaos Experiments use the [LocalStack Chaos API]({{< ref "chaos-api" >}}) under the hood to offer a set of customizable templates that can be seamlessly integrated into any automation workflows.
+
+{{< figure src="chaos-experiments.png" width="900" >}}
+
+## Features
+
+Chaos Experiments offer the following features:
+
+* **DynamoDB Error**: Randomly inject `ProvisionedThroughputExceededException` errors into DynamoDB API responses.
+* **Kinesis Error**: Randomly inject `ProvisionedThroughputExceededException` errors into Kinesis API responses.
+* **500 Internal Error**: Randomly terminate incoming requests, returning an `Internal Server Error` with a response code of 500.
+* **Service Unavailable**: Cause a specified percentage of service API calls to receive a 503 `Service Unavailable` response.
+* **AWS Region Unavailable**: Simulate regional outages and failovers by disabling entire AWS regions.
+* **Latency**: Introduce specified latency to every API call, useful for simulating network latency or degraded network performance.