f fix overly aggressive sed

Author: TheBlueMatt

lightning/src/ln/monitor_tests.rs

@@ -89,9 +89,9 @@ fn chanmon_fail_from_stale_commitment() {
 
 #[test]
 fn chanmon_claim_value_coop_close() {
-	// Tests .unwrap().get_claimable_balances` returns the correct values across a simple cooperative claim.
+	// Tests `get_claimable_balances` returns the correct values across a simple cooperative claim.
 	// Specifically, this tests that the channel non-HTLC balances show up in
-	// .unwrap().get_claimable_balances` until the cooperative claims have confirmed and generated a
+	// `get_claimable_balances` until the cooperative claims have confirmed and generated a
 	// `SpendableOutputs` event, and no longer.
 	let chanmon_cfgs = create_chanmon_cfgs(2);
 	let node_cfgs = create_node_cfgs(2, &chanmon_cfgs);
@@ -186,9 +186,9 @@ fn sorted_vec<T: Ord>(mut v: Vec<T>) -> Vec<T> {
 }
 
 fn do_test_claim_value_force_close(prev_commitment_tx: bool) {
-	// Tests .unwrap().get_claimable_balances` with an HTLC across a force-close.
+	// Tests `get_claimable_balances` with an HTLC across a force-close.
 	// We build a channel with an HTLC pending, then force close the channel and check that the
-	// .unwrap().get_claimable_balances` return value is correct as transactions confirm on-chain.
+	// `get_claimable_balances` return value is correct as transactions confirm on-chain.
 	let mut chanmon_cfgs = create_chanmon_cfgs(2);
 	if prev_commitment_tx {
 		// We broadcast a second-to-latest commitment transaction, without providing the revocation
@@ -327,7 +327,7 @@ fn do_test_claim_value_force_close(prev_commitment_tx: bool) {
 
 	// Once the commitment transaction confirms, we will wait until ANTI_REORG_DELAY until we
 	// generate any `SpendableOutputs` events. Thus, the same balances will still be listed
-	// available in .unwrap().get_claimable_balances`. However, both will swap from `ClaimableOnClose` to
+	// available in `get_claimable_balances`. However, both will swap from `ClaimableOnClose` to
 	// other Balance variants, as close has already happened.
 	assert!(nodes[0].chain_monitor.chain_monitor.get_and_clear_pending_events().is_empty());
 	assert!(nodes[1].chain_monitor.chain_monitor.get_and_clear_pending_events().is_empty());