use the `images` folder for images

channel-construction.asciidoc

@@ -177,7 +177,7 @@ As Alice would loose access of her Bitcoins once she sends it to a 2-of-2 multis
 Thus before Alice publishes the funding transaction she will create another transaction that sends all the bitcoin from the 2-of-2 multisignature output back to an address which she controls.
 
 .The situation can be seen in the following picture
-image:channel-construction-opening-1.png[]
+image:images/channel-construction-opening-1.png[]
 Of course for the commitment transaction Alice would need to get a signature from Bob before she can safely broadcast the funding transaction.
 After publishing the funding transaction instead of braodcasting the commitment transaction she will keep it in a safe place.
 For this to work Alice needs to be sure that the funding transaction could not be published with a different transaction id.
@@ -207,7 +207,7 @@ Let us assume as an example that Alice wants to send 30k Satoshi to Bob.
 For now we can assume that through some communication protocol Alice and Bob would negotiate a double spent of the funding transaction output of 100k satoshi.
 The new commitment transaction for which Alice and Bob would exchange signatures would send 70k satoshi to Alice and 30k Satoshi to Bob.
 The situation can be seen in the following picture
-image:channel-construction-opening-2.png[]
+image:images/channel-construction-opening-2.png["A new balance in an insecure payment channel"]
 Whenever Alice and Bob want to change the balance of the payment channel they will negotiate a new commitment transaction.
 Effectively they double spend the funding transaction output.
 But as the commitment transactions are not broadcasted - as long as the channel stays open - they will be able to do that.