diff --git a/specs/phase0/p2p-interface.md b/specs/phase0/p2p-interface.md
index 69f6559bd..34b0375e0 100644
--- a/specs/phase0/p2p-interface.md
+++ b/specs/phase0/p2p-interface.md
@@ -727,7 +727,7 @@ Request Content:
 (
   start_slot: Slot
   count: uint64
-  step: uint64
+  step: uint64 # Deprecated, must be set to 1
 )
 ```
 
@@ -738,12 +738,12 @@ Response Content:
 )
 ```
 
-Requests beacon blocks in the slot range `[start_slot, start_slot + count * step)`, leading up to the current head block as selected by fork choice.
-`step` defines the slot increment between blocks.
-For example, requesting blocks starting at `start_slot` 2 with a step value of 2 would return the blocks at slots [2, 4, 6, …].
+Requests beacon blocks in the slot range `[start_slot, start_slot + count)`, leading up to the current head block as selected by fork choice.
+For example, requesting blocks starting at `start_slot=2` and `count=4` would return the blocks at slots `[2, 3, 4, 5]`.
 In cases where a slot is empty for a given slot number, no block is returned.
-For example, if slot 4 were empty in the previous example, the returned array would contain [2, 6, …].
-A request MUST NOT have a 0 slot increment, i.e. `step >= 1`.
+For example, if slot 4 were empty in the previous example, the returned array would contain `[2, 3, 5]`.
+
+`step` is deprecated and must be set to 1. Clients may respond with a single block if a larger step is returned during the deprecation transition period.
 
 `BeaconBlocksByRange` is primarily used to sync historical blocks.