From eaf6d75be3dd6af8807bc32383c5a8d25172fe90 Mon Sep 17 00:00:00 2001
From: Daimakaimura <17453177+Daimakaimura@users.noreply.github.com>
Date: Thu, 2 Nov 2023 09:48:44 +0000
Subject: [PATCH] Line 70 edit

---
 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..435cae96 100644
--- a/rlog/2023-09-26-wakurtosis-retro.mdx
+++ b/rlog/2023-09-26-wakurtosis-retro.mdx
@@ -66,7 +66,7 @@ As the number of containers (nodes) increased, the simultaneous read/write opera
 
 ##### ARP table exhaustion
 Another important issue we encounteres is the exhaustion of the ARP table. 
-The Address Resolution Protocol (ARP) is pivotal for routing, translating IP addresses to MAC addresses so data packets can be correctly delivered within a local network. 
+The Address Resolution Protocol (ARP) is pivotal for delivering Ethernet frames, translating IP addresses to MAC addresses so data packets can be correctly delivered within a local network. 
 However, ARP tables have a size limit. With the vast number of containers running, we quickly ran into situations where the ARP tables were filled to capacity, leading to routing failures.