From f802e98e73bc4e42dd70e58069652703ce6094e4 Mon Sep 17 00:00:00 2001
From: Christian Decker <decker.christian@gmail.com>
Date: Sat, 12 Aug 2017 12:08:11 +0200
Subject: [PATCH] doc: Fix sendpay instructions

They were telling people to use the `<amount>`, but that's encoded in
the route already. Instead the final parameter is the `<rhash>` which
is the only piece of information missing for the transfer.

Reported-by: Toshiro Takahashi @toshirot
Signed-off-by: Christian Decker <decker.christian@gmail.com>
---
 README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index d0897a129..2a60a670d 100644
--- a/README.md
+++ b/README.md
@@ -97,11 +97,12 @@ daemon/lightning-cli invoice <amount> <label>
 This returns a random value called `rhash` that is part of the invoice.
 The recipient needs to communicate its ID `<recipient_id>`, `<rhash>` and the desired `<amount>` to the sender.
 
-The sender needs to compute a route to the recipient, and use that route to actually send the payment:
+The sender needs to compute a route to the recipient, and use that route to actually send the payment.
+The route contains the path that the payment will take throught the Lightning Network and the respective funds that each node will forward.
 
 ```
 route=$(daemon/lightning-cli getroute <recipient_id> <amount> 1 | jq --raw-output .route -)
-daemon/lightning-cli sendpay $route <amount>
+daemon/lightning-cli sendpay $route <rhash>
 ```
 
 Notice that in the first step we stored the route in a variable and reused it in the second step.