Update the "Operators > Node Setup" index page

docs/operators/maintenance/index.md

@@ -4,5 +4,6 @@ This section covers maintenance actions such as moving a node to a different loc
 
 | Title                                                                           | Description                 |
 | ----------------------------------------------------------- | ----------------------------------------------- |
+|[Upgrading the Node](./upgrade.md) | How to stage and verify protocol upgrades on your node |
 |[Archiving and Restoring a Database](./archiving-and-restoring.md) | Using `zstd` for the compression and decompression of a Casper node database and streaming from a backup location |
 |[Moving a Validating Node](./moving-node.md) | Ways to move a validator node to another machine   |

docs/operators/setup/index.md

@@ -1,6 +1,6 @@
 # Setting up a Node
 
-The prerequisite for becoming a validator is to set up a node and join a network as described here.
+To participate as a validator, you must first set up a Casper node and join the network. Node setup instructions apply whether you're running a validator, an RPC node, or an archival node.
 
 | Title                                                                           | Description                 |
 | ----------------------------------------------------------- | ----------------------------------------------- |
@@ -9,7 +9,6 @@ The prerequisite for becoming a validator is to set up a node and join a network
 |[Node Endpoints](./node-endpoints.md) | Ports for communicating with other nodes and dApps |
 |[Installing a Node](./install-node.md) | Step-by-step instructions to install a Casper node |
 |[Setting the Open Files Limit](./open-files.md) | Required setting for the Casper node to run correctly |
-|[Upgrading the Node](./upgrade.md) | Before joining the network, the node needs to be upgraded |
 |[Joining a Running Network](./joining.md) | Steps to join an existing Casper network |
 |[Setting up a Non-Root User](./non-root-user.md) | Logging into the node remotely using a key |
 |[Node Events](./node-events.md) | Information on a node's events stream |

docs/operators/setup/node-endpoints.md

@@ -50,7 +50,7 @@ address = '0.0.0.0:8888'
 
 Opening port 8888 is recommended but not required. This port allows the node to be included in the general network health metrics, thus giving a more accurate picture of overall network health. If this port is closed, the requests coming to this port will not be served, but the node remains unaffected.
 
-One may use this port to [get a trusted hash](./basic-node-configuration.md#trusted-hash-for-synchronizing), [verify successful staging](./upgrade.md#verifying-successful-staging) during an upgrade, or to [confirm that the node is synchronized](./joining.md#step-7-confirm-the-node-is-synchronized).
+One may use this port to [get a trusted hash](./basic-node-configuration.md#trusted-hash-for-synchronizing), [verify successful staging](../maintenance/upgrade.md#verifying-successful-staging) during an upgrade, or to [confirm that the node is synchronized](./joining.md#step-7-confirm-the-node-is-synchronized).
 
 
 ### Example usage
@@ -210,7 +210,7 @@ Here is a summary of the links mentioned on this page:
 - [Interacting with the network using CLI](../../developers/cli/index.md)
 - [Bonding](../becoming-a-validator/bonding.md#example-bonding-transaction) or [unbonding](../becoming-a-validator/unbonding.md) as a validator
 - [Getting a trusted node hash](./basic-node-configuration.md#trusted-hash-for-synchronizing)
-- [Verifying successful staging](./upgrade.md#verifying-successful-staging)
+- [Verifying successful staging](../maintenance/upgrade.md#verifying-successful-staging)
 - [Confirming that the node is synchronized](./joining.md#step-7-confirm-the-node-is-synchronized)
 - [Monitoring and consuming events](../../developers/dapps/monitor-and-consume-events.md)
 - [Private network access control](../setup-network/create-private.md#network-access-control)

versioned_docs/version-2.0.0/operators/maintenance/index.md

@@ -4,5 +4,6 @@ This section covers maintenance actions such as moving a node to a different loc
 
 | Title                                                                           | Description                 |
 | ----------------------------------------------------------- | ----------------------------------------------- |
+|[Upgrading the Node](./upgrade.md) | How to stage and verify protocol upgrades on your node |
 |[Archiving and Restoring a Database](./archiving-and-restoring.md) | Using `zstd` for the compression and decompression of a Casper node database and streaming from a backup location |
 |[Moving a Validating Node](./moving-node.md) | Ways to move a validator node to another machine   |

versioned_docs/version-2.0.0/operators/setup/index.md

@@ -1,6 +1,6 @@
 # Setting up a Node
 
-The prerequisite for becoming a validator is to set up a node and join a network as described here.
+To participate as a validator, you must first set up a Casper node and join the network. Node setup instructions apply whether you're running a validator, an RPC node, or an archival node.
 
 | Title                                                                           | Description                 |
 | ----------------------------------------------------------- | ----------------------------------------------- |
@@ -9,7 +9,6 @@ The prerequisite for becoming a validator is to set up a node and join a network
 |[Node Endpoints](./node-endpoints.md) | Ports for communicating with other nodes and dApps |
 |[Installing a Node](./install-node.md) | Step-by-step instructions to install a Casper node |
 |[Setting the Open Files Limit](./open-files.md) | Required setting for the Casper node to run correctly |
-|[Upgrading the Node](./upgrade.md) | Before joining the network, the node needs to be upgraded |
 |[Joining a Running Network](./joining.md) | Steps to join an existing Casper network |
 |[Setting up a Non-Root User](./non-root-user.md) | Logging into the node remotely using a key |
 |[Node Events](./node-events.md) | Information on a node's events stream |

versioned_docs/version-2.0.0/operators/setup/node-endpoints.md

@@ -50,7 +50,7 @@ address = '0.0.0.0:8888'
 
 Opening port 8888 is recommended but not required. This port allows the node to be included in the general network health metrics, thus giving a more accurate picture of overall network health. If this port is closed, the requests coming to this port will not be served, but the node remains unaffected.
 
-One may use this port to [get a trusted hash](./basic-node-configuration.md#trusted-hash-for-synchronizing), [verify successful staging](./upgrade.md#verifying-successful-staging) during an upgrade, or to [confirm that the node is synchronized](./joining.md#step-7-confirm-the-node-is-synchronized).
+One may use this port to [get a trusted hash](./basic-node-configuration.md#trusted-hash-for-synchronizing), [verify successful staging](../maintenance/upgrade.md#verifying-successful-staging) during an upgrade, or to [confirm that the node is synchronized](./joining.md#step-7-confirm-the-node-is-synchronized).
 
 
 ### Example usage
@@ -210,7 +210,7 @@ Here is a summary of the links mentioned on this page:
 - [Interacting with the network using CLI](../../developers/cli/index.md)
 - [Bonding](../becoming-a-validator/bonding.md#example-bonding-transaction) or [unbonding](../becoming-a-validator/unbonding.md) as a validator
 - [Getting a trusted node hash](./basic-node-configuration.md#trusted-hash-for-synchronizing)
-- [Verifying successful staging](./upgrade.md#verifying-successful-staging)
+- [Verifying successful staging](../maintenance/upgrade.md#verifying-successful-staging)
 - [Confirming that the node is synchronized](./joining.md#step-7-confirm-the-node-is-synchronized)
 - [Monitoring and consuming events](../../developers/dapps/monitor-and-consume-events.md)
 - [Private network access control](../setup-network/create-private.md#network-access-control)