Merge pull request 0xPolygon#2605 from 0xPolygon/jaime-dev

Agglayer: overview.md, pessimistic-proof.md, unified-bridge.md, agglayer-node.md

Author: pgebheim

docs/agglayer/architecture/agglayer-node.md

@@ -4,7 +4,8 @@
 
 **The Agglayer node** is the Rust-based service designed to receive zero-knowledge proofs from Agglayer-connected chains, verify their validity, and send them to the L1 for final settlement. 
 
-> **Note:** Instructions on how to clone and build the Agglayer locally, including running the pessimistic proof test suite and generating a verifiable proof using Succinct’s Prover Network, can be found [here](#).
+!!! note
+      Instructions on how to clone and build the Agglayer locally, including running the pessimistic proof test suite and generating a verifiable proof using Succinct’s Prover Network, can be found [here](https://github.com/agglayer/agglayer/blob/main/README.md)
 
 ## Crate directory
 

docs/agglayer/architecture/pessimistic-proof.md

@@ -23,11 +23,12 @@ For any cross-chain token transfer to be finalized such that the token may be wi
 !!! note
       For more on how the Agglayer settles bridge claims to the underlying L1, see: [Unified Bridge](/agglayer/architecture/unified-bridge/)
 
+
 ## Token State
 Each chain maintains a data structure called a **Local Exit Tree**, which contains only the messages and token transfers originating from it. In the unified bridge, Ethereum holds a **Global Exit Root**, which represents a tree containing all of the Local Exit Roots of chains integrated with the AggLayer.
 
 !!! note
-      For a detailed breakdown of all data used by the Agglayer, see: [Unified Bridge: Data Structures](/agglayer/architecture/unified-bridge.md#unified-bridge-data-structures)
+      For a detailed breakdown of all data used by the Agglayer, see: [Unified Bridge: Data Structures](../../agglayer/architecture/unified-bridge.md#unified-bridge-data-structures)
 
 In a simple token transfer, the source chain’s **Local Exit Tree** is used to reduce the balance of available tokens on its **Local Balance Tree**.
 

docs/agglayer/architecture/unified-bridge.md

@@ -34,9 +34,9 @@ Functionally similar to the **Local Exit Root**, but it tracks the bridging acti
 When the **Mainnet Exit Root** is updated in `PolygonZkEVMBridgeV2.sol`, the contract then updates `mainnetExitRoot` in `PolygonZkEVMGlobalExitRootV2.sol`.
 
 ### Global Exit Root, L1 Info Tree, Global Index
-**Global Exit Root** is the hash of the **Rollup Exit Root** and **Mainnet Exit Root**. When a new **Rollup Exit Root** or **Mainnet Exit Root** is submitted, the contract appends the new **Global Exit Root** to the **L1 Info Tree**.
-**L1 Info Tree** is a **Sparse Merkle Tree** that maintains Global Exit Roots. It is a binary tree with a height of 32, updated every time a new Global Exit Root is submitted. 
-**Global Index** is a **256-bit string** used to locate the unique leaf in the latest **Global Exit Tree** when creating and verifying SMT proofs.
+**Global Exit Root** is the hash of the Rollup Exit Root and Mainnet Exit Root. When a new Rollup Exit Root or Mainnet Exit Root is submitted, the contract appends the new **Global Exit Root** to the **L1 Info Tree**.
+**L1 Info Tree** is a Sparse Merkle Tree that maintains Global Exit Roots. It is a binary tree with a height of 32, updated every time a new Global Exit Root is submitted. 
+**Global Index** is a 256-bit string used to locate the unique leaf in the latest **Global Exit Tree** when creating and verifying SMT proofs.
 
 ## Bridge Service