cleanup

- fixing image sizing on l2-to-l1-messaging
- fixing unrelated broken link that has popped up

Author: pete-vielhaber

arbitrum-docs/how-arbitrum-works/11-l2-to-l1-messaging.mdx

@@ -103,7 +103,7 @@ The following diagram depicts the process that funds follow during a withdrawal
 <ImageZoom
   src="/img/dapps-withdrawing-ether.svg"
   alt="Process funds follow during withdrawal operation"
-  className="img-600px"
+  className="img-800px"
 />
 
 ## `ERC-20` token withdrawal
@@ -117,7 +117,7 @@ Arbitrum has a canonical <a data-quicklook-from="bridge">bridge</a> design and a
 <ImageZoom
   src="/img/dapps-bridge_withdrawals.png"
   alt="Withdrawal process using the gateway"
-  className="img-600px"
+  className="img-800px"
 />
 
 For any given gateway pairing, calls have to be initiated through the corresponding router (`L2GatewayRouter`), and the gateways must conform to the `TokenGateway` interfaces; the `TokenGateway` interfaces should be flexible and extensible enough to support any bridging functionality a particular token may require.

arbitrum-docs/node-running/how-tos/running-an-orbit-node.mdx

@@ -89,7 +89,7 @@ And, you need to set the following flag to specify the DAS REST endpoints, there
 
 Please contact the chain owners to get the URL of the DAS REST endpoints. If you are a chain owner, please refer to the [DAC setup guide](/run-arbitrum-node/data-availability-committees/01-get-started.mdx#if-you-are-a-chain-owner) to set it up.
 
-(Batch posters only) For your batch posters to post data to the DAS, you need to follow [step 3 of config das](/run-arbitrum-node/data-availability-committees/04-configure-dac.mdx#Step-3:-Craft-the-new-configuration-for-the-batch-poster) to your node config.
+(Batch posters only) For your batch posters to post data to the DAS, you need to follow [step 3 of config das](/run-arbitrum-node/data-availability-committees/04-configure-dac.mdx#step-3-craft-the-new-configuration-for-the-batch-poster) to your node config.
 
 ### 3.Important ports