Merge branch 'master' into update-send

docs/FAQ/FAQ-UseWasabi.md

@@ -347,7 +347,8 @@ Wasabi uses [BIP 44 multi-account hierarchy for deterministic wallets](https://g
 
 ### How do I generate a new receiving address?
 
-You can generate a new bech32 address in the `Receive` dialog of Wasabi Wallet.
+You can generate a new address using the `Receive` button in the main view's top right corner.
+By default it returns a SegWit (bech32) address, the drop-down can be used to generate a Taproot (bech32m) address.
 First you must set a label for it, so that you later know who knows that this address is yours.
 Be precise in the label of the observers who know this address is yours, as this is an important part of good [coin selection](/why-wasabi/Coins.md) privacy best practices.
 Do not write anything else on the label exept the name of the entities that know this address belongs to you.
@@ -360,7 +361,9 @@ This is a good feature to help protect you against [address reuse](/why-wasabi/A
 ### Where can I find previously generated addresses?
 
 Generated addresses which haven't received any funds yet, are displayed at the `Addresses Awaiting Payment` list.
-Click on the `Receive` button > `Addresses Awaiting Payment`
+Click on the `Receive` button > `Addresses Awaiting Payment`. 
+
+SegWit and Taproot addresses are two different lists, use the receive button drop-down to see the desired type.
 
 ![Addresses Awaiting Payment](/AddressesAwaitingPayment.png "Addresses Awaiting Payment")
 

docs/using-wasabi/CoinJoin.md

@@ -68,7 +68,7 @@ Notice that it is not yet possible to coinjoin from a hardware wallet, the keys
 
 As of Wasabi version [2.2.0.0](https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.2.0.0), the Wasabi client will only participate in coinjoin rounds where it only pays for the mining fees for the blockspace it uses, like any other bitcoin transaction.
 
-> In rare cases the output decomposition contains change (maximum of 10 000 sats per coinjoin), this leftover goes to the coordinator. This is because creating such small amounts would harm privacy and end up being more expansive than just forfeiting it.
+> In rare cases the output decomposition contains change (maximum of 10 000 sats per coinjoin), this leftover goes to the coordinator. This is because creating such small amounts would harm privacy and ends up being more expensive than just forfeiting it.
 
 The coordinator sets the mining fee rate for the coinjoin transaction.
 

docs/using-wasabi/Send.md

@@ -67,13 +67,13 @@ For example, if you receive a coin from Alice, then the cluster is `Alice`.
 If you now send half of this coin to Bob, then the cluster of your change coin is `Alice, Bob`.
 The goal is to know the observers who know about your coins and try to reduce their number for each coin.
 
-## Receiving Address
+## Destination Address
 
 When sending bitcoin, you need to know the destination address of the receiver.
 This commits to the spending condition that the receiver agrees to have for this coin.
 The address can be a public key hash [starting with `1`], a script hash [starting with `3`], a native SegWit bech32 public key hash [starting with `bc1q`], or a Taproot bech32m public key [starting with `bc1p`].
 Make sure that you ask the receiver for a [new address](/why-wasabi/AddressReuse.md) for every payment to protect your privacy and theirs.
-Wasabi will calculate the checksum and notify you if the provided address is wrong.
+Wasabi will calculate the checksum and notify you if the provided address is wrong/contains a typo.
 
 ## Observers
 
@@ -100,7 +100,9 @@ So in order to increase your privacy, you can set a non-rounded amount, like `0.
 
 Every transaction must specify a fee which incentives the miner to include it in a block, it is calculated by `value of inputs - value of outputs`.
 The higher the fee per virtual byte (vByte) transaction size, the more likely miners are to confirm this transaction.
-Wasabi uses Bitcoin Core's `smart fee` algorithm to estimate the time it will take to confirm at the given fee level.
+
+Wasabi's fee estimation is based on Bitcoin Core's `smart fee` algorithm with some additions: it uses the mempool.space fee histogram to remove estimations that overpay, and Wasabi also makes sure to be included in the top 300 MB mempool to not be dropped from default Bitcoin Core mempools.
+
 You can change the fee by moving the slider, or by manually setting the [transaction fee rate](/FAQ/FAQ-UseWasabi.md#how-do-i-set-custom-fee-rate).
 
 ![Wasabi Wallet Fee Slider](/SendFeeSlider.png "Wasabi Wallet Fee Slider")