update deleted unused docs

Author: EmpieichO

docs/zkEVM/architecture/architecture.md

@@ -159,7 +159,7 @@ Before getting into a transaction flow in L2, users need some funds to perform a
    - Aggregator will take pending transactions to be verified and build a Proof in order to achieve finality on L1
    - Once the Proof is validated, user's transactions will attain L1 finality (important for withdrawals). This is called the **consolidated state**.
 
-The above process is a summarized version of how transactions are processed in zkEVM. We recommend you to take a look at the complete [transaction life cycle](../protocol/l2-transaction-cycle-intro.md) document.
+The above process is a summarized version of how transactions are processed in zkEVM. We recommend you to take a look at the complete [transaction life cycle](../protocol/submit-transaction.md) document.
 
 ## Design characteristics
 

docs/zkEVM/bridge-to-zkevm.md

@@ -5,12 +5,11 @@
 
 Users can deposit assets from Ethereum and transact off-chain on Polygon zkEVM. For moving assets across chains (L1 ↔ zkEVM), you will need to use the zkEVM Bridge. The bridge interface is available for both Mainnet Beta and Testnet in the [Polygon Wallet Suite](https://wallet.polygon.technology/zkEVM/bridge). 
 
-<!-- Also, bridging can be done with the help of [MaticJS](/docs/develop/ethereum-polygon/matic-js/zkevm/initialize-zkevm/) SDK. -->
 
 The next video is a guide on how to bridge tokens from L1 to the zkEVM Testnet. The same video applies to the zkEVM Mainnet.
 
 <video loop width="100%" height="100%" controls="true" >
-  <source type="video/mp4" src="../img/zkvm/zkevmwallettestnet.mp4"></source>
+  <source type="video/mp4" src="../../img/zkvm/zkevmwallettestnet.mp4"></source>
   <p>Your browser does not support the video element.</p>
 </video>
 

docs/zkEVM/connect-wallet.md

@@ -16,7 +16,7 @@ Navigate to `Add network` in your wallet, and enter the respective network detai
 Here is a video tutorial on **how to add Polygon zkEVM Testnet to MetaMask and deploy smart contracts**:
 
 <video loop width="100%" height="100%" controls="true" >
-  <source type="video/mp4" src="../img/zkvm/tutorial.mp4"></source>
+  <source type="video/mp4" src="../../img/zkvm/tutorial.mp4"></source>
   <p>Your browser does not support the video element.</p>
 </video>
 

docs/zkEVM/protocol/batch-aggregation.md

@@ -1,7 +1,7 @@
 
 !!!info
 
-This document is a continuation in the series of articles explaining the [<ins>Transaction Life Cycle</ins>](l2-transaction-cycle-intro.md) inside Polygon zkEVM.
+This document is a continuation in the series of articles explaining the [<ins>Transaction Life Cycle</ins>](submit-transaction.md) inside Polygon zkEVM.
 
 The **Trusted Aggregator should eventually aggregate the sequences of batches previously committed by the Trusted Sequencer in order to achieve the L2 State final stage**, which is the Consolidated State.
 

docs/zkEVM/protocol/flow-of-assets.md

@@ -41,7 +41,7 @@ Consider now the case where a user commits to bridging some assets from L2 to L1
 
     For example, the interaction between the Consensus Contract and the Sequencer is omitted in the figure.
 
-    For a more wholistic view of the interaction between the Consensus Contract and the Sequencer, the reader is referred to earlier subsections of this documentation, specifically on the [<ins>Consensus Contract</ins>](/zkevm/architecture.md#consensus-contract).
+    For a more wholistic view of the interaction between the Consensus Contract and the Sequencer, the reader is referred to earlier subsections of this documentation, specifically on the [<ins>Consensus Contract</ins>](../architecture/architecture.md).
 
 
 ![A end-to-end flow of assets between L1 and L2](../../img/zkvm/06pzb-complete-asset-flow-l1-l2.png)

…M/protocol/l2-transaction-cycle-intro.md docs/zkEVM/protocol/submit-transaction.mddocs/zkEVM/protocol/l2-transaction-cycle-intro.md renamed to docs/zkEVM/protocol/submit-transaction.md docs/zkEVM/protocol/l2-transaction-cycle-intro.md renamed to docs/zkEVM/protocol/submit-transaction.md

@@ -1,6 +1,6 @@
 
 !!!info
-    This document is a continuation in the series of articles explaining the [<ins>Transaction Life Cycle</ins>](l2-transaction-cycle-intro.md) inside Polygon zkEVM.
+    This document is a continuation in the series of articles explaining the [<ins>Transaction Life Cycle</ins>](submit-transaction.md) inside Polygon zkEVM.
 
 
 The **Trusted Sequencer** must batch the transactions using the following `BatchData` struct specified in the `PolygonZkEVM.sol` contract:

docs/zkEVM/protocol/submit-trasaction.md

@@ -1,6 +1,6 @@
 
 !!!info
-    This document is a continuation in the series of articles explaining the [<ins>Transaction Life Cycle</ins>](l2-transaction-cycle-intro.md) inside Polygon zkEVM.
+    This document is a continuation in the series of articles explaining the [<ins>Transaction Life Cycle</ins>](submit-transaction.md) inside Polygon zkEVM.
 
 The **Trusted Sequencer reads transactions from the pool** and decides whether to **discard** them or **order and execute** them. Transactions that have been executed are added to a transaction batch, and the Sequencer's local L2 State is updated.
 

docs/zkEVM/protocol/transaction-batching.md

@@ -5,12 +5,9 @@ This document provides a comprehensive list of differences between the Ethereum
 
     Note that the following differences have no impact on the developer experience with the zkEVM as compared to the EVM. Gas optimization techniques, interacting with libraries like Web3.js and Ethers.js, and deploying contracts works seamlessly on the zkEVM without any overhead.
 
-    To start deploying your own smart contracts on the zKEVM, check out the [<ins>deployment guide</ins>](/zkevm/develop.md).
-
-
 ## Opcodes
 
-This section lists out the changes we have done with Opcodes in zKEVM as compared to the EVM.
+This section lists the changes we have done with Opcodes in zKEVM as compared to the EVM.
 
 - **SELFDESTRUCT** &rarr; removed and replaced by **SENDALL**.