From 5d216e84d20e821009e1258a4f4daeb6213ef11d Mon Sep 17 00:00:00 2001 From: shak58 <150069539+shak58@users.noreply.github.com> Date: Tue, 7 Nov 2023 11:25:51 +0000 Subject: [PATCH 1/2] fix typo in documentation by changing 'splitted' to 'split' --- packages/website/pages/docs/concepts/taiko-nodes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/website/pages/docs/concepts/taiko-nodes.mdx b/packages/website/pages/docs/concepts/taiko-nodes.mdx index a965eefdfdb..a3b44d8d935 100644 --- a/packages/website/pages/docs/concepts/taiko-nodes.mdx +++ b/packages/website/pages/docs/concepts/taiko-nodes.mdx @@ -83,7 +83,7 @@ To propose a block, the `proposer`: 1. Fetches the pending transactions from the L2 execution engine through the `txpool_content` RPC method. 2. If there are too many pending transactions in the L2 execution engine, splits them into several smaller `txLists`. This is because the Taiko protocol restricts the max size of each proposed `txList`. -3. Proposes all splitted `txLists` by sending `TaikoL1.proposeBlock` transactions. +3. Proposes all split `txLists` by sending `TaikoL1.proposeBlock` transactions. ## Process of proving a block From 7640ce9212970ecf2fa629e4c3f80d221159b514 Mon Sep 17 00:00:00 2001 From: shak58 <150069539+shak58@users.noreply.github.com> Date: Tue, 7 Nov 2023 11:27:20 +0000 Subject: [PATCH 2/2] fixed typo in documentation related to RLP decoding process --- packages/website/pages/docs/concepts/proposing.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/website/pages/docs/concepts/proposing.mdx b/packages/website/pages/docs/concepts/proposing.mdx index c798df602a7..8f6f28033f5 100644 --- a/packages/website/pages/docs/concepts/proposing.mdx +++ b/packages/website/pages/docs/concepts/proposing.mdx @@ -18,7 +18,7 @@ The Ethereum yellow paper has well-defined rules to compute the state transition 2.1 Asserts that the length of the transaction list does not exceed a predefined maximum (MAX_TX_LIST_BYTES), ensuring that the list is within the limits. - 2.2 The transaction list is (RLP) decoded into a list of transactions (txList). If the bytes are not decodeable it will result in an empty block. + 2.2 The transaction list is (RLP) decoded into a list of transactions (txList). If the bytes are not decodable it will result in an empty block. 2.3 The amount of gas required to include transactions is available. (If a transaction cannot fit into a block, it is simply excluded from it, but the block is still valid with other transactions.)