From 1e216723da27ca81d64831f9f12df4f92fe53685 Mon Sep 17 00:00:00 2001 From: kael Date: Sat, 24 Feb 2024 17:23:31 +0800 Subject: [PATCH 1/2] wrong word check --- _config.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_config.yml b/_config.yml index a6d969f35b1d38..5fa119564fa8e1 100644 --- a/_config.yml +++ b/_config.yml @@ -39,7 +39,7 @@ kramdown: parse_block_html: false # This is the default, but be explicit as some EIPs depend on it auto_ids: true - # This is to ensure more determistic behaviour + # This is to ensure more deterministic behaviour auto_id_stripping: true syntax_highlighter: rouge From 4173bfd460ee9ab3329e88bee02d9e79e31e32cb Mon Sep 17 00:00:00 2001 From: kael Date: Sat, 24 Feb 2024 18:07:06 +0800 Subject: [PATCH 2/2] modify eip-7542 wrong words correct --- EIPS/eip-7542.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/EIPS/eip-7542.md b/EIPS/eip-7542.md index 0074c26911fefc..a7f6f92a769f27 100644 --- a/EIPS/eip-7542.md +++ b/EIPS/eip-7542.md @@ -42,8 +42,8 @@ Nodes must retain connections regardless of a peer's available block range, with ## Rationale Including the available block range in the `eth` handshake allows for immediate understanding of peer capabilities. This can lead to more efficient networking as nodes can prioritize connections based on the data they need. -The new message types are introduced to allow nodes to reuqest updated available block range from other nodes since the range can change by the node syncing or pruning blocks. -Maintaining connections with peers that dont have the desired range ensures network resilience, while the exception facilitates efficient block sync under full peer capacity. +The new message types are introduced to allow nodes to request updated available block range from other nodes since the range can change by the node syncing or pruning blocks. +Maintaining connections with peers that don't have the desired range ensures network resilience, while the exception facilitates efficient block sync under full peer capacity. ## Backwards Compatibility @@ -53,7 +53,7 @@ This EIP doesn't affect the consensus engine and doesn't necessitate a hard fork ## Test Cases -Testing will involve ensuring that nodes can correctly communicate and understand the block range information during the handshake. Additionally, it will involve ensuring nodes can correcly request and share updated block range when requested. +Testing will involve ensuring that nodes can correctly communicate and understand the block range information during the handshake. Additionally, it will involve ensuring nodes can correctly request and share updated block range when requested. ## Security Considerations