From ea85aa72beac8f853732bfb340c386e721c27102 Mon Sep 17 00:00:00 2001
From: fradamt <104826920+fradamt@users.noreply.github.com>
Date: Thu, 8 Feb 2024 13:16:49 +0100
Subject: [PATCH] fix typo

---
 specs/bellatrix/p2p-interface.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/specs/bellatrix/p2p-interface.md b/specs/bellatrix/p2p-interface.md
index e33d0ca510..617f6f1fc7 100644
--- a/specs/bellatrix/p2p-interface.md
+++ b/specs/bellatrix/p2p-interface.md
@@ -168,7 +168,7 @@ Similar to the discussion about the maximum gossip size increase, the
 `ExecutionPayload` type can cause `BeaconBlock`s to exceed the 1 MiB bounds put
 in place during Phase 0.
 
-As with the gossip limit, 10 MiB is selected because this is firmly below any
+As with the gossip limit, 10 MiB is selected because this is firmly above any
 valid block sizes in the range of gas limits expected in the medium term.
 
 As with both gossip and req/rsp maximum values, type-specific limits should