From 13675375ef8265a6ecab99d8cddebf5bce2d035e Mon Sep 17 00:00:00 2001
From: Kate Osborn <50597707+kate-osborn@users.noreply.github.com>
Date: Wed, 1 Nov 2023 13:38:03 -0600
Subject: [PATCH] Update tests/zero-downtime-scaling/zero-downtime-scaling.md

Co-authored-by: bjee19 <139261241+bjee19@users.noreply.github.com>
---
 tests/zero-downtime-scaling/zero-downtime-scaling.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/zero-downtime-scaling/zero-downtime-scaling.md b/tests/zero-downtime-scaling/zero-downtime-scaling.md
index 970a5199ee..e816024e25 100644
--- a/tests/zero-downtime-scaling/zero-downtime-scaling.md
+++ b/tests/zero-downtime-scaling/zero-downtime-scaling.md
@@ -78,7 +78,7 @@ The rest of the test environment is the same for both cases:
 Notes:
 
 - For sending traffic, we will use both wrk and curl.
-  - *wrk* will generate a lot of traffic continuously, and it will have a high chance of catching of any
+  - *wrk* will generate a lot of traffic continuously and it will have a high chance of catching any
     (however small) periods of downtime.
   - *curl* will generate 1 request every 0.1s. While it might not catch small periods of downtime, it will give us
     timeline of failed request for big periods of downtime, which wrk doesn't do.