From bf86febd802d1d57234df874ecc49dfb892c0cd6 Mon Sep 17 00:00:00 2001 From: ok300 <106775972+ok300@users.noreply.github.com> Date: Tue, 30 Apr 2024 14:56:39 +0200 Subject: [PATCH] Update wording in section title --- src/guide/communicating_fees.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guide/communicating_fees.md b/src/guide/communicating_fees.md index d754d995..09b93631 100644 --- a/src/guide/communicating_fees.md +++ b/src/guide/communicating_fees.md @@ -162,7 +162,7 @@ Here is how you can build this message: -### Receive onchain +### Receiving an on-chain transaction For receiving onchain, there is a minimum and a maximum amount the user can receive. The fees are made up of the same components as receiving a lightning payment. The user gets an onchain address from `receive_onchain`. There is no way to know ahead of time exactly the amount that will be received on this address, so it is recommended to show the user the receivable boundaries and the fees involved: