update agglayer and inanddesign

kmurphypolygon · kmurphypolygon · commit 1d24cf470d5d · 2024-08-16T11:05:44.000+02:00
diff --git a/docs/cdk/agglayer/agglayer-go.md b/docs/cdk/agglayer/agglayer-go.md
@@ -1,5 +1,3 @@
-## Overview
-
 The AggLayer-go is a service designed to receive zero-knowledge (ZK) proofs  from various CDK chains and verify their validity before sending them to the L1 for final settlement.
 
 !!! warning
diff --git a/docs/cdk/agglayer/agglayer-rs.md b/docs/cdk/agglayer/agglayer-rs.md
@@ -1,6 +1,6 @@
-## Overview
+AggLayer-rs is a Rust-based service designed to receive ZK proofs from various CDK chains and verify their validity before sending them to the L1 for final settlement. 
 
-AggLayer-rs is a Rust-based service designed to receive ZK 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).
+It replaces the previous [Golang implementation](agglayer-go.md).
 
 ## Architecture
 
diff --git a/docs/cdk/agglayer/overview.md b/docs/cdk/agglayer/overview.md
@@ -1,18 +1,13 @@
 !!! info "Disclaimer"
     - 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.
+    - Feel free to experiment with any code in the [AggLayer public repos](https://github.com/agglayer/).
 
 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 ZK proofs. 
 
 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
 
-### Polygon CDK
-
-The AggLayer connects chains built with Polygon CDK, which use ZK proofs to generate state transitions that are cryptographically secure. 
-
 ### Unified bridge
 
 The unified bridge is a single bridge contract for all AggLayer-connected chains, allowing for the cross-chain transfer of fungible (non-wrapped) tokens. It is the source of unified liquidity for the AggLayer. 
@@ -22,4 +17,8 @@ The unified bridge is a single bridge contract for all AggLayer-connected chains
 
 ### AggLayer service
 
-The AggLayer service is a service designed to receive ZK 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).
+The AggLayer service is a service designed to receive ZK proofs from various zk-powered 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).
+
+## Further reading
+
+Check out the [aggregated blockchains blog](https://polygon.technology/blog/aggregated-blockchains-a-new-thesis) for more information.
diff --git a/docs/cdk/agglayer/token-flows.md b/docs/cdk/agglayer/token-flows.md
@@ -1,4 +1,4 @@
-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. 
+The following workflows describe how token transfers and message passing are implemented by the unified bridge across various L1 and L2 permutations. While the descriptions refer only to token transfers in the current AggLayer implementation, the sequence of events is exactly the same for arbitrary messages. 
 
 ## L1 to L2
 
@@ -34,7 +34,7 @@ The following describes how token transfers and message passing are implemented
 
 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.
 
-2. The bridge contracts communicates the L2 exit tree root to the L2 global exit root manager. The L2 global exit root manager, however, does not update the global exit tree at this stage.
+2. The bridge contract communicates the L2 exit tree root to the L2 global exit root manager. The L2 global exit root manager, however, does not update the global exit tree at this stage.
 
 3. For proving and verification, the zk-proof-generating circuit obtains the L2 exit tree root from the L2 global exit root manager.
 
diff --git a/docs/cdk/agglayer/unified-bridge.md b/docs/cdk/agglayer/unified-bridge.md
@@ -1,8 +1,5 @@
-## Overview
-
 The unified bridge is a single bridge contract on Ethereum, providing a safe, common access point for the transfer of all native, never-wrapped tokens. Each chain has a local copy of the unified bridge root, enabling cross-chain interoperability that doesn’t require the security risks of third-party bridges.
 
-
 !!! important "AggLayer smart contracts"
     - The current version of the unified bridge uses the contracts in the [PolygonzkEVM smart contract repo](https://github.com/0xPolygonHermez/zkevm-contracts).
 
diff --git a/docs/innovation-design/index.md b/docs/innovation-design/index.md
@@ -31,12 +31,12 @@ hide:
    </div>
 </div>
 <div class="grid-container">
-   <div class="grid-item">
-      <a href="../cdk/agglayer/overview">
+    <div class="grid-item">
+      <a href="./polygon-protocols">
          <div class="product-list-item-header">
-            <div class="feature-card-heading">AggLayer documentation</div>
+            <div class="feature-card-heading">The future of Polygon network</div>
          </div>
-         <p class="feature-paragraph">AggLayer solves blockchain fragmentation by enabling sovereign chains to securely share liquidity, users, and state.</p>
+         <p class="feature-paragraph">Upcoming updates and iterations across Polygon network</p>
       </a>
    </div>
    <div class="grid-item">
@@ -62,14 +62,6 @@ hide:
          </div>
          <p class="feature-paragraph">State-of-the-art cryptography libraries for developers.</p>
       </a>
-   </div>
-    <div class="grid-item">
-      <a href="./polygon-protocols">
-         <div class="product-list-item-header">
-            <div class="feature-card-heading">The future of Polygon network</div>
-         </div>
-         <p class="feature-paragraph">Upcoming updates and iterations across Polygon network</p>
-      </a>
    </div>
    <div class="grid-item">
       <a href="https://polygon.technology/blog/reorgs-demystified-insights-from-monitoring-with-a-sensor-network">
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -556,15 +556,15 @@ nav:
           - Polygon: https://polygonscan.com/ 
           - zkEVM: https://zkevm.polygonscan.com/
           - zkEVM testnet: https://cardona-zkevm.polygonscan.com/
+  - AggLayer:
+    - Overview: cdk/agglayer/overview.md
+    - AggLayer | Unified bridge: cdk/agglayer/unified-bridge.md
+    - AggLayer | Go: cdk/agglayer/agglayer-go.md
+    - AggLayer | Rust: cdk/agglayer/agglayer-rs.md
+    - AggLayer | Token flows: cdk/agglayer/token-flows.md
   - Innovation & design:
       - Innovation & design: innovation-design/index.md
       - Welcome: innovation-design/welcome.md
-      - AggLayer:
-        - Overview: cdk/agglayer/overview.md
-        - AggLayer | Unified bridge: cdk/agglayer/unified-bridge.md
-        - AggLayer | Go: cdk/agglayer/agglayer-go.md
-        - AggLayer | Rust: cdk/agglayer/agglayer-rs.md
-        - AggLayer | Token flows: cdk/agglayer/token-flows.md
       - Polygon type 1 prover:
           - Introduction and definitions: cdk/architecture/type-1-prover/intro-t1-prover.md
           - How to:

Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,3 @@`
`1`		`-## Overview`
`2`		`-`
`3`	`1`	`The AggLayer-go is a service designed to receive zero-knowledge (ZK) proofs from various CDK chains and verify their validity before sending them to the L1 for final settlement.`
`4`	`2`
`5`	`3`	`!!! warning`