From 22b4bccfe461a712f179495ff3cf56037452b1a4 Mon Sep 17 00:00:00 2001
From: Daimakaimura <17453177+Daimakaimura@users.noreply.github.com>
Date: Thu, 2 Nov 2023 09:53:27 +0000
Subject: [PATCH] Update rlog/2023-09-26-wakurtosis-retro.mdx

Co-authored-by: kaiserd <1684595+kaiserd@users.noreply.github.com>
---
 rlog/2023-09-26-wakurtosis-retro.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/rlog/2023-09-26-wakurtosis-retro.mdx b/rlog/2023-09-26-wakurtosis-retro.mdx
index dc141f78..ab3633c5 100644
--- a/rlog/2023-09-26-wakurtosis-retro.mdx
+++ b/rlog/2023-09-26-wakurtosis-retro.mdx
@@ -83,7 +83,7 @@ These constraints were exacerbated by limitations in the orchestration language
 The array of hardware and software limitations imposed by Kurtosis had significant ramifications on our testing capabilities. 
 The constraints primarily manifested in the inability to realistically simulate diverse network configurations and conditions. 
 This inflexibility in network topologies was a significant setback. 
-Moreover, when it came to protocol implementation, Kurtosis's approach was rather rudimentary. 
+Moreover, when it came to protocol implementation, Kurtosis' approach was rather rudimentary. 
 Relying on a basic gossip model, the platform missed capturing the nuances that are critical for deriving meaningful insights from the simulations.
 
 ### The Pivot to Kubernetes and Shadow