Skip to content

Commit 3f9bbbb

Browse files
Update usage.md (#332)
Correction to the duplication of "and production" use!
1 parent b9788fd commit 3f9bbbb

File tree

1 file changed

+1
-1
lines changed
  • website/versioned_docs/version-3.16.0/introduction

1 file changed

+1
-1
lines changed

website/versioned_docs/version-3.16.0/introduction/usage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Chaos experiments can be done anywhere in the DevOps cycle. The extent of chaos
1212

1313
## Common Use Cases
1414

15-
Typical use cases of Litmus include – failure or chaos testing in CI pipelines, increased chaos testing in staging and production and production environments, Kubernetes upgrades certification, post-upgrade validation of services, and resilience benchmarking, etc.
15+
Typical use cases of Litmus include – failure or chaos testing in CI pipelines, increased chaos testing in staging and production environments, Kubernetes upgrades certification, post-upgrade validation of services, and resilience benchmarking, etc.
1616

1717
- **For Developers:** To run chaos experiments during application development as an extension of unit testing or integration testing.
1818
- **For CI pipeline builders:** To run chaos as a pipeline stage to find bugs when the application is subjected to fail paths in a pipeline.

0 commit comments

Comments
 (0)