diff --git a/docs/validator/fullnode.md b/docs/validator/fullnode.md
index 67c058fbf3..a0f79362bc 100644
--- a/docs/validator/fullnode.md
+++ b/docs/validator/fullnode.md
@@ -17,7 +17,7 @@ We support running a full node on **Mac OS X**, **Linux**, and **Windows**.
 
 ## Suggested Requirements
 - VPS running recent versions of Mac OS X, Linux, or Windows.
-- **IMPORTANT** 2 TB of free disk space, solid-state drive(SSD), gp3, 8k IOPS, 250 MB/S throughput, read latency <1ms. (if node is started with snap sync, it will need NVMe SSD)
+- **IMPORTANT** 3 TB of free disk space, solid-state drive(SSD), gp3, 8k IOPS, 250 MB/S throughput, read latency <1ms. (if node is started with snap sync, it will need NVMe SSD)
 - 16 cores of CPU and 64 GB of memory (RAM)
 - Suggest m5zn.3xlarge instance type on AWS, c2-standard-16 on Google cloud.
 - A broadband Internet connection with upload/download speeds of 5 MB/S
diff --git a/docs/validator/node-maintenance.md b/docs/validator/node-maintenance.md
index 4a3fe4c5dd..d79108e71c 100644
--- a/docs/validator/node-maintenance.md
+++ b/docs/validator/node-maintenance.md
@@ -11,7 +11,7 @@ All the clients are suggested to upgrade to the latest release. The [latest vers
 
 #### Prune State
 
-According to the test, the performance of a full node will degrade when the storage size exceeds 1.5 TB. We suggest that the fullnode always keep light storage by pruning the storage. 
+According to the test, the performance of a full node will degrade when the storage size reaches a high volume(previously it was 1.5TB, which is an experimental value, the latest number needs to be updated). We suggest that the fullnode always keep light storage by pruning the storage.
 
 How to prune:
 
diff --git a/docs/validator/run-val.md b/docs/validator/run-val.md
index 71581a7117..780d5e742c 100644
--- a/docs/validator/run-val.md
+++ b/docs/validator/run-val.md
@@ -9,7 +9,7 @@ hide_table_of_contents: false
 
 ### 1. Mainnet
 - VPS running recent versions of Mac OS X or Linux.
-- **IMPORTANT** 2T GB of free disk space, solid-state drive(SSD), gp3, 8k IOPS, 250MB/S throughput, read latency <1ms (if start with snap/fast sync, it will need NVMe SSD)
+- **IMPORTANT** 3T GB of free disk space, solid-state drive(SSD), gp3, 8k IOPS, 250MB/S throughput, read latency <1ms (if start with snap sync, it will need NVMe SSD)
 - 16 cores of CPU and 64 gigabytes of memory (RAM)
 - Suggest m5zn.3xlarge instance type on AWS, or c2-standard-16 on Google cloud.
 - A broadband Internet connection with upload/download speeds of 10 megabyte per second
@@ -17,7 +17,7 @@ hide_table_of_contents: false
 ### 2. Testnet
 - CPU: 4core, Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
 - Memory: 16 GB
-- Disk: ~1.85 TB
+- Disk: ~1.5 TB
 - Network Bandwidth: Upto 25 Gbps
 - EBS Bandwidth: Upto 9.5 Gbps