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

Co-authored-by: Gaël Blanchemain <[email protected]>

Author: pete-vielhaber

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

@@ -121,7 +121,7 @@ Arbitrum has a canonical <a data-quicklook-from="bridge">bridge</a> design and a
   className="img-600px"
 />
 
-For any given gateway pairing, we require initiation of calls through the corresponding router (`L2GatewayRouter`) and that the gateways conform to the [TokenGateway] interfaces; the `TokenGateway` interfaces should be flexible and extensible enough to support any bridging functionality a particular token may require.
+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.
 
 Token withdrawals are the most common usage of child-to-parent chain messaging. The standard withdrawal process follows (for standard gateway):