Fixin asciidoc errors

04_node_client.asciidoc

@@ -51,14 +51,14 @@ Alternatively, you can use the +git+ command to create a version-controlled clon
 
 To make a local copy of the repository on your computer, run the git command as follows:
 
-[git-clone-lnbook]
+[[git-clone-lnbook]]
 ----
 $ git clone https://github.com/lnbook/lnbook.git
 ----
 
 You now have a complete copy of the book repository in a folder called +lnbook+. You will want to change to the newly downloaded directory by running:
 
-[cd-lnbook]
+[[cd-lnbook]]
 ----
 $ cd lnbook
 ----
@@ -77,12 +77,12 @@ The installation of use of Docker and its commands is detailed in <<appendix_doc
 
 You can find the latest container definitions and build configurations in the book's repository under the +code/docker+ folder. Each container is in a separate folder as can be seen below:
 
-[tree]
+[[tree]]
 ----
 $ tree -F --charset=asciii code/docker
 ----
 
-[docker-dir-list]
+[[docker-dir-list]]
 ----
 code/docker
 |-- bitcoind/

05_node_operations.asciidoc

@@ -941,19 +941,23 @@ The unit of _millionths_ is often abbreviated with _ppm_ (parts per million).
 For example, a _base fee_ of 1,000 (millisatoshi) and a _fee rate_ of 1,000 ppm (millionths) would result in the following charges for a 100,000 satoshi payment:
 
 [latexmath]
-====
-P = 100,000 satoshi
+++++
+\begin{equation}
+\begin{aligned}
+P = 100,000 satoshi \\
 
-F_base = 1,000 millisatoshi = 1 satoshi
+F_base = 1,000 millisatoshi = 1 satoshi \\
 
-F_rate = 1,000 ppm = 1,000/1,000,000 = 1/1,000 = 0.001 = 0.1%
+F_rate = 1,000 ppm = 1,000/1,000,000 = 1/1,000 = 0.001 = 0.1% \\
 
-F_total = F_base + ( P * F_rate )
+F_total = F_base + ( P * F_rate ) \\
 
- \Rightarrow  F_total = 1 satoshi + ( 100,000/1,000 ) satoshi
+ \Rightarrow  F_total = 1 satoshi + ( 100,000/1,000 ) satoshi \\
 
- \Rightarrow  F_total = 1 satoshi + 100 satoshi = 101 satoshi
-====
+ \Rightarrow  F_total = 1 satoshi + 100 satoshi = 101 satoshi \\
+\end{aligned}
+\end{equation}
+++++
 
 Broadly speaking, you can take one of two approaches to routing fees. You can route lots of payments with low fees, making up for low fees by high volume. Alternatively, you can choose to charge higher fees. If you choose to set higher fees, your node will be selected only when other cheaper routes don't exist. Therefore, you will route less frequently but earn more per successful routing.
 

08_routing_htlcs.asciidoc

@@ -354,7 +354,7 @@ Let's see how we would implement this as an HTLC in Bitcoin Script. In <<receive
 
 [[received_htlc]]
 .HTLC implemented in Bitcoin Script (BOLT3)
-[source,linenum]
+[source,text,linenums]
 ----
 # To remote node with revocation key
 OP_DUP OP_HASH160 <RIPEMD160(SHA256(revocationpubkey))> OP_EQUAL

09_channel_operation.asciidoc

@@ -93,10 +93,11 @@ The received information is enough for Bob to create a new commitment transactio
 
 We've already seen the basic structure of an HTLC in <<routing>>. The complete script of an offered HTLC is defined in https://github.com/lightningnetwork/lightning-rfc/blob/master/03-transactions.md#offered-htlc-outputs[BOLT #3 - Transactions - Offered HTLC output] and is shown in <<offered_htlc_output_script>> below:
 
-[source,linenum]
+
 [[offered_htlc_output_script]]
 .Offered HTLC output script:
 ====
+[source,text,linenums]
 ----
 # Revocation <1>
 OP_DUP OP_HASH160 <RIPEMD160(SHA256(revocationpubkey))> OP_EQUAL