fix(specs): line length

specs/deposits.md

@@ -118,7 +118,8 @@ Although we define only one new transaction type, we can distinguish between two
 transactions, based on their positioning in the L2 block:
 
 1. The first transaction MUST be a [L1 attributes deposited transaction][l1-attr-deposit], followed by
-2. an array of zero-or-more [user-deposited transactions][user-deposited] submitted to the deposit
+2. an array of zero-or-more [user-deposited transactions][user-deposited] 
+   submitted to the deposit
    feed contract on L1 (called `OptimismPortal`). User-deposited transactions are only present in the first block of a L2 epoch.
 
 We only define a single new transaction type in order to minimize modifications to L1 client
@@ -320,7 +321,8 @@ generated by the [L2 Chain Derivation][g-derivation] process. The content of eac
 transaction are determined by the corresponding `TransactionDeposited` event emitted by the
 [deposit contract][deposit-contract] on L1.
 
-1. `from` is unchanged from the emitted value (though it may have been transformed to an alias in `OptimismPortal`, the deposit feed contract).
+1. `from` is unchanged from the emitted value (though it may 
+   have been transformed to an alias in `OptimismPortal`, the deposit feed contract).
 2. `to` is any 20-byte address (including the zero address)
     - In case of a contract creation (cf. `isCreation`), this address is set to `null`.
 3. `mint` is set to the emitted value.