chore: fix readme

README.md

@@ -17,11 +17,15 @@ This crate provides an in-memory node that supports forking the state from other
 
 The goal of this crate is to offer a fast solution for integration testing, bootloader and system contract testing, and prototyping.
 
-🔗 For a detailed walkthrough, refer to the [official documentation](https://docs.zksync.io/build/test-and-debug/in-memory-node).
+🔗 **For a detailed walkthrough, refer to the following resources:**
+
+- [Official documentation: Anvil-ZKsync](https://docs.zksync.io/build/test-and-debug/in-memory-node)
+- [Foundry Book: Anvil for zkSync](https://foundry-book.zksync.io/reference/anvil-zksync/)
+- [Rust Book: Anvil-ZKsync](https://matter-labs.github.io/era-test-node/era_test_node/index.html)
 
 ## 📌 Overview
 
-The In-Memory Node is designed for local testing and uses an in-memory database for storing state information. It also employs simplified hashmaps for tracking blocks and transactions. When in fork mode, it fetches missing storage data from a remote source if not available locally. Additionally, it uses the remote server (openchain) to resolve the ABI and topics to human-readable names.
+`anvil-zksync` is designed for local testing and uses an in-memory database for storing state information. It also employs simplified hashmaps for tracking blocks and transactions. When in fork mode, it fetches missing storage data from a remote source if not available locally. Additionally, it uses the remote server (openchain) to resolve the ABI and topics to human-readable names.
 
 ## ⚠️ Caution