resolve TODOs

Author: eshaben

node-infrastructure/run-a-collator.md

@@ -23,7 +23,6 @@ Block-producing collators require robust hardware for reliable operation, includ
 - **CPU**: 4+ cores (8+ cores recommended for optimal performance)
 - **Memory**: 32 GB RAM minimum (64 GB recommended)
 - **Storage**:
-    <!-- TODO-ERIN: knowing the issues with the other pages, this needs to be double-checked. 200 GB doesn't seem correct. 👇 -->
     - 200+ GB NVMe SSD (with pruning enabled for both parachain and relay chain)
     - Fast disk I/O is critical for block production performance
 - **Network**:
@@ -442,7 +441,7 @@ The registration process varies by system parachain. General steps include the f
 
     ![](/images/node-infrastructure/run-a-collator/run-a-collator-03.webp)
 
-5. For system parachains using invulnerables lists, await governance approval for your proposal. Monitor the [Polkadot Forum](https://forum.polkadot.network){target=\_blank} governance channels and announcements. Once approved, your collator is added to the invulnerables list and will begin producing blocks in the next session or era. 
+5. For system parachains using invulnerables lists, await governance approval for your proposal. Once approved, your collator is added to the invulnerables list and will begin producing blocks in the next session or era. 
 
 6. Verify your collator is active by monitoring logs for block production messages like "Prepared block for proposing" and "Imported #123". See the [Log Management](#commands-for-log-management) section for commands for log viewing.
 

node-infrastructure/run-a-node/parachain-rpc.md

@@ -22,14 +22,13 @@ RPC nodes serving production traffic require robust hardware:
 - **Memory**: 64 GB RAM minimum; 128 GB recommended for high traffic
 - **Storage**: Storage requirements vary by parachain. Fast NVMe I/O is critical for RPC query performance
     - **System parachains**: [Snapshots](https://snapshots.polkadot.io/){target=\_blank} _may_ be available
-        - **Archive node**: Using snapshots, expected storage requirements (including ~822 GB for the pruned relay chain) are:
+        - **Archive node (complete history)**: Using snapshots, expected storage requirements (including ~822 GB for the pruned relay chain) are:
             - **Asset Hub**: ~1.2 TB
             - **Bridge Hub**: ~1.1 TB
             - **Collectives**: ~1 TB
             - **People Chain**: ~900 GB
             - **Coretime**: ~900 GB
-        <!-- TODO-ERIN: this makes no sense to me 👇 -->
-        - **Pruned node**: 200+ GB for both parachain and relay chain 
+        - **Pruned node (recent state)**: ~200 GB total for both parachain and relay chain 
     - **Non-system parachains**: Consult the parachain team or documentation, then add ~822 GB for the pruned relay chain
 - **Network**:
     - Public IP address

node-infrastructure/run-a-node/polkadot-hub-rpc.md

@@ -24,9 +24,8 @@ RPC nodes serving production traffic require robust hardware. The following shou
 - **CPU**: 8+ cores; 16+ cores for high traffic
 - **Memory**: 64 GB RAM minimum; 128 GB recommended for high traffic
 - **Storage**:
-    - **Archive node**: ~1.2 TB NVMe SSD total (~392 GB for Asset Hub archive + ~822 GB for relay chain pruned snapshot)
-    <!-- TODO-ERIN: this means ~1.4 TB? 👇 -->
-    - **Pruned node**: 200+ GB NVMe SSD (with pruning enabled for both parachain and relay chain)
+    - **Archive node (complete history)**: ~1.2 TB NVMe SSD total (~392 GB for Asset Hub archive + ~822 GB for relay chain pruned snapshot)
+    - **Pruned node (recent state)**: ~2~00 GB NVMe SSD total (with pruning enabled for both parachain and relay chain)
     - Fast disk I/O is critical for query performance
 - **Network**:
     - Public IP address