fix: several typos in the docs #367
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
mapachurro
reviewed
Dec 13, 2023
| @@ -45,7 +45,7 @@ The transaction's block will then be subject to [conflation](./sequencer/conflat | |||
|
|
|||
| Occasionally, a batch may only consist of one block, with no conflation having taken place. This occurs when chain activity levels are particularly high, and the block size is larger than normal. | |||
|
|
|||
| Amongst Ethereum's L2 networks, Linea is the only network that uses batch conflation. | |||
| Among Ethereum's L2 networks, Linea is the only network that uses batch conflation. | |||
There was a problem hiding this comment.
This does not need to be changed. This is dialectical preference, and we do not enforce American English, British English, or any other as a rule.
mapachurro
reviewed
Dec 13, 2023
| @@ -68,7 +68,7 @@ Let's break down the two elements submitted to L1: | |||
| - The proof, as explained [above](#step-5-generating-a-zk-proof-using-transaction-data), and; | |||
| - `calldata`, the object in which L2 transaction data is stored. The public availability of `calldata` means that anyone can use it to reconstruct Linea's state. You can then compare this reconstruction to the contents of the proof, and verify the latter. This is what happens when the Linea rollup contract on L1 calls the Ethereum verifier contract using `calldata`, determining whether or not to accept the batch as valid. | |||
|
|
|||
| You can view `calldata` in completed batches on L1 by heading to the [Linea L1 rollup contract](https://etherscan.io/address/0xd19d4b5d358258f05d7b411e21a1460d11b0876f) and finding a transaction whose method is labelled as "Finalize Blocks". Once there, scroll and expand the "More details" section, and then decode the input data. | |||
| You can view `calldata` in completed batches on L1 by heading to the [Linea L1 rollup contract](https://etherscan.io/address/0xd19d4b5d358258f05d7b411e21a1460d11b0876f) and finding a transaction whose method is labeled as "Finalize Blocks". Once there, scroll and expand the "More details" section, and then decode the input data. | |||
There was a problem hiding this comment.
Again, dialectical preference -- do not change.
|
@tudorpintea999 hey, could you address @mapachurro's review and fix the conflicts please? thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello
I fixed some typos in the docs,
Hope it helps.
Br,
Tudor.