Merge pull request #2147 from OffchainLabs/fix-bridge-deposits-image

Fix bridge deposits image

Author: pete-vielhaber

arbitrum-docs/build-decentralized-apps/token-bridging/03-token-bridge-erc20.mdx

@@ -52,7 +52,7 @@ All Ethereum to Arbitrum token transfers are initiated via the router contract o
 
 Similarly, Arbitrum to Ethereum transfers are initiated via the router contract on L2, the `L2GatewayRouter` contract, which calls the token's gateway contract on L2, the `L2ArbitrumGateway` contract, which in turn communicates to its corresponding gateway contract on L1, the `L1ArbitrumGateway` contract (typically/expectedly via [sending L2-to-L1 messages to the outbox](/how-arbitrum-works/11-l2-to-l1-messaging.mdx)).
 
-<ImageZoom src="/img/dapps-bridge-withdrawals.png" alt="" className="img-600px" />
+<ImageZoom src="/img/dapps-bridge_withdrawals.png" alt="" className="img-600px" />
 
 For any given gateway pairing, we require that calls be initiated through the corresponding router (`L1GatewayRouter` or `L2GatewayRouter`), and that the gateways conform to the [TokenGateway](https://github.com/OffchainLabs/token-bridge-contracts/blob/main/contracts/tokenbridge/libraries/gateway/TokenGateway.sol) interfaces; the `TokenGateway` interfaces should be flexible and extensible enough to support any bridging functionality a particular token may require.