diff --git a/.vitepress/constants/mocha_versions.js b/.vitepress/constants/mocha_versions.js
index 559872b5a42..a0edc9eef7f 100644
--- a/.vitepress/constants/mocha_versions.js
+++ b/.vitepress/constants/mocha_versions.js
@@ -1,9 +1,9 @@
 const mochaVersions = Object.freeze({
-  "app-latest-tag": "v2.1.2",
-  "app-latest-sha": "48173df3dc78f9348eedb3796f29ef9e9e5dc584",
+  "app-latest-tag": "v2.2.0-mocha",
+  "app-latest-sha": "d3f8b2997fcbc8e7f43785a9513b2d0c91675087",
   "core-latest-tag": "v1.40.1-tm-v0.34.29-rc0",
   "core-latest-sha": "0d2b63836d0f4587e162bfded58f53fba238e69c",
-  "node-latest-tag": "v0.16.0",
-  "node-latest-sha": "6744f648649ebb5fee1b27faf7aca96ecf4519b2",
+  "node-latest-tag": "v0.18.2-mocha",
+  "node-latest-sha": "4309c8349857638b033a2a278da0f8ab182fdb26",
 });
 export default mochaVersions;
diff --git a/how-to-guides/arbitrum-deploy.md b/how-to-guides/arbitrum-deploy.md
index 9e851a0853d..2978940ed25 100644
--- a/how-to-guides/arbitrum-deploy.md
+++ b/how-to-guides/arbitrum-deploy.md
@@ -123,7 +123,7 @@ deploy your Orbit chain.
 
 After configuring your batch poster, proceed to the next step.
 
-### Step 3: Review & Deploy your Orbit chain
+### Step 4: Review & Deploy your Orbit chain
 
 Now, deploy your chain's base contracts to Arbitrum Sepolia!
 
@@ -154,7 +154,7 @@ the challenge mechanism, bridging mechanisms, and more.
 Once your transaction is complete, continue to Step 4 to
 download your chain's configuration files and launch your chain.
 
-### Step 4: Download your chain's configuration files and launch your chain
+### Step 5: Download your chain's configuration files and launch your chain
 
 After configuring your chain, you will need to download the necessary configuration files to launch your chain. Click the **Download zip files** button to download both the Rollup Config and L3 Config in a single ZIP file.
 
@@ -166,7 +166,7 @@ Ensure to securely store these downloaded files as they contain sensitive inform
 
 ![download config](/arbitrum/download-config.png)
 
-### Step 5: Clone the setup script repository and add your configuration files
+### Step 6: Clone the setup script repository and add your configuration files
 
 1. Clone the [orbit-setup-script](https://github.com/celestiaorg/orbit-setup-script/tree/main)
 repository:
@@ -181,7 +181,7 @@ root of your cloned `orbit-setup-script` repository.
 
 3. Install dependencies by running `yarn install` from the root of the `orbit-setup-script` repository.
 
-### Step 6: Pick an L2 RPC URL for the Batch Poster
+### Step 7: Pick an L2 RPC URL for the Batch Poster
 
 In order for the Batch Poster, which is responsible for posting batches of data, to
 subscribe to Blobstream's smart contract events, the node most use a WebSocket
@@ -210,7 +210,7 @@ and successfully subscribe to Blobstream events.
 Without a WSS connection, the Batch Poster won't be able to subscribe to Blobstream
 events, and thus will fall back to posting data to parent chain.
 
-### Step 7: Run your light node for Mocha testnet
+### Step 8: Run your light node for Mocha testnet
 
 First, be sure that your light node is running, using a command similar to:
 
@@ -297,7 +297,7 @@ This is crucial to protect against potential misuse by copy-paste errors.
 
 [See the compatibility matrix in the appendix to verify you're using the right versions.](#compatibility-matrix)
 
-### Step 8: Run your chain's node and block explorer
+### Step 9: Run your chain's node and block explorer
 
 Start Docker, then run `docker-compose up -d` from the root of
 the `orbit-setup-script` repository.
@@ -313,7 +313,7 @@ After you have some activity on your rollup, it will look more like this:
 
 ![explorer-view](/arbitrum/explorer-view.png)
 
-### Step 9: Finish setting up your chain
+### Step 10: Finish setting up your chain
 
 The Offchain Labs team has provided a Hardhat script that
 handles the following tasks:
diff --git a/how-to-guides/bridge-node.md b/how-to-guides/bridge-node.md
index 2c7dfa354b2..06891fe147e 100644
--- a/how-to-guides/bridge-node.md
+++ b/how-to-guides/bridge-node.md
@@ -49,7 +49,7 @@ bridge node:
 
 - Memory: **16 GB RAM (minimum)**
 - CPU: **6 cores**
-- Disk: **10 TB SSD Storage**
+- Disk: **2 TB NVME Storage**
 - Bandwidth: **1 Gbps for Download/1 Gbps for Upload**
 
 ## Setting up your bridge node
diff --git a/how-to-guides/full-storage-node.md b/how-to-guides/full-storage-node.md
index 46f222eb9d4..261b7d3e529 100644
--- a/how-to-guides/full-storage-node.md
+++ b/how-to-guides/full-storage-node.md
@@ -24,7 +24,7 @@ the full storage node:
 
 - Memory: **16 GB RAM (minimum)**
 - CPU: **6 cores**
-- Disk: **10 TB SSD Storage**
+- Disk: **2 TB NVME Storage**
 - Bandwidth: **1 Gbps for Download/1 Gbps for Upload**
 
 ## Setting up your full storage node
diff --git a/how-to-guides/nodes-overview.md b/how-to-guides/nodes-overview.md
index 2d91193d6e1..8b7517c95f1 100644
--- a/how-to-guides/nodes-overview.md
+++ b/how-to-guides/nodes-overview.md
@@ -36,8 +36,8 @@ each tutorial guide.
 | Node type         | Memory      | CPU         | Disk       | Bandwidth |
 |-------------------|-------------|-------------|------------|-----------|
 | Light node        | 500 MB RAM  | Single core | 100 GB SSD | 56 Kbps   |
-| Bridge node       | 16 GB RAM   | 6 cores     | 10 TB SSD  | 1 Gbps    |
-| Full storage node | 16 GB RAM   | Quad-core   | 10 TB SSD  | 1 Gbps    |
+| Bridge node       | 16 GB RAM   | 6 cores     | 2 TB NVME  | 1 Gbps    |
+| Full storage node | 16 GB RAM   | Quad-core   | 2 TB NVME  | 1 Gbps    |
 
 ## Consensus nodes