diff --git a/docs/docs/guides/developer_guides/running_nodes/running_provers.md b/docs/docs/guides/developer_guides/running_nodes/running_provers.md
index 08c82423723..65c66279486 100644
--- a/docs/docs/guides/developer_guides/running_nodes/running_provers.md
+++ b/docs/docs/guides/developer_guides/running_nodes/running_provers.md
@@ -1,7 +1,11 @@
+---
+draft: true
+---
+
 # Running Prover Nodes
 
 TODO(https://github.com/AztecProtocol/aztec-packages/issues/9190)
-*Details about how to configure a prover node and hardware requirements are to be determined. This guide will be updated once the information becomes available.*
+_Details about how to configure a prover node and hardware requirements are to be determined. This guide will be updated once the information becomes available._
 
 For the current state of design please see the RFC at https://forum.aztec.network/t/request-for-comments-aztecs-block-production-system/6155.
 
diff --git a/docs/docs/guides/developer_guides/running_nodes/running_validators.md b/docs/docs/guides/developer_guides/running_nodes/running_validators.md
index 26a09f32a9c..45588045341 100644
--- a/docs/docs/guides/developer_guides/running_nodes/running_validators.md
+++ b/docs/docs/guides/developer_guides/running_nodes/running_validators.md
@@ -1,3 +1,7 @@
+---
+draft: true
+---
+
 # Aztec Validator Node Guide
 
 ## Introduction
@@ -284,15 +288,18 @@ This is a brief summary to understand what the validator is doing at a high leve
 Validators are selected through a committee selection process:
 
 - **Epoch Initialization**:
+
   - At the start of each epoch, the rollup contract computes a random seed using `block.prevrandao`.
   - The seed is used to select a committee of validators using the Swap-or-Not algorithm.
   - The committee size is fixed for the duration of the epoch.
 
 - **Proposer Selection**:
+
   - Each validator in the committee is assigned proposer duties for specific slots within the epoch.
   - Proposers know in advance when they will be required to propose a block.
 
 - **Validator Registration**:
+
   - The rollup contract maintains the active set of validators.
   - Updates to the validator set occur at the beginning of new epochs.
   - Registration includes staking a minimum threshold of collateral (amount to be determined).
diff --git a/docs/docs/guides/index.md b/docs/docs/guides/index.md
index cb047909a87..05eb85fea9b 100644
--- a/docs/docs/guides/index.md
+++ b/docs/docs/guides/index.md
@@ -45,24 +45,3 @@ In this section you will find:
     </CardBody>
   </Card>
 </div>
-
-## Running Aztec Nodes
-
-<div className="card-container">
-  <Card shadow='tl' link='/guides/developer_guides/running_nodes/running_validators'>
-    <CardHeader>
-      <h3>Run Aztec Validator Nodes</h3>
-    </CardHeader>
-    <CardBody>
-      Participate in the Aztec protocol as a validator (also called a sequencer) that helps form consensus on what goes into a block. Runs on consumer hardware.
-    </CardBody>
-  </Card>
-  <Card shadow='tl' link='/guides/developer_guides/running_nodes/running_provers'>
-    <CardHeader>
-      <h3>Run Aztec Prover Nodes</h3>
-    </CardHeader>
-    <CardBody>
-      Participate in the Aztec protocol as a prover node, proving the rollup integrity that is pivotal to the protocol. Runs on hardware fit for data centers.
-    </CardBody>
-  </Card>
-</div>
\ No newline at end of file