From b846f16e6ccf777a7e7e452bdc6faaa2a6fe2a2d Mon Sep 17 00:00:00 2001
From: dstrukt <gfxdsign@gmail.com>
Date: Mon, 6 Jun 2022 02:58:32 -0700
Subject: [PATCH] ui+pos: update notification copy (#3801)

---
 BTCPayServer/Views/UIApps/UpdatePointOfSale.cshtml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/BTCPayServer/Views/UIApps/UpdatePointOfSale.cshtml b/BTCPayServer/Views/UIApps/UpdatePointOfSale.cshtml
index f5c75c339..ced99e303 100644
--- a/BTCPayServer/Views/UIApps/UpdatePointOfSale.cshtml
+++ b/BTCPayServer/Views/UIApps/UpdatePointOfSale.cshtml
@@ -208,7 +208,7 @@
                                     <input asp-for="NotificationUrl" class="form-control" />
                                     <span asp-validation-for="NotificationUrl" class="text-danger"></span>
                                 </div>
-                                <p>A <code>POST</code> callback will be sent to notification with the following form will be sent to <code>notificationUrl</code> once the enough is paid and once again once there is enough confirmations to the payment:</p>
+                                <p>A <code>POST</code> callback will be sent to the specified <code>notificationUrl</code> (for on-chain transactions when there are sufficient confirmations):</p>
                                 <pre class="p-3">@Model.ExampleCallback</pre>
                                 <p><strong>Never</strong> trust anything but <code>id</code>, <strong>ignore</strong> the other fields completely, an attacker can spoof those, they are present only for backward compatibility reason:</p>
                                 <ul>