Update index.md

rmv redundancy

Author: m4sterbunny

public/content/developers/docs/nodes-and-clients/node-architecture/index.md

@@ -4,7 +4,7 @@ description: Introduction to how Ethereum nodes are organized.
 lang: en
 ---
 
-An Ethereum node is composed of a minimum of two clients: an [execution client](/developers/docs/nodes-and-clients/#execution-clients) and a [consensus client](/developers/docs/nodes-and-clients/#consensus-clients). For a node to propose a new block, it must also run a [validator client](#validators) and stake ETH.
+An Ethereum node is composed of a minimum of two clients: an [execution client](/developers/docs/nodes-and-clients/#execution-clients) and a [consensus client](/developers/docs/nodes-and-clients/#consensus-clients). For a node to propose a new block, it must also run a [validator client](#validators).
 
 When Ethereum was using [proof-of-work](/developers/docs/consensus-mechanisms/pow/), an execution client was enough to run a full Ethereum node. However, since implementing [proof-of-stake](/developers/docs/consensus-mechanisms/pow/), the execution client must be used alongside another piece of software called a [consensus client](/developers/docs/nodes-and-clients/#consensus-clients).
 
@@ -58,4 +58,4 @@ Staking and running the validator software makes a node eligible to be selected
 
 - [Proof-of-stake](/developers/docs/consensus-mechanisms/pos)
 - [Block proposal](/developers/docs/consensus-mechanisms/pos/block-proposal)
-- [Validator rewards and penalties](/developers/docs/consensus-mechanisms/pos/rewards-and-penalties)
+- [Validator rewards and penalties](/developers/docs/consensus-mechanisms/pos/rewards-and-penalties)