diff --git a/EIPS/eip-3675.md b/EIPS/eip-3675.md
index c3869d0c1a..ccd1f8d97a 100644
--- a/EIPS/eip-3675.md
+++ b/EIPS/eip-3675.md
@@ -223,8 +223,6 @@ The value of `FORK_NEXT` in EIP-2124 refers to the block number of the next fork
 
 The number of `TRANSITION_BLOCK` cannot be known ahead of time given the dynamic nature of the transition trigger condition. As the block will not be known a priori, nodes can't use its number for `FORK_NEXT` and in light of this fact an explicitly set `FORK_NEXT_VALUE` is used instead.
 
-The number set to `FORK_NEXT_VALUE` parameter should reference a block which is presumably happening a week earlier than `TRANSITION_BLOCK`. Picking the number this way gives enough time for users who forgot to upgrade their software to do so when they see their nodes are losing peers.
-
 ### Removing block gossip
 
 After the upgrade of the consensus mechanism only the beacon chain network will have enough information to validate a block. Thus, block gossip provided by the `eth` network protocol will become unsafe and is deprecated in favour of the block gossip existing in the beacon chain network.