Merge pull request bitcoin#1776 from craigraw/wallet-labels-edits

BIP329: PR 1750 follow-up edits

bip-0329.mediawiki

@@ -150,7 +150,7 @@ but should be given if they are readily available.
 
 === Transactions ===
 
-* <tt>height</tt>: An integer giving the block height where this fully confirmed transaction can be found. For transactions that are confirmed by less than 6 blocks, omit this field or provide a value of zero.  (Background: Until it is fully confirmed, the "height" of a transaction is in flux and may vary due to chain reorgs. However, the consumer of the labels, may not know the current block height, so it cannot know if the height is "real" (firm, fixed) or just transitory, so it's important not to include the height unless the generating wallet considers the transaction to be confirmed.)
+* <tt>height</tt>: An integer giving the block height where this fully confirmed transaction can be found. For transactions that are confirmed by less than 6 blocks, omit this field or provide a value of zero.  (Background: Until it is fully confirmed, the "height" of a transaction is in flux and may vary due to chain reorgs. However, the consumer of the labels, may not know the current block height, so it cannot know if the height is "real" (firm, fixed) or just transitory. Therefore, it is important to omit the height unless the generating wallet considers the transaction to be confirmed.)
 
 * <tt>time</tt>: ISO-8601 formatted timestamp of the block given by the "height" field, preferably in UTC, although ISO-8601 can represent local times. Example: <tt>2025-01-23T11:40:35Z</tt>.
 
@@ -174,14 +174,14 @@ but should be given if they are readily available.
 
 === Address ===
 
-* <tt>heights</tt>: a list of block heights that contain any activity related to this address, include outputs that deposit to the address, and transactions that spend UTXO of this address. An empty array indicates the address is unused.
+* <tt>heights</tt>: a list of block heights that contain any activity related to this address, include outputs that deposit to the address, and transactions that spend UTXOs of this address. Omit heights for transactions that are not fully confirmed. An empty array indicates the address is unused for confirmed transactions.
 
 == Comment on Types in JSON ==
 
 JSON can serialize a number of basic types, including string, integer
 and boolean (true/false).  Decimal values (<tt>123.45</tt>) can
 also be serialized, but some parsing libraries may interpret them as floating
-point values which is generally not what we want in financial applications.
+point values, which is generally not what we want in financial applications.
 When hand-crafting JSON data, be careful not to write <tt>"false"</tt> (with quotes),
 since that is a string with 5 characters and not a boolean.