From 3cb15806bebadc721ec61fd43cd1786a5cb18d35 Mon Sep 17 00:00:00 2001 From: Alex Stokes Date: Fri, 11 Sep 2020 17:08:37 -0700 Subject: [PATCH] Update p2p-interface.md Typo fixes --- specs/phase0/p2p-interface.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/specs/phase0/p2p-interface.md b/specs/phase0/p2p-interface.md index 1ecbc4ec9..b337be67e 100644 --- a/specs/phase0/p2p-interface.md +++ b/specs/phase0/p2p-interface.md @@ -725,7 +725,7 @@ A request MUST NOT have a 0 slot increment, i.e. `step >= 1`. `BeaconBlocksByRange` is primarily used to sync historical blocks. -The request MUST be encoded as an SSZ-container. +The request MUST be encoded as a SSZ-container. The response MUST consist of zero or more `response_chunk`. Each _successful_ `response_chunk` MUST contain a single `SignedBeaconBlock` payload. @@ -735,7 +735,7 @@ and MUST support serving requests of blocks up to their own `head_block_root`. Clients MUST respond with at least the first block that exists in the range, if they have it, and no more than `MAX_REQUEST_BLOCKS` blocks. -The following blocks, where they exist, MUST be send in consecutive order. +The following blocks, where they exist, MUST be sent in consecutive order. Clients MAY limit the number of blocks in the response.