From: Matt Corallo <git@bluematt.me>
Date: Thu, 21 Sep 2023 20:21:13 +0000 (+0000)
Subject: Refer to an "outage" over a "timeout", for when failure happens
X-Git-Tag: v0.0.117-rc1~11^2~2
X-Git-Url: http://git.bitcoin.ninja/index.cgi?a=commitdiff_plain;ds=inline;h=974ba314a29fa35f2ed662b9357fa9cd701e444d;p=rust-lightning

Refer to an "outage" over a "timeout", for when failure happens

Timeouts may be worth retrying, but an outage is a more general
term which obviously cannot be retried.
---

diff --git a/lightning/src/chain/chainmonitor.rs b/lightning/src/chain/chainmonitor.rs
index a49b3b42..60d50bf0 100644
--- a/lightning/src/chain/chainmonitor.rs
+++ b/lightning/src/chain/chainmonitor.rs
@@ -98,7 +98,7 @@ impl MonitorUpdateId {
 ///    If at some point no further progress can be made towards persisting the pending updates, the
 ///    node should simply shut down.
 ///
-///  * If the persistence has failed and cannot be retried further (e.g. because of some timeout),
+///  * If the persistence has failed and cannot be retried further (e.g. because of an outage),
 ///    [`ChannelMonitorUpdateStatus::UnrecoverableError`] can be used, though this will result in
 ///    an immediate panic and future operations in LDK generally failing.
 ///