Update docs/liquid/liquid-part1.md

docs/liquid/liquid-part1.md

@@ -104,12 +104,14 @@ Now let's peg-in some bitcoin in order to receive L-BTC within our Liquid wallet
   - `$ sudo ./scripts/app compose bitcoin exec bitcoind bitcoin-cli getrawtransaction $B_TRANSID`
      
      020000000173f50....
+
 * Save that output to bash variable
   - `$ export B_RAWTRANS='020000000173f50....`
 * On your BITCOIN node, get output proof
   - `$ sudo ./scripts/app compose bitcoin exec bitcoind bitcoin-cli gettxoutproof '["<transaction_id_paste>"]'`
      
      00406426ea774aff7437de482c73f2ac8......
+
 * Save output proof in bash variable
   - `$ export B_OUTPROOF='00406426ea774aff7437de482c73f2ac8....'`
 * Now back on the elements node, we can claim the L-BTC
@@ -125,7 +127,7 @@ Now let's peg-in some bitcoin in order to receive L-BTC within our Liquid wallet
   - `$ sudo ./scripts/app compose elements exec node elements-cli -rpcuser=$E_RPCUSER -rpcpassword=$E_RPCPASS getwalletinfo`
 
     "balance": {
-    "bitcoin": 0.00149952}
+    "bitcoin": 0.00149952}[^6]
 
 ## Wrap Up and Preview for Part II. 
 
@@ -136,10 +138,16 @@ In Part II is where the fun begins, we will issue Assets, get the assets in the
 
 **Footnotes:**
 [^1]: As of 1-21-2024. There are 66 members who can perform other functions on network, but only Functionaries can sign
+
 [^2]: RAM usage is higher for Liquid than for BTC alone due to Confidential Transactions processing
+
 [^3]: It may be possible to run the `elements-cli` command without installing it separately, however I could not find it in the container. Anyway, the download of elements node is quite small and it communicates via localport on Umbrel, so this works fine.
+
 [^4]: Requires 102 confirmations on BTC side. Services like sideswap will release after 2 confs for small amounts  
+
 [^5]: Balance less the 48sat transaction fee
 
+[^6]: yes, the label is still called 'bitcoin' but can be changed if that annoys you :)
+