f test comments

Author: TheBlueMatt

lightning/src/ln/payment_tests.rs

@@ -2622,7 +2622,7 @@ fn test_simple_partial_retry() {
 #[cfg(feature = "std")]
 fn test_threaded_payment_retries() {
 	// In the first version of the in-`ChannelManager` payment retries, retries weren't limited to
-	// a single thread and would happily let multile threads run retries at the same time. Because
+	// a single thread and would happily let multiple threads run retries at the same time. Because
 	// retries are done by first calculating the amount we need to retry, then dropping the
 	// relevant lock, then actually sending, we would happily let multiple threads retry the same
 	// amount at the same time, overpaying our original HTLC!
@@ -2635,7 +2635,7 @@ fn test_threaded_payment_retries() {
 	// than 10% of the original value. Thus, we want all our retries to be below that. In order to
 	// keep things simple, we route one HTLC for 0.1% of the payment over channel 1 and the rest
 	// out over channel 3+4. This will let us ignore 99% of the payment value and deal with only
-	// out channel.
+	// our channel.
 	let chan_1_scid = create_announced_chan_between_nodes_with_value(&nodes, 0, 1, 10_000_000, 0).0.contents.short_channel_id;
 	create_announced_chan_between_nodes_with_value(&nodes, 1, 3, 10_000_000, 0);
 	let chan_3_scid = create_announced_chan_between_nodes_with_value(&nodes, 0, 2, 10_000_000, 0).0.contents.short_channel_id;
@@ -2703,7 +2703,7 @@ fn test_threaded_payment_retries() {
 	assert_eq!(send_msg_events.len(), 2);
 	send_msg_events.retain(|msg|
 		if let MessageSendEvent::UpdateHTLCs { node_id, .. } = msg {
-			// Drop the commitment update for noddes[2], we can just let that one sit pending
+			// Drop the commitment update for nodes[2], we can just let that one sit pending
 			// forever.
 			*node_id == nodes[1].node.get_our_node_id()
 		} else { panic!(); }