From 4e1e0463f77b9baca056fbe55824409b30235b16 Mon Sep 17 00:00:00 2001 From: Armin Sabouri Date: Wed, 15 Nov 2023 09:32:58 -0500 Subject: [PATCH] docs: fix spelling mistakes in eth-wire.md (#5438) Co-authored-by: DaniPopes <57450786+DaniPopes@users.noreply.github.com> --- docs/crates/eth-wire.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/crates/eth-wire.md b/docs/crates/eth-wire.md index dfc85e37d..41bc065f9 100644 --- a/docs/crates/eth-wire.md +++ b/docs/crates/eth-wire.md @@ -5,10 +5,10 @@ The `eth-wire` crate provides abstractions over the [RLPx](https://github.com/et This crate can be thought of as having 2 components: -1. Data structures which serialize and deserialize the eth protcol messages into Rust compatible types. -2. Abstractions over Tokio Streams which operate on these types. +1. Data structures that serialize and deserialize the Ethereum protocol messages into Rust-compatible types. +2. Abstractions over Tokio Streams that operate on these types. -(Note that ECIES is implemented in a seperate `reth-ecies` crate.) +(Note that ECIES is implemented in a separate `reth-ecies` crate.) ## Types The most basic Eth-wire type is an `ProtocolMessage`. It describes all messages that reth can send/receive. @@ -59,7 +59,7 @@ pub struct RequestPair { } ``` -Every `Ethmessage` has a correspoding rust struct which implements the `Encodable` and `Decodable` traits. +Every `Ethmessage` has a corresponding rust struct that implements the `Encodable` and `Decodable` traits. These traits are defined as follows: [Crate: crates/rlp](https://github.com/paradigmxyz/reth/tree/1563506aea09049a85e5cc72c2894f3f7a371581/crates/rlp)