This pull request includes several updates to the ZK-EVM specifications documentation. The main change is in bytecode-proof.md, where the definition of push_data_left has been made clearer. Previously, the description read, "The number of left bytes data needs to be PUSHed," which was somewhat incomprehensible. Other minor grammar and clarity fixes are included in different parts of the documentation.
Commits:
4302df1: Updated the description of push_data_left for better clarity.
1225a85: Fixed a spelling error in opcode/5AGAS.md.
60d3c05: Improved grammar in copy-proof.md.
5754ad8: Corrected grammar in evm-proof.md.
Request for Review:
I've updated the definition of push_data_left to make it easier to understand as I found hard to interpret. It'd be great if you could check this part to ensure it aligns well with the technical aspects of the ZK-EVM.
Description:
This pull request includes several updates to the ZK-EVM specifications documentation. The main change is in
bytecode-proof.md, where the definition ofpush_data_lefthas been made clearer. Previously, the description read, "The number of left bytes data needs to be PUSHed," which was somewhat incomprehensible. Other minor grammar and clarity fixes are included in different parts of the documentation.Commits:
push_data_leftfor better clarity.opcode/5AGAS.md.copy-proof.md.evm-proof.md.Request for Review:
I've updated the definition of
push_data_leftto make it easier to understand as I found hard to interpret. It'd be great if you could check this part to ensure it aligns well with the technical aspects of the ZK-EVM.