diff --git a/website/versioned_docs/version-3.16.0/introduction/usage.md b/website/versioned_docs/version-3.16.0/introduction/usage.md
index 96117562..9716e17f 100644
--- a/website/versioned_docs/version-3.16.0/introduction/usage.md
+++ b/website/versioned_docs/version-3.16.0/introduction/usage.md
@@ -12,7 +12,7 @@ Chaos experiments can be done anywhere in the DevOps cycle. The extent of chaos
 
 ## Common Use Cases
 
-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.
+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.
 
 - **For Developers:** To run chaos experiments during application development as an extension of unit testing or integration testing.
 - **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.