Add Consensus clients article

docs/04-monitoring/monitoring-node-health.md

@@ -103,7 +103,7 @@ When it becomes **Healthy** (**synced** and with **peers**) you should receive:
 
 This check verifies if the client receives messages from the CL. If you see this warning in your logs, it means that
 there is something wrong with CL<->Nethermind communication. Check more about setting up Nethermind and
-CL [here](../fundamentals/10-running-nethermind-post-merge.md).
+CL [here](../get-started/consensus-clients.md).
 
 ```
 No incoming messages from Consensus Client. Consensus Client is required to sync the node. Please make sure that it's working properly.

docs/07-resources/guides-and-helpers/validator-setup/eth2-validator.md

@@ -64,7 +64,7 @@ Run the following command to install Nethermind:
 sudo add-apt-repository ppa:nethermindeth/nethermind; sudo apt install nethermind
 ```
 
-See [here](../../../fundamentals/10-running-nethermind-post-merge.md) for docs for
+See [here](../../../get-started/consensus-clients.md) for docs for
 other ways to install Nethermind.
 
 #### **Installing Consensus Client**
@@ -146,7 +146,7 @@ sudo chown -R nethermindeth:nethermindeth /usr/share/nethermind
 
 Create a JWT Token which will be used to communicate between consensus and execution clients. For more information about
 JWT Token please refer
-to [this section](../../../fundamentals/10-running-nethermind-post-merge.md#step-3--configure-json-rpc-api).
+to [this section](../../../get-started/consensus-clients.md#step-3--configure-json-rpc-api).
 
 ```bash
 openssl rand -hex 32 | tr -d "\n" > "/var/lib/nethermind/jwt-secret"