From f9f44fc592c1407b836ea94ced6a6a829e48a77b Mon Sep 17 00:00:00 2001
From: Quentin <125748180+quentintaranpino@users.noreply.github.com>
Date: Wed, 20 Nov 2024 16:32:04 +0100
Subject: [PATCH] Update buds/07.md

Co-authored-by: hzrd149 <8001706+hzrd149@users.noreply.github.com>
---
 buds/07.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/buds/07.md b/buds/07.md
index c414721..bb07c09 100644
--- a/buds/07.md
+++ b/buds/07.md
@@ -62,7 +62,7 @@ X-Lightning: lnbc30n1pnnmw3lpp57727jjq8zxctahfavqacymellq56l70f7lwfkmhxfjva6dgul
 
 Clients MUST parse and validate all available `X-{payment_method}` headers received from the server. The client SHOULD provide a way for the user to complete the payment and retry the request using the same `X-{payment_method}` header.
 
-The client MUST provide the payment proof in the request headers using the same `X-{payment_method}` header that was chosen. The payment proof MUST aling with the payment method specification:
+The client MUST provide the payment proof when re-trying the request using the same `X-{payment_method}` header that was chosen. The payment proof MUST align with the payment method specification:
 
 - For cashu the payment proof should be a serialized cashu token according to [NUT-00](https://github.com/cashubtc/nuts/blob/main/00.md#v4-tokens).
 - For lightning the payment proof should be the preimage of the payment request according to [BOLT-11](https://github.com/lightning/bolts/blob/master/11-payment-encoding.md).