From c878cd8e1dae32df781c9e31bcd09f813aa64716 Mon Sep 17 00:00:00 2001
From: Matt Corallo <649246+TheBlueMatt@users.noreply.github.com>
Date: Mon, 17 Jan 2022 18:40:47 +0000
Subject: [PATCH] s/send a warning/warn the user/ in BOLT 5 to avoid confusion
 (#951)

Prior to the addition of `warning` messages, BOLT 5 specified a
few cases where users should be warned that funds may have been
lost. However, it used the phrasing "send a warning" which can now
be confused  with `warning` messages. Nodes should not generally
inform their counterparty that they have been robbed.
---
 05-onchain.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/05-onchain.md b/05-onchain.md
index 08cd27e..c324b17 100644
--- a/05-onchain.md
+++ b/05-onchain.md
@@ -361,7 +361,7 @@ A local node:
       - MUST handle HTLCs offered by the remote node as specified in
       [HTLC Output Handling: Remote Commitment, Remote Offers](#htlc-output-handling-remote-commitment-remote-offers)
     - otherwise (it is NOT able to handle the broadcast for some reason):
-      - MUST send a warning regarding lost funds.
+      - MUST inform the user of potentially lost funds.
 
 ## Rationale
 
@@ -625,7 +625,7 @@ A node:
   - upon discovering a transaction that spends a funding transaction output
   which does not fall into one of the above categories (mutual close, unilateral
   close, or revoked transaction close):
-    - MUST send a warning regarding lost funds.
+    - MUST warn the user of potentially lost funds.
       - Note: the existence of such a rogue transaction implies that its private
       key has leaked and that its funds may be lost as a result.
   - MAY simply monitor the contents of the most-work chain for transactions.