Apply suggestions from code review

Co-authored-by: hsutaiyu <51791408+hsutaiyu@users.noreply.github.com>

Author: EmpieichO

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

@@ -1,4 +1,4 @@
-An exit tree is a binary, append-only, sparse Merkle tree (SMT) whose leaf nodes store bridging data. The exit trees have a maximum depth of 32.
+An exit tree is a binary, append-only, sparse Merkle tree (SMT) with a maximum depth of 32, where leaf nodes store bridging data.
 
 The Merkle root of an exit tree is known as the exit tree root, and it is the fingerprint of all the information recorded in the exit tree's leaf nodes. 
 

docs/zkEVM/architecture/high-level/smart-contracts/sequencing.md

@@ -13,7 +13,7 @@ The diagram below shows the sequencing workflow for rollup (non-validium) stacks
 
 ![Polygon Solidity smart contract architecture](../../../../img/cdk/high-level-architecture/sequencing-flow.png)
 
-## `sequenceBatches()` function
+## `sequenceBatches()`
 
 The `sequenceBatches()` function is called on the `PolygonZkEVMEtrog.sol` contract:
 
@@ -49,7 +49,7 @@ Stepwise, the function does the following:
 1. Calls the `PolygonRollupManager.onSequenceBatches(...)` function which waits for an `OnSequenceBatches(...)` event callback.
 1. Emits `SequenceBatches(...)` event.
 
-## `onSequenceBatches()` function
+## `onSequenceBatches()`
 
 The `onSequenceBatches()` function is called on the `PolygonRollupManager.sol` contract:
 
@@ -67,7 +67,7 @@ Stepwise, the function does the following:
 1. Attempts to consolidate pending state for the rollup by updating `lastVerifiedBatch`, `batchNumToStateRoot[]`, and `lastLocalExitRoot` state variables, and also by updating `globalExitRootManager.updateExitRoot(L2sLocalExitRoot)`, after which it emits a `ConsolidatePendingState(...)` event.
 1. Emits an `OnSequenceBatches(...)` event back to the original `sequenceBatches(...)` call.
 
-## `sequenceBatchesValidium()` function
+## `sequenceBatchesValidium()`
 
 The `sequenceBatchesValidium()` function is called on the `PolygonValidiumEtrog.sol` contract:
 

docs/zkEVM/architecture/high-level/smart-contracts/verification.md

@@ -13,7 +13,7 @@ The sequence diagram below shows the verification workflow for rollup stacks and
 
 ![Polygon Solidity consensus verification flow](../../../../img/cdk/high-level-architecture/verification-flow.png)
 
-## `verifyBatchesTrustedAggregator()` function
+## `verifyBatchesTrustedAggregator()`
 
 The `verifyBatchesTrustedAggregator()` function is called on the `PolygonRollupManager` contract:
 

docs/zkEVM/architecture/high-level/unified-LxLy/bridging.md

@@ -93,7 +93,7 @@ The data below is transaction data (represented by a leaf node in an exit tree)
 
 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 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.
+2. The bridge contract transmits 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.
 

docs/zkEVM/architecture/index.md

@@ -69,7 +69,7 @@ The underlying protocol in zkEVM ensures that the state transitions are correct
 
 In order to ensure adherence to a set of pre-determined rules for state transitions, the consensus contract deployed on L1, is utilized.
 ​
-!!!info
+!!! info
     The consensus contract is currently deployed on both [Ethereum mainnet](https://etherscan.io/address/0x5132A183E9F3CB7C848b0AAC5Ae0c4f0491B7aB2) and [Cardona testnet](https://sepolia.etherscan.io/address/0xa997cfD539E703921fD1e3Cf25b4c241a27a4c7A).
 ​
 A smart contract verifies the validity proofs to ensure that each transition is completed correctly.