removing incorrect class diagrams

Author: kmurphypolygon

docs/img/cdk/high-level-architecture/bridging-class-diagram.png

@@ -1,5 +1,3 @@
-![Polygon Solidity smart contract bridging architecture](../../../../img/cdk/high-level-architecture/bridging-class-diagram.png)
-
 The unified bridge transfers assets and messages between networks (L1, L2) by calling bridge and claim functions on the [PolygonZkEVMBridgeV2.sol](https://github.com/0xPolygonHermez/zkevm-contracts/blob/main/contracts/v2/PolygonZkEVMBridgeV2.sol) contract whose deployment address is an [upgradeable proxy](https://etherscan.io/address/0x2a3DD3EB832aF982ec71669E178424b10Dca2EDe#code). Interaction with the actual contract happens via the proxy.
 
 This contract is deployed on L1 and there is also one deployed on every L2 network. It communicates closely with an exit root manager contract specific to L1 or L2.

docs/img/cdk/high-level-architecture/exit-root-class-diagram.png

@@ -1,7 +1,3 @@
-The class diagram below describes how the exit root contracts communicate with the bridge and the rollup manager.
-
-![Polygon Solidity smart contract bridging architecture](../../../../img/cdk/high-level-architecture/exit-root-class-diagram.png)
-
 An exit tree is a binary, append-only, sparse Merkle tree (SMT) whose leaf nodes store bridging data. The exit trees have a depth of 32.
 
 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/img/cdk/high-level-architecture/full-topology.png

@@ -6,10 +6,6 @@ comments: true
 
 Chain stacks at the node level direct transaction data to the L2 and L1 networks via smart contract calls. The system stores state in binary tree structures containing verifiable local and global exit roots.
 
-The diagram below details the Polygon Solidity smart contract architecture minus the bridging contracts. 
-
-![Polygon Solidity smart contract architecture](../../../../img/cdk/high-level-architecture/smart-contracts-full-view.png)
-
 There are four key contract types built into the system design: 
 
 - The [consensus contract set](#consensus-contracts). 
@@ -37,10 +33,6 @@ The [PolygonRollupManager.sol](https://github.com/0xPolygonHermez/zkevm-contract
 
 ## Bridge 
 
-The class diagram below describes the unified bridge interactions.
-
-![Polygon Solidity smart contract bridging architecture](../../../../img/cdk/high-level-architecture/bridging-class-diagram.png)
-
 The unified bridge contract [PolygonZkEVMBridgeV2.sol](https://github.com/0xPolygonHermez/zkevm-contracts/blob/main/contracts/v2/PolygonZkEVMBridgeV2.sol) is responsible for bridging and claiming activity across L1 and L2 chains. 
 
 <center>
@@ -51,10 +43,6 @@ In the L1 network, the bridge also manages the complex exit root mechanism gover
 
 ## Global exit roots
 
-The class diagram below describes the exit root interactions.
-
-![Polygon Solidity smart contract bridging architecture](../../../../img/cdk/high-level-architecture/exit-root-class-diagram.png)
-
 System state as a whole is stored on binary trees with data and/or exit roots written into their leaves. 
 
 Local updates at the leaf-level trigger exit root updates at the top of the trees which are then available to the global exit root trees and the consensus contracts via the L1 bridge contract.

docs/img/cdk/high-level-architecture/smart-contracts-full-view.png

@@ -109,8 +109,8 @@ nav:
               - Start services: zkEVM/get-started/setup-nodes/deploy-zkevm/start-services.md
           - Sync state with snapshots: zkEVM/get-started/state-sync-snapshots.md
         - Historical data: zkEVM/get-started/historical-data.md
-      - Architecture high-level:
-        - Overview: zkEVM/architecture/high-level/overview.md
+      - Architecture:
+        - Architecture: zkEVM/architecture/index.md
         - Smart contracts: 
           - Overview: zkEVM/architecture/high-level/smart-contracts/overview.md
           - Main contracts: zkEVM/architecture/high-level/smart-contracts/main-contracts.md
@@ -148,8 +148,6 @@ nav:
             - Utils:
               - ClaimCompressor.sol:  zkEVM/architecture/high-level/smart-contracts/api/utils/ClaimCompressor.md
           - Addresses: zkEVM/architecture/high-level/smart-contracts/addresses.md
-      - Architecture low-level:
-        - Architecture: zkEVM/architecture/index.md
         - zkEVM protocol:
           - zkEVM protocol: zkEVM/architecture/protocol/index.md
           - zkNode: zkEVM/architecture/zknode/index.md