Merge branch 'zkevm/arch-menu' of https://github.com/0xPolygon/polygon-docs into zkevm/arch-menu

Author: kmurphypolygon

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

@@ -4,7 +4,7 @@
 
 This section of the docs provides a detailed analysis of the full topology of the Polygon zero-knowledge system architecture. 
 
-Built for CDK stacks and using zkEVM technology, these documents explain the contents, layout, and interactions between component systems and functions, drilling down into detailed descriptions of the components that make up the wider system with reference to the relevant code bases.
+Tailored for CDK stacks and using zkEVM technology, these documents explore the contents, layout, and interactions among component systems and functions. They offer in-depth descriptions of the components that constitute the larger system, with references to relevant code bases.
 
 The diagram below is a full and detailed topological overview of the entire Polygon zero-knowledge system architecture.
 
@@ -17,7 +17,7 @@ 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.
 - 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.
+    - Aggregator: Used for aggregating transaction batches to send to the prover. 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.
@@ -33,8 +33,8 @@ When complete, this section will include information on:
 
 - The structure of a CDK node and how it interacts with L2 and L1 smart contracts.
 - The structure of a zkEVM node and how it interacts with L2 and L1 smart contracts.
-- The key components included in the nodes, how they function, and their interactions with other components, external developers, and the L1/L2 environment.
-- Key similarities and differences between a CDK and zkEVM node set up.
+- The key components included in the nodes, how they function, and their interactions with other components, external dApps, and the L1/L2 environment.
+- Key similarities and differences between a CDK and zkEVM node.
 - CDK validium components, including the DAC and DAC sequencer.
 - Detailed description of the Polygon smart contract sets for L1 and L2.
 - The zkProver and how it interacts with a zkEVM node aggregator.