From 7a0acf951df2d63016879aa9a13dde15cefd371a Mon Sep 17 00:00:00 2001
From: Jeffrey Czyz <jkczyz@gmail.com>
Date: Mon, 8 Mar 2021 00:09:58 -0800
Subject: [PATCH] Fix misspelling of 'occurred' in public interface

---
 lightning/src/ln/peer_handler.rs | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/lightning/src/ln/peer_handler.rs b/lightning/src/ln/peer_handler.rs
index db8bb429..03470588 100644
--- a/lightning/src/ln/peer_handler.rs
+++ b/lightning/src/ln/peer_handler.rs
@@ -1345,7 +1345,7 @@ impl<Descriptor: SocketDescriptor, CM: Deref, RM: Deref, L: Deref> PeerManager<D
 	/// It will send pings to each peer and disconnect those which did not respond to the last round of pings.
 
 	/// Will most likely call send_data on all of the registered descriptors, thus, be very careful with reentrancy issues!
-	pub fn timer_tick_occured(&self) {
+	pub fn timer_tick_occurred(&self) {
 		let mut peers_lock = self.peers.lock().unwrap();
 		{
 			let peers = &mut *peers_lock;
@@ -1518,11 +1518,11 @@ mod tests {
 		assert_eq!(peers[0].peers.lock().unwrap().peers.len(), 1);
 
 		// peers[0] awaiting_pong is set to true, but the Peer is still connected
-		peers[0].timer_tick_occured();
+		peers[0].timer_tick_occurred();
 		assert_eq!(peers[0].peers.lock().unwrap().peers.len(), 1);
 
-		// Since timer_tick_occured() is called again when awaiting_pong is true, all Peers are disconnected
-		peers[0].timer_tick_occured();
+		// Since timer_tick_occurred() is called again when awaiting_pong is true, all Peers are disconnected
+		peers[0].timer_tick_occurred();
 		assert_eq!(peers[0].peers.lock().unwrap().peers.len(), 0);
 	}
 
-- 
2.30.2