f s/evening/eventing/

Author: tnull

lightning-liquidity/README.md

@@ -12,7 +12,7 @@ from the incoming payment, i.e., no funds are required client-side to initiate t
 
 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.
 
-`LiquidityManager` uses an evening system to notify the user about important updates to the protocol flow. To this end, you will need to handle events emitted via one of the event handling methods provided by `LiquidityManager`, e.g., `LiquidityManager::next_event`.
+`LiquidityManager` uses an eventing system to notify the user about important updates to the protocol flow. To this end, you will need to handle events emitted via one of the event handling methods provided by `LiquidityManager`, e.g., `LiquidityManager::next_event`.
 
 [LSP specifications]: https://github.com/BitcoinAndLightningLayerSpecs/lsp
 [LSPS0]: https://github.com/BitcoinAndLightningLayerSpecs/lsp/tree/main/LSPS0

lightning-liquidity/src/lib.rs

@@ -24,7 +24,7 @@
 //! [`LiquidityManager::lsps2_service_handler`], to access the respective client-side or
 //! service-side handlers.
 //!
-//! [`LiquidityManager`] uses an evening system to notify the user about important updates to the
+//! [`LiquidityManager`] uses an eventing system to notify the user about important updates to the
 //! protocol flow. To this end, you will need to handle events emitted via one of the event
 //! handling methods provided by [`LiquidityManager`], e.g., [`LiquidityManager::next_event`].
 //!