remove pics

Author: kmurphypolygon

docs/cdk/agglayer/agglayer-go.md

@@ -1,15 +1,15 @@
 ## Overview
 
-The AggLayer Golang is a web service designed to receive zero-knowledge proofs (ZKP) from CDK chains, ensure they are valid, and send them to the L1 verifier contract for final verification.
+The AggLayer-go is a service designed to receive zero-knowledge proofs (ZKP) from various CDK chains and verify their validity before sending them to the L1 for final settlement.
 
 !!! warning
-    This service is being deprecated and replaced with a more robust and efficient [Rust implementation](agglayer-rs.md).
+    This service is being deprecated n favor of the more robust and efficient [Rust implementation](agglayer-rs.md).
 
 ## Architecture
 
-The AggLayer Golang architecture supports interoperability among connected CDK chains by using ZKPs to ensure safety. It uses a PostgreSQL database for storage and interacts with both L1 and L2 chains through configured RPC nodes.
+The AggLayer golang architecture supports interactions with multiple CDK chains for proof-verification. It uses a PostgreSQL database for storage and interacts with both L1 and L2 chains through configured RPC nodes.
 
-The diagram below shows the full start-up, running, and shutdown sequence for the AggLayer Golang application and its components.
+The diagram below shows the full start-up, running, and shutdown sequence for the application and its components.
 
 <center>
 ![CDK architecture](../../img/cdk/agglayer/agglayer-go.png)
@@ -97,4 +97,4 @@ Refer to the `cmd` and `client` directories for API implementation details. Docu
 
 ---
 
-For more information, visit the [AggLayer Golang repository](https://github.com/AggLayer/agglayer-go).
+For more information, visit the [AggLayer-go repository](https://github.com/AggLayer/agglayer-go).

docs/cdk/agglayer/agglayer-rs.md

@@ -1,25 +1,10 @@
 ## Overview
 
-The AggLayer is a Rust-based web service designed to ensure safety for cross-chain asset transfers among heterogeneous blockchain networks. This safety is provided using ZKPs, allowing end-users to interoperate with no additional trust assumptions.  
-
-The service verifies the validity of proofs from various CDK chains before forwarding them to L1 for verification.
-
-It replaces the previous [Golang implementation](agglayer-go.md).
+AggLayer-rs is a Rust-based service designed to receive zero-knowledge proofs from various CDK chains and verify their validity before sending them to the L1 for final settlement. It replaces the previous [Golang implementation](agglayer-go.md).
 
 ## Architecture
 
-### Components
-
-- Unified bridge: A shared bridge contract for all AggLayer-connected chains, allowing for the transfer of native assets. 
-- Pessimistic proof: A novel ZKP that provides safety for the assets on the unified bridge by ensuring no chain can withdraw more tokens of any type than have been deposited into it. Pessimistic proofs are validated by the verifier contract on the L1. 
-
-### Data flow
-
-- Input: Proofs of execution generated by CDK chains.
-- Processing: Verification of proofs.
-- Output: Verified proofs sent to L1.
-
-[pic-here]
+The AggLayer Rust architecture supports interactions with multiple CDK chains for proof-verification. Its architecture is the same as `agglayer-go`, but without the PostgreSQL database for storage. 
 
 ## Getting started
 

docs/cdk/agglayer/bridge-and-call.md

@@ -1,58 +1,27 @@
 !!! info "Disclaimer"
-    - Much of the content in this section is discussing technology in development and not ready for release.
+    - Some of the content in this section discusses technology in development and not ready for release.
     - Please check against the main documentation site for any live releases.
     - Feel free to experiment with any code in public repos.
 
 ## Welcome to AggLayer documentation
 
-The culmination of Polygon Lab's innovation and design, AggLayer is an evolving ecosystem of zk-based (zero-knowledge) interacting chains. It addresses the current industry focus on interoperability and shared liquidity.
+The AggLayer is an in-development interoperability protocol that allows for trustless, cross-chain token transfers and message-passing, as well as more complex operations. The safety of the AggLayer is provided by zero-knowledge proofs. 
 
-While most rollup environments follow a modular approach, where developers pick-and-choose components such as execution and data availability layers for example, the AggLayer vision is uniquely centered around zk-proof technology.
-
-<center>
-![CDK architecture](../../img/cdk/agglayer/mono-modu.png)
-</center>
+The AggLayer currently connects chains built with Polygon CDK, a developer toolkit for designing ZK-powered Layer 2s. The long term goal for the protocol is to be flexible enough to provide interoperability among a growing range of blockchain architectures, including L2s, appchains, and non-EVM chains. 
 
 ## AggLayer components
 
-AggLayer connects CDK chains and provides a zero-knowledge prover for validity and security.
-
-<center>
-![CDK architecture](../../img/cdk/cdk-architecture.png)
-</center>
-
-### Chain development kit (CDK)
-
-- CDK chains connect to AggLayer.
-- CDK chains are similar to other rollup stacks but enforce unique zk-based cryptographic proofs for transaction validation to ensure robust security and efficiency.
-- Non-CDK chains will also eventually connect to AggLayer.
-
-### AggLayer
-
-- Running now on the unified bridge technology, AggLayer takes a many-to-many approach to CDK chain interactions which focuses on validity, interoperability, and security.
-- It aggregates and batches proofs from multiple CDK chains into a single proof, significantly lowering the verification cost across chains as the ecosystem grows.
-
-<center>
-![AggLayer overview](../../img/cdk/agglayer/agg-layer-overview.png)
-</center>
-
-- AggLayer ensures seamless and correct ordering of cross-chain transaction execution and securely-shared liquidity across all zk-based chains.
-
-### Provers
+### Polygon CDK
 
-- Provers generate cryptographic proofs for zk-based chains that verify the validity of transactions.
-- Ethereum smart contracts then validate those proofs.
-- The cost of proof validation on Ethereum remains fixed regardless of the number of transactions.
-- AggLayer offers a modular approach to provers. Options include the Polygon zkEVM prover technology and the SP1/Plonky 3 prover currently in development.
+The AggLayer connects chains built with Polygon CDK, which use ZK proofs to generate state transitions that are cryptographically secure. 
 
-<center>
-![AggLayer overview](../../img/cdk/agglayer/prover.png)
-</center>
+### Unified bridge
 
-## What to expect
+The unified bridge is a single bridge contract for all AggLayer-connected chains, allowing for the cross-chain transfer of fungible (non-wrapped) tokens. In the abstract, it is the source of unified liquidity for the AggLayer. 
 
-These documents introduce you to the current unified bridge technology that inspires and underpins AggLayer. 
+!!! tip "More information"
+    See the [unified bridge documentation](unified-bridge.md) for details. 
 
-We also document some of AggLayer's key technology in development now; such as the Go and Rust libraries, the bridge and call API, and Plonky prover technology. 
+### AggLayer service
 
-We also document a little about what the future has in store.
+The AggLayer service is a service designed to receive zero-knowledge proofs from various CDK chains and verify their validity before sending them to the L1 for final settlement. Currently, the AggLayer service has two implementations: [agglayer-go](agglayer-go.md) and [agglayer-rs](agglayer-rs.md).

docs/cdk/agglayer/overview.md

@@ -1,12 +1,8 @@
-The following document describes how token and message transactions are implemented by the unified bridge across various L1 and L2 permutations.
+The following describes how token transfers and message passing are implemented by the unified bridge across various L1 and L2 permutations. While the examples provided describe only token transfers, the sequence is the same for arbitrary messages in this current implementation of the AggLayer. 
 
-<center>
-![Token flows](../../img/cdk/agglayer/tx-flows.png)
-</center>
+## L1 to L2
 
-### L1 to L2
-
-1. If a call to `bridgeAsset` or `bridgeMessage` on L1 passes validation, the bridge contract appends an exit leaf to the L1 exit tree and computes the new L1 exit tree root.
+1. If a call to `bridgeAsset` or `bridgeMessage` on L1 passes validation, the unified bridge contract appends an exit leaf to the L1 exit tree and computes the new L1 exit tree root.
 
 2. The global exit root manager appends the new L1 exit tree root to the global exit tree and computes the global exit root.
 
@@ -16,25 +12,25 @@ The following document describes how token and message transactions are implemen
 
 5. A call to `claimAsset` or `claimMessage` provides a Merkle proof that validates the correct exit leaf in the global exit root.
 
-6. The bridge contract validates the caller's Merkle proof against the global exit root. If the proof is valid, the bridging process succeeds; otherwise, the transaction fails.
+6. The unified bridge contract validates the caller's Merkle proof against the global exit root. If the proof is valid, the bridging process succeeds; otherwise, the transaction fails.
 
-### L2 to L1
+## L2 to L1
 
-1. If a call to `bridgeAsset` or `bridgeMessage` on L2 passes validation, the bridge contract appends an exit leaf to the L2 exit tree and computes the new L2 exit tree root.
+1. If a call to `bridgeAsset` or `bridgeMessage` on L2 passes validation, the unified bridge contract appends an exit leaf to the L2 exit tree and computes the new L2 exit tree root.
 
-2. The L2 global exit root manager appends the new L2 exit tree root to the global exit tree and computes the global exit root. At that point, the caller's bridge transaction is included in one of batches selected and sequenced by the sequencer.
+2. The L2 global exit root manager appends the new L2 exit tree root to the global exit tree and computes the global exit root. At that point, the caller's bridge transaction is included in one of the batches selected and sequenced by the sequencer.
 
 3. The aggregator generates a zk-proof attesting to the computational integrity in the execution of sequenced batches which include the transaction.
 
-4. For verification purposes, the aggregator sends the zk-proof together with all relevant batch information that led to the new L2 exit tree root (computed in step 2), to the consensus contract.
+4. For verification purposes, the aggregator sends the zk-proof together with all relevant batch information that led to the new L2 exit tree root (computed in step 2), to the verifier contract.
 
-5. The consensus contract utilizes the `verifyBatches` function to verify validity of the received zk-proof. If valid, the contract sends the new L2 exit tree root to the global exit root manager in order to update the global exit tree.
+5. The verifier contract utilizes the `verifyBatches` function to verify validity of the received zk-proof. If valid, the contract sends the new L2 exit tree root to the global exit root manager in order to update the global exit tree.
 
-6. `claimMessage` or `claimAsset` is then called on the bridge contract with Merkle proofs for correct validation of exit leaves.
+6. `claimMessage` or `claimAsset` is then called on the unified bridge contract with Merkle proofs for correct validation of exit leaves.
 
-7. The bridge contract retrieves the global exit root from the L1 global exit root manager and verifies validity of the Merkle proof. If the Merkle proof is valid, the bridge completes. Otherwise, the transaction is reverted.
+7. The unified bridge contract retrieves the global exit root from the L1 global exit root manager and verifies validity of the Merkle proof. If the Merkle proof is valid, the settlement completes, otherwise, the transaction is reverted.
 
-### L2 to L2
+## L2 to L2
 
 1. When a batch of transactions is processed, the bridge contract appends the L2 exit tree with a new leaf containing the batch information. This updates the L2 exit tree root.