From 26d5156975e53314d70576c3e18a7d8eafb38223 Mon Sep 17 00:00:00 2001
From: praveen-wedaa <140157936+praveen-wedaa@users.noreply.github.com>
Date: Sat, 26 Jul 2025 10:14:13 +0530
Subject: [PATCH] Update usage.md

Correction to the duplication of "and production" use!
---
 website/versioned_docs/version-3.16.0/introduction/usage.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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.