doc: feedbacks

Author: leruaa

book/docs/custom-chains.md

@@ -0,0 +1,19 @@
+---
+title: Custom chains
+sidebar_position: 8
+---
+
+If you want to run SP1 Contract Call on a custom EVM chain, you can use the [`with_genesis()`] function while [building the `EvmSketch`](https://succinctlabs.github.io/sp1-contract-call/api/sp1_cc_host_executor/struct.EvmSketch.html#method.builder). The [`Genesis`] enum allows to specify a custom chain by using its genesis JSON.
+
+:::tip
+
+You can find examples of genesis JSON [here](https://github.com/succinctlabs/rsp/tree/main/bin/host/genesis).
+
+:::
+
+
+
+
+
+[`with_genesis()`]: pathname:///api/sp1_cc_host_executor/struct.EvmSketchBuilder.html#method.with_genesis
+[`Genesis`]: pathname:///api/sp1_cc_host_executor/enum.Genesis.html

book/docs/events.md

@@ -23,7 +23,7 @@ sol! {
 }
 ```
 
-You'll nee to interact with the module generated by the `sol!` macro in both the host and the client, so it's a good practice to have the code above in a shared lib accessible in both environments.
+You'll need to interact with the module generated by the `sol!` macro in both the host and the client, so it's a good practice to have the code above in a shared lib accessible in both environments.
 
 ### Host-Side Event Processing
 

book/docs/examples.md

@@ -1,6 +1,6 @@
 ---
 title: Examples
-sidebar_position: 7
+sidebar_position: 8
 ---
 
 ## Uniswap (basic)

book/docs/proof-verification.md

@@ -35,7 +35,7 @@ let sketch = EvmSketch::builder()
 
 ### Chaining
 
-The EIP-4788 anchor mechanism can be used to query view call state from blocks beyond the 8191 block limit by separating the anchor into two components: an execution block and a reference block. While the reference block acts as the anchor and must remain within the ~27 hour onchain validation timeframe, the execution block can extend significantly further into the past—covering periods of days, weeks, or even months.
+The EIP-4788 anchor mechanism can be used to query view call state from blocks beyond the 8191 block limit by separating the anchor into two components: an execution block and a reference block. While the reference block acts as the anchor and must remain within the ~27 hour onchain validation timeframe, the execution block can extend significantly further into the past—up to the Cancun hardfork (March 13, 2024 on Mainnet).
 
 These two blocks have an inherent relationship: the execution block must always be an ancestor of the reference block. By validating a chain of beacon block roots between these two blocks, you can prove that the execution block exists within the committed chain.