diff --git a/docs/base-chain/node-operators/performance-tuning.mdx b/docs/base-chain/node-operators/performance-tuning.mdx
index f1f519c14..4d98d1e00 100644
--- a/docs/base-chain/node-operators/performance-tuning.mdx
+++ b/docs/base-chain/node-operators/performance-tuning.mdx
@@ -9,8 +9,8 @@ This guide provides recommendations for hardware, client software, and configura
 
 Running a performant Base node requires adequate hardware. We recommend the following minimum specifications:
 
-1. A modern multi-core CPU with good single-core performance.  
-2. At least 32 GB RAM (64 GB recommended).  
+1. A modern multi-core (8+) CPU with good single-core performance.  
+2. At least 32 GB RAM (64 GB recommended). 
 3. A locally attached NVMe SSD drive. RAID 0 configurations can improve performance.  
 4. Sufficient storage capacity calculated as:
 
diff --git a/docs/base-chain/node-operators/run-a-base-node.mdx b/docs/base-chain/node-operators/run-a-base-node.mdx
index 8c79ebd00..075134131 100644
--- a/docs/base-chain/node-operators/run-a-base-node.mdx
+++ b/docs/base-chain/node-operators/run-a-base-node.mdx
@@ -29,19 +29,7 @@ If you're looking to harden your app and avoid rate-limiting for your users, ple
 
 ### Hardware requirements
 
-We recommend you have this configuration to run a node:
-
-- 8-Core CPU
-- at least 16 GB RAM
-- a locally attached NVMe SSD drive
-- Adequate storage capacity:
-  - Minimum: `(2 × chain_size) + snapshot_size + 20% buffer`
-  - Accounts for snapshot restoration (if applicable) and chain data
-
-<Note>
-If utilizing Amazon Elastic Block Store (EBS), ensure timing buffered disk reads are fast enough in order to avoid latency issues alongside the rate of new blocks added to Base during the initial synchronization process; `io2 block express` is recommended.
-</Note>
-
+See the [Node Performance guide](/base-chain/node-operators/performance-tuning#hardware) for full hardware specifications, storage requirements, and production hardware examples.
 
 ### Networking