fix: md linter

Author: 0xng

specs/protocol/bridges.md

@@ -55,7 +55,11 @@ domain to be able to deposit tokens to that domain. One of these tokens can be
 deployed using the `OptimismMintableERC20Factory` contract.
 
 ## ERC20 Unlocking
-The `ERC20Unlocked` function is used to unlock tokens stuck due to failure in relaying prior ERC20 bridging actions. A `messageHash` must exist in the `ROLLBACK_INBOX` contract to certify the message hash corresponding to an ERC20 bridging action started from the standard bridged failed on the other domain.
+
+The `ERC20Unlocked` function is used to unlock tokens stuck due to failure in
+relaying prior ERC20 bridging actions. A `messageHash` must exist in the `ROLLBACK_INBOX`
+contract to certify the message hash corresponding to an ERC20 bridging action started
+from the standard bridged failed on the other domain.
 
 ## Upgradability
 

specs/protocol/messengers.md

@@ -85,7 +85,14 @@ on the OptimismPortal, which calls `relayMessage` on the
 `L1CrossDomainMessenger` to finalize the withdrawal.
 
 ## Rolling a Message Back
-The `sendHashToRollbackInbox` function is used to send the hashes of failed and unsuccesful messages to the `ROLLBACK_INBOX` contract on the other domain after a given delay, ensuring the message corresponding to the rolled back hash is never processed in the current domain. The main purpose of this function is to inform the other domain of failed messages so contracts living in this other domain can handle the message failure. This allows functionalities such as unlocking stuck ERC20s.
+
+The `sendHashToRollbackInbox` function is used to send the hashes of failed
+and unsuccesful messages to the `ROLLBACK_INBOX` contract on the other domain
+after a given delay, ensuring the message corresponding to the rolled back hash
+is never processed in the current domain. The main purpose of this function
+is to inform the other domain of failed messages so contracts living in
+this other domain can handle the message failure. This allows functionalities
+such as unlocking stuck ERC20s.
 
 ## Upgradability
 

specs/protocol/rollback-inboxes.md

@@ -12,7 +12,10 @@
 
 ## Overview
 
-The rollback inbox contracts are responsible for storing the hashes of messages that failed on the other domain. They are built with the purpose of allowing contracts on the same domain to have the capability of handling what actions to perform when a message failed on the other domain and was rolled-back to it's origin domain.
+The rollback inbox contracts are responsible for storing the hashes of messages
+that failed on the other domain. They are built with the purpose of allowing contracts
+on the same domain to have the capability of handling what actions to perform when a
+message failed on the other domain and was rolled-back to it's origin domain.
 
 The `L2RollbackInbox` is a predeploy contract located at TO BE DEFINED.
 
@@ -29,7 +32,9 @@ interface RollbackInbox {
 
 ## Message Hash Reception
 
-The `receiveMessageHash` function is used to receive message hashes from the other domain. It must ensure the caller is the `CrossDomainMessenger` from this domain, and that the sender is the `CrossDomainMessenger` from the other domain.
+The `receiveMessageHash` function is used to receive message hashes from the other domain.
+It must ensure the caller is the `CrossDomainMessenger` from this domain, and that the
+sender is the `CrossDomainMessenger` from the other domain.
 
 ## Upgradability