f - Rephrase update_best_block docs

Author: jkczyz

lightning/src/chain/chainmonitor.rs

@@ -96,7 +96,7 @@ where C::Target: chain::Filter,
 	///
 	/// Used instead of [`block_connected`] by clients that are notified of transactions rather than
 	/// blocks. May be called before or after [`update_best_block`] for transactions in the
-	/// corresponding block. See [`update_best_block`] for further calling expectations. 
+	/// corresponding block. See [`update_best_block`] for further calling expectations.
 	///
 	/// [`block_connected`]: Self::block_connected
 	/// [`update_best_block`]: Self::update_best_block
@@ -116,10 +116,9 @@ where C::Target: chain::Filter,
 	/// block.
 	///
 	/// Must be called after new blocks become available for the most recent block. Intermediary
-	/// blocks, however, may be safely skipped. For a chain reorganization, must either be:
-	/// * called at at the fork point and then again for the most recent block -- intermediary
-	///   blocks may be skipped as before -- or
-	/// * not called in favor of calling [`transaction_unconfirmed`] for any affected transactions.
+	/// blocks, however, may be safely skipped. In the event of a chain re-organization, this only
+	/// needs to be called for the most recent block assuming `transaction_unconfirmed` is called
+	/// for any affected transactions.
 	///
 	/// [`block_connected`]: Self::block_connected
 	/// [`transactions_confirmed`]: Self::transactions_confirmed