add a few lines restructure the list

Author: kmurphypolygon

docs/zkEVM/architecture/high-level/overview.md

@@ -16,14 +16,16 @@ The diagram below is a full and detailed topological overview of the entire Poly
 
 - Smart contracts: L1 and L2 Solidity smart contracts used for interacting with the whole stack. See the discussion on [zkEVM smart contracts](../../architecture/protocol/zkevm-bridge/smart-contracts.md) for more information.
 - Exit root trees: Append-only sparse Merkle trees which record the current and historical state of the system. See the discussion on [zkEVM exit trees](../../architecture/protocol/zkevm-bridge/exit-tree.md) for more information.
-- Aggregator: Used for aggregating transactions into batches for proving. See the discussion on [aggregators](../../architecture/index.md#aggregator) for more information.
-- Sequencer: Does the complex job of carefully sequencing transactions as they come in before sending them to the aggregator for batching. See the discussion on [sequencers](../../architecture/index.md#sequencer) for more information.
-- Synchronizer: This component ensures a synchronized state between the node's systems and the L1 outside world via the Etherman component and the state database. 
-- Etherman component: The Etherman helps the synchronizer maintain a synchronized state with L1 by communicating with the L1 Ethereum chain via smart contract methods.
-- JSON RPC client: Allows computational read/write access to the system via published methods which, when called, interact with the pool and state databases.
-- Pool database: The pool database records transaction requests coming in from the JSON RPC client and sends them to the sequencer.
-- State database: The state database responds to read requests from the JSON RPC client.
+- CDK and zkEVM nodes containing:
+    - Aggregator: Used for aggregating transactions into batches for proving. See the discussion on [aggregators](../../architecture/index.md#aggregator) for more information.
+    - Sequencer: Does the complex job of carefully sequencing transactions as they come in before sending them to the aggregator for batching. See the discussion on [sequencers](../../architecture/index.md#sequencer) for more information.
+    - Synchronizer: This component ensures a synchronized state between the node's systems and the L1 outside world via the Etherman component and the state database. 
+    - Etherman component: The Etherman helps the synchronizer maintain a synchronized state with L1 by communicating with the L1 Ethereum chain via smart contract methods.
+    - JSON RPC client: Allows computational read/write access to the system via published methods which, when called, interact with the pool and state databases.
+    - Pool database: The pool database records transaction requests coming in from the JSON RPC client and sends them to the sequencer.
+    - State database: The state database responds to read requests from the JSON RPC client.
 - Bridge service component: Main facility for transferring tokens from L1 to L2 and back again.
+- Prover component: System for calculating zero-knowledge proofs on transaction batches.
 
 ## What to expect