zkEVM update - fixed broken links

Author: EmpieichO

docs/cdk/agglayer/unified-bridge.md

@@ -8,7 +8,7 @@ The unified bridge is a single bridge contract on Ethereum, providing a safe, co
 
 ## Bridging mechanism
 
-The bridging mechanism enables token transfers and message-passing between Ethereum (L1) and CDK chains via smart contracts. Detailed in the [zkEVM bridging documentation](../../zkEVM/architecture/high-level/smart-contracts/bridging.md), core components include the bridge and exit root Solidity smart contracts.
+The bridging mechanism enables token transfers and message-passing between Ethereum (L1) and CDK chains via smart contracts. Detailed in the [zkEVM bridging documentation](../../zkEVM/architecture/high-level/unified-LxLy/bridging.md), core components include the bridge and exit root Solidity smart contracts.
 
 ## Data structures 
 

docs/cdk/concepts/bridging.md

@@ -8,7 +8,7 @@ CDK-built chains come with a built-in bridge service and customizable UI out of
 
 The LxLy bridge contracts carry out deposit and withdrawal of assets between L2 and L1.
 
-Chains looking to run their own bridge infrastructure can choose to deploy a new instance of the [LxLy bridge](../../zkEVM/architecture/protocol/unified-LxLy/lxly-bridge.md) that allows users to move assets (both native and [ERC20](https://ethereum.org/en/developers/docs/standards/tokens/erc-20/) tokens) from L1 to the L2 and vice versa.
+Chains looking to run their own bridge infrastructure can choose to deploy a new instance of the [LxLy bridge](../../zkEVM/architecture/high-level/unified-LxLy/lxly-bridge.md) that allows users to move assets (both native and [ERC20](https://ethereum.org/en/developers/docs/standards/tokens/erc-20/) tokens) from L1 to the L2 and vice versa.
 
 Deploying an individual instance of the LxLy means interoperability with other L2 chains via the [AggLayer](../agglayer/overview.md) is not possible. To enable cross-chain interoperability (i.e. L2-to-L2 cross-chain transactions), chains can opt-in to the AggLayer and use the [unified bridge](../agglayer/unified-bridge.md).
 
@@ -31,5 +31,5 @@ This option is suited to chains that want a standard bridging experience and do
 ## Further reading
 
 - [Aggregated blockchains: A new thesis](https://polygon.technology/blog/aggregated-blockchains-a-new-thesis).
-- [LxLy bridge](../../zkEVM/architecture/protocol/unified-LxLy/lxly-bridge.md).
+- [LxLy bridge](../../zkEVM/architecture/high-level/unified-LxLy/lxly-bridge.md).
 - [Unified bridge Ooverview](../agglayer/unified-bridge.md).

docs/zkEVM/architecture/high-level/smart-contracts/exit-roots.md

@@ -71,7 +71,7 @@ uint8 private constant _LEAF_TYPE_ASSET = 0;
 uint8 private constant _LEAF_TYPE_MESSAGE = 1;
 ```
 
-Data in a leaf contains a Keccak256 hash of the metadata (ABI encoded metadata if any) and the following parameters (matched by publicly available transaction data as seen in the [bridge L1 to L2](bridging.md#l1-to-l2) documentation):
+Data in a leaf contains a Keccak256 hash of the metadata (ABI encoded metadata if any) and the following parameters (matched by publicly available transaction data as seen in the [bridge L1 to L2](../unified-LxLy/bridging.md#l1-to-l2) documentation):
 
 ```solidity
 _addLeaf(

docs/zkEVM/get-started/index.md

@@ -13,4 +13,4 @@ Users do not need any special toolings or wallets in order to build or interact
 Simply switch to the zkEVM RPC and start building on a network with a higher throughput and lower fees.
 
 !!!caution
-    Check the list of potential risks associated with the use of Polygon zkEVM in the [Disclosures](../troubleshooting/risk-disclosures.md) section.
+    Check the list of potential risks associated with the use of Polygon zkEVM in the [Disclosures](../get-started/risk-disclosures.md) section.

docs/zkEVM/get-started/quick-start.md

@@ -3,7 +3,7 @@ comments: true
 ---
 
 !!!caution
-    Check the list of potential risks associated with the use of Polygon zkEVM in the [Disclosures](../troubleshooting/risk-disclosures.md) section.
+    Check the list of potential risks associated with the use of Polygon zkEVM in the [Disclosures](../get-started/risk-disclosures.md) section.
 
 ## Connect to zkEVM mainnet or testnet