From f132af1f3350813f185a2c5c1eaf31a659785fe5 Mon Sep 17 00:00:00 2001 From: str4d Date: Tue, 5 Sep 2023 15:54:15 +0100 Subject: [PATCH] Documentation fixes Co-authored-by: Daira Emma Hopwood --- zcash_client_sqlite/src/wallet/scanning.rs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/zcash_client_sqlite/src/wallet/scanning.rs b/zcash_client_sqlite/src/wallet/scanning.rs index 00632cfa8..640f6bf9b 100644 --- a/zcash_client_sqlite/src/wallet/scanning.rs +++ b/zcash_client_sqlite/src/wallet/scanning.rs @@ -810,13 +810,13 @@ pub(crate) fn update_chain_tip( // to the chain tip. However, it may be stable or unstable relative to // the prior chain tip, which we could determine by looking up the // prior chain tip height from the scan queue. For simplicity we merge - // these two cases together, and pretend that the max scanned block is - // always unstable relative to the prior chain tip. + // these two cases together, and proceed as though the max scanned + // block is unstable relative to the prior chain tip. // // To confirm its stability, prioritize the `VERIFY_LOOKAHEAD` blocks // above the max scanned height as `Verify`: // - // - We use `Verify` to ensure this connectivity check is performed, + // - We use `Verify` to ensure that a connectivity check is performed, // along with any required rewinds, before any `ChainTip` ranges // (from this or any prior `update_chain_tip` call) are scanned. //