diff --git a/bun.lockb b/bun.lockb
index 5a86f695..57ba6596 100755
Binary files a/bun.lockb and b/bun.lockb differ
diff --git a/content/00.build/70.api-reference/35.ethereum-rpc.md b/content/00.build/70.api-reference/35.ethereum-rpc.md
index ee2879de..94528d70 100644
--- a/content/00.build/70.api-reference/35.ethereum-rpc.md
+++ b/content/00.build/70.api-reference/35.ethereum-rpc.md
@@ -3,9 +3,19 @@ title: Ethereum JSON-RPC API
 description: JSON-RPC API methods for the eth_ namespace for zkSync Era.
 ---
 
-ZKsync Era supports the standard [Ethereum JSON-RPC API](https://ethereum.org/en/developers/docs/apis/json-rpc/). With the
-exception of `eth_sendTransaction` which is intentionally not
-supported.
+ZKsync Era supports the standard [Ethereum JSON-RPC API](https://ethereum.org/en/developers/docs/apis/json-rpc/).
+
+## Important Differences for Developers
+
+When working with zkSync, there are specific differences you should be aware of:
+
+1. **Block Data Retrieval Methods**:
+   - Methods that return data about a block, such as `eth_getBlockByHash`, `eth_getBlockByNumber`, and Geth’s pubsub
+  API `eth_subscribe` with the `newHeads` parameter, do not provide the actual `receiptsRoot`, `transactionsRoot`, and `stateRoot` values.
+   - Instead, these fields contain zero values because zkSync’s L2 blocks do not include the concept of a state root; only L1 batches have this concept.
+
+2. **Unsupported Method**:
+   - The method `eth_sendTransaction` is intentionally not supported in zkSync.
 
 ## `eth_chainId`
 
diff --git a/package.json b/package.json
index 97e623e8..64d03969 100644
--- a/package.json
+++ b/package.json
@@ -8,6 +8,7 @@
   "homepage": "https://zksync.io",
   "devDependencies": {
     "@nuxt/devtools": "^1.1.5",
+    "@nuxtjs/seo": "^2.0.0-rc.10",
     "@types/bun": "^1.0.8",
     "@vue/test-utils": "^2.4.5",
     "cspell": "^8.6.0",