Fix typo and unecessary word

mimblewimble · Jul 16, 2019 · 2c77e05 · 2c77e05
1 parent 9d8bdea
commit 2c77e05
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/api/src/handlers/transactions_api.rs b/api/src/handlers/transactions_api.rs
@@ -54,15 +54,15 @@ impl TxHashSetHandler {
 		Ok(TxHashSetNode::get_last_n_output(w(&self.chain)?, distance))
 	}
 
-	// gets last n outputs inserted in to the tree
+	// gets last n rangeproofs inserted in to the tree
 	fn get_last_n_rangeproof(&self, distance: u64) -> Result<Vec<TxHashSetNode>, Error> {
 		Ok(TxHashSetNode::get_last_n_rangeproof(
 			w(&self.chain)?,
 			distance,
 		))
 	}
 
-	// gets last n outputs inserted in to the tree
+	// gets last n kernels inserted in to the tree
 	fn get_last_n_kernel(&self, distance: u64) -> Result<Vec<TxHashSetNode>, Error> {
 		Ok(TxHashSetNode::get_last_n_kernel(w(&self.chain)?, distance))
 	}

diff --git a/doc/coinbase_maturity.md b/doc/coinbase_maturity.md
@@ -110,7 +110,7 @@ If the hash stored in the output MMR covers both the commitment and the output f
 With this additional step we know if the output was a coinbase output or a regular transaction output based on the provided features.
 The hash will not match unless the features in the input match the original output features.
 
-For a regular non-coinbase output we are finished to explain. We know the output is currently spendable and we do not need to check the lock height.
+For a regular non-coinbase output we are finished. We know the output is currently spendable and we do not need to check the lock height.
 
 For a coinbase output we can proceed to verify the lock height and maturity. For this we need to identify the block where the output originated.
 We cannot determine the block itself, but we can require the input to specify the block (hash) and we can then prove this is actually correct based on the merkle roots in the block header (without needing full block data).