Address doc nits

We address some minor mistakes that made it into the docs before.

Author: tnull

lightning-liquidity/README.md

@@ -6,9 +6,11 @@ Currently the following specifications are supported:
 - [LSPS0] defines the transport protocol with the LSP over which the other protocols communicate.
 - [LSPS1] allows to order Lightning channels from an LSP. This is useful when the client needs
 inbound Lightning liquidity for which they are willing and able to pay in bitcoin.
-- [LSPS2] allows to generate a special invoice for which, when paid, an LSP will open a "just-in-time".
-This is useful for the initial on-boarding of clients as the channel opening fees are deducted
-from the incoming payment, i.e., no funds are required client-side to initiate this flow.
+- [LSPS2] allows to generate a special invoice for which, when paid, an LSP
+  will open a "just-in-time" channel. This is useful for the initial
+  on-boarding of clients as the channel opening fees are deducted from the
+  incoming payment, i.e., no funds are required client-side to initiate this
+  flow.
 
 To get started, you'll want to setup a `LiquidityManager` and configure it to be the `CustomMessageHandler` of your LDK node. You can then call `LiquidityManager::lsps1_client_handler` / `LiquidityManager::lsps2_client_handler`, or `LiquidityManager::lsps2_service_handler`, to access the respective client-side or service-side handlers.
 

lightning-liquidity/src/lib.rs

@@ -14,9 +14,10 @@
 //! - [LSPS0] defines the transport protocol with the LSP over which the other protocols communicate.
 //! - [LSPS1] allows to order Lightning channels from an LSP. This is useful when the client needs
 //! inbound Lightning liquidity for which they are willing and able to pay in bitcoin.
-//! - [LSPS2] allows to generate a special invoice for which, when paid, an LSP will open a "just-in-time".
-//! This is useful for the initial on-boarding of clients as the channel opening fees are deducted
-//! from the incoming payment, i.e., no funds are required client-side to initiate this flow.
+//! - [LSPS2] allows to generate a special invoice for which, when paid, an LSP will open a
+//! "just-in-time" channel. This is useful for the initial on-boarding of clients as the channel
+//! opening fees are deducted from the incoming payment, i.e., no funds are required client-side to
+//! initiate this flow.
 //!
 //! To get started, you'll want to setup a [`LiquidityManager`] and configure it to be the
 //! [`CustomMessageHandler`] of your LDK node. You can then for example call

lightning-liquidity/src/lsps0/client.rs

@@ -1,4 +1,4 @@
-//! Contains the main LSPS2 client-side object, [`LSPS0ClientHandler`].
+//! Contains the main LSPS0 client-side object, [`LSPS0ClientHandler`].
 //!
 //! Please refer to the [LSPS0
 //! specifcation](https://github.com/BitcoinAndLightningLayerSpecs/lsp/tree/main/LSPS0) for more

lightning-liquidity/src/lsps0/msgs.rs

@@ -1,4 +1,4 @@
-//! Message, request, and other primitive types used to implement LSPS1.
+//! Message, request, and other primitive types used to implement LSPS0.
 
 use crate::lsps0::ser::{LSPSMessage, RequestId, ResponseError};
 use crate::prelude::Vec;

lightning-liquidity/src/manager.rs

@@ -75,13 +75,18 @@ pub struct LiquidityClientConfig {
 /// Users need to continually poll [`LiquidityManager::get_and_clear_pending_events`] in order to surface
 /// [`Event`]'s that likely need to be handled.
 ///
-/// If configured, users must forward the [`Event::HTLCIntercepted`] event parameters to [`LSPS2ServiceHandler::htlc_intercepted`]
-/// and the [`Event::ChannelReady`] event parameters to [`LSPS2ServiceHandler::channel_ready`].
+/// If the LSPS2 service is configured, users must forward the following parameters from LDK events:
+/// - [`Event::HTLCIntercepted`] to [`LSPS2ServiceHandler::htlc_intercepted`]
+/// - [`Event::ChannelReady`] to [`LSPS2ServiceHandler::channel_ready`]
+/// - [`Event::HTLCHandlingFailed`] to [`LSPS2ServiceHandler::htlc_handling_failed`]
+/// - [`Event::PaymentForwarded`] to [`LSPS2ServiceHandler::payment_forwarded`]
 ///
 /// [`PeerManager`]: lightning::ln::peer_handler::PeerManager
 /// [`MessageHandler`]: lightning::ln::peer_handler::MessageHandler
 /// [`Event::HTLCIntercepted`]: lightning::events::Event::HTLCIntercepted
 /// [`Event::ChannelReady`]: lightning::events::Event::ChannelReady
+/// [`Event::HTLCHandlingFailed`]: lightning::events::Event::HTLCHandlingFailed
+/// [`Event::PaymentForwarded`]: lightning::events::Event::PaymentForwarded
 pub struct LiquidityManager<ES: Deref + Clone, CM: Deref + Clone, C: Deref + Clone>
 where
 	ES::Target: EntropySource,