maliciously (#253)

* maliciously

maliciously instead of malicously

* Update 03_how_ln_works.asciidoc

fixed another typo

Co-authored-by: Rene Pickhardt <rene@rene-pickhardt.de>

03_how_ln_works.asciidoc

@@ -524,10 +524,11 @@ It is important to understand that HTLCs have a time measured in absolute blockh
 Once the sender of a payment sends away the onion it is completely out if their control what happens.
 Honest nodes SHOULD either forward the onion as quickly as possible or send an error back the original.
 While sender expects nodes along the path to be honest it has according to the protocol no power of making sure that nodes act quickly.
-Thus payment can currently get stuck if nodes want to behave malicously. 
+
+
+Thus payments can currently get stuck if nodes want to behave maliciously. 
 While the likelihood for a payment to fail is pretty high if it does not settle quickly a node SHOULD never initiate another payment attempt along a different path before the onion returned with an error as a node might just have delayed the forwarding of the payment.
-Nodes which act malicously by delaying the forwarding of payments or errors are actually hard to detect due to the privacy properties that are gained with the onion routing scheme. 
-====
+Nodes which act maliciously by delaying the forwarding of payments or errors are actually hard to detect due to the privacy properties that are gained with the onion routing scheme. 
 
 
 === Missing bits