Apply suggestions from code review

Author: storopoli

docs/technical/bitcoin-bridge.md

@@ -65,13 +65,13 @@ who sends 10[^fees] BTC to a P2TR address, where:
     used to generate the pubkey by shifting the NUMS point.
 
 1. The script path spend has two paths:
-    1. "Deposit path", an $N$-of-$N$ multisig path,
-    where $N$ is the number of operators in the bridge.
-    1. "Take back" path,
-    which allows the user to take back their funds if the bridge fails to
-    move funds from the Deposit Request Transaction (DRT)
-    into the bridge address within approximately 8.5 hours,
-    i.e. it is time-locked and the user can spend it by providing a signature.
+   1. "Deposit path", an $N$-of-$N$ multisig path,
+      where $N$ is the number of operators in the bridge.
+   1. "Take back" path,
+      which allows the user to take back their funds if the bridge fails to
+      move funds from the Deposit Request Transaction (DRT)
+      into the bridge address within approximately 8.5 hours,
+      i.e. it is time-locked and the user can spend it by providing a signature.
 
 This transaction has some metadata attached to it, in the form of an `OP_RETURN`
 output, that can be up to 80 bytes long (according to bitcoin standardness policy),
@@ -125,7 +125,7 @@ The user requests a withdrawal on Strata and an operator is assigned to
 fulfill the request on bitcoin:
 
 1. The user initiates a withdrawal request, in response to which
-    the corresponding amount of strata BTC or `S-BTC` is burned from Strata.
+   the corresponding amount of strata BTC or `S-BTC` is burned from Strata.
 1. After the burn is confirmed, the assigned operator creates
    and signs a Withdrawal Transaction (WT) on the Bitcoin blockchain
    where they spend 10 BTC from the bridge address' UTXO set,