lint

Author: qbzzt

pages/interop/tutorials/message-passing/relay-with-cast.mdx

@@ -185,7 +185,7 @@ INNER_END_OF_FILE
 ACCESS_LIST=`cast rpc admin_getAccessListForIdentifier --rpc-url http://localhost:8420 "$RPC_PARAMS" | jq .accessList`
 ```
 
-To secure cross-chain messaging and prevent potential [denial of service attacks]((https://github.com/ethereum-optimism/design-docs/blob/main/protocol/interop-access-list.md)), relay transactions require properly formatted access lists that include a checksum derived from the message data.
+To secure cross-chain messaging and prevent potential [denial of service attacks](https://github.com/ethereum-optimism/design-docs/blob/main/protocol/interop-access-list.md), relay transactions require properly formatted access lists that include a checksum derived from the message data.
 This lets sequencers know what executing messages to expect in a transaction, which makes it easy not to include transactions that are invalid because they rely on messages that were never sent.
 
 The [algorithm to calculate the access list](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/CrossL2Inbox.sol#L87-L115) is a bit complicated, but you don't need to worry about it.