Revert "Update overview.md"

This reverts commit 731382d.

Author: kmurphypolygon

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

@@ -13,17 +13,17 @@ The diagram below is a full and detailed topological overview of the entire Poly
 ## Components 
 
 - Smart contracts: L1 and L2 Solidity smart contracts used for interacting with the whole stack.
-- Exit root trees: Append-only sparse Merkle trees which record the current and historical state of the network. 
+- Exit root trees: Append-only sparse Merkle trees which record the current and historical state of the system. 
 - CDK and zkEVM nodes containing:
     - JSON RPC client: Exposes the read/write interfaces for interacting with a node/chain.
-    - Pool database: Records transactions coming in from the JSON RPC client.
-    - State database: Permanently stores state data.
-    - Sequencer: A node responsible for fetching transactions from the pool database, executes and puts them into batches. See the discussion on [sequencers](../../architecture/index.md#sequencer) for more information.
-    - Aggregator: A node tasked with aggregating batches and using the prover to produce proofs of computational integrity. See the discussion on [aggregators](../../architecture/index.md#aggregator) for more information.
-    - Synchronizer: Updates the state database by fetching data from Ethereum through the Etherman.
-    - Etherman: Implements methods for interacting with the L1 network and smart contracts.
-- Bridge service: Provides an API to perform bridge claims, i.e. asset and message transfers between L1/L2 and L2/L2.
-- Prover: System for generating proofs attesting to computational integrity.
+    - 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.
+    - 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.
+    - Aggregator: Used for aggregating transaction batches to send to the prover. See the discussion on [aggregators](../../architecture/index.md#aggregator) 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 functions.
+- Bridge service component: Provides an API to perform bridge claims, i.e. asset and message transfers between L1/L2 and L2/L2.
+- Prover component: System for calculating zero-knowledge proofs on transaction batches.
 
 ## What to expect