diff --git a/_compress_images_cache.yml b/_compress_images_cache.yml
index 1fae1ad90..7167934c9 100644
--- a/_compress_images_cache.yml
+++ b/_compress_images_cache.yml
@@ -714,3 +714,31 @@ assets/images/guide/private-key-management/backups/paperbackup.jpg: paperbackup.
assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg: multiple-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/cloud-backup.jpg: cloud-backup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg: multiple-discoveryprotection@2x.jpg
+assets/images/guide/payments/receive/address-info.png: address-info.png
+assets/images/guide/payments/receive/address-info@2x.png: address-info@2x.png
+assets/images/guide/payments/receive/address-switch.png: address-switch.png
+assets/images/guide/payments/receive/address-switch@2x.png: address-switch@2x.png
+assets/images/guide/payments/receive/enter-details-amount.png: enter-details-amount.png
+assets/images/guide/payments/receive/enter-details-amount@2x.png: enter-details-amount@2x.png
+assets/images/guide/payments/receive/enter-details-compact.png: enter-details-compact.png
+assets/images/guide/payments/receive/enter-details-compact@2x.png: enter-details-compact@2x.png
+assets/images/guide/payments/receive/enter-details-from.png: enter-details-from.png
+assets/images/guide/payments/receive/enter-details-from@2x.png: enter-details-from@2x.png
+assets/images/guide/payments/receive/enter-details-purpose.png: enter-details-purpose.png
+assets/images/guide/payments/receive/enter-details-purpose@2x.png: enter-details-purpose@2x.png
+assets/images/guide/payments/receive/receive-pending-details.png: receive-pending-details.png
+assets/images/guide/payments/receive/receive-pending-details@2x.png: receive-pending-details@2x.png
+assets/images/guide/payments/receive/receive-with-pending.png: receive-with-pending.png
+assets/images/guide/payments/receive/receive-with-pending@2x.png: receive-with-pending@2x.png
+assets/images/guide/payments/receive/share-sharesheet.png: share-sharesheet.png
+assets/images/guide/payments/receive/share-sharesheet@2x.png: share-sharesheet@2x.png
+assets/images/guide/payments/receive/share.png: share.png
+assets/images/guide/payments/receive/share@2x.png: share@2x.png
+assets/images/guide/payments/receive/simple-share-address-settings.png: simple-share-address-settings.png
+assets/images/guide/payments/receive/simple-share-address-settings@2x.png: simple-share-address-settings@2x.png
+assets/images/guide/payments/receive/simple-share.png: simple-share.png
+assets/images/guide/payments/receive/simple-share@2x.png: simple-share@2x.png
+assets/images/guide/payments/receive/transactions-no-label-context.png: transactions-no-label-context.png
+assets/images/guide/payments/receive/transactions-no-label-context@2x.png: transactions-no-label-context@2x.png
+assets/images/guide/payments/receive/transactions-with-label-context.png: transactions-with-label-context.png
+assets/images/guide/payments/receive/transactions-with-label-context@2x.png: transactions-with-label-context@2x.png
diff --git a/assets/images/guide/payments/receive/address-info.png b/assets/images/guide/payments/receive/address-info.png
new file mode 100644
index 000000000..6b7ac548a
Binary files /dev/null and b/assets/images/guide/payments/receive/address-info.png differ
diff --git a/assets/images/guide/payments/receive/address-info@2x.png b/assets/images/guide/payments/receive/address-info@2x.png
new file mode 100644
index 000000000..1185ea1bf
Binary files /dev/null and b/assets/images/guide/payments/receive/address-info@2x.png differ
diff --git a/assets/images/guide/payments/receive/address-switch.png b/assets/images/guide/payments/receive/address-switch.png
new file mode 100644
index 000000000..e166705fc
Binary files /dev/null and b/assets/images/guide/payments/receive/address-switch.png differ
diff --git a/assets/images/guide/payments/receive/address-switch@2x.png b/assets/images/guide/payments/receive/address-switch@2x.png
new file mode 100644
index 000000000..8e0cfd126
Binary files /dev/null and b/assets/images/guide/payments/receive/address-switch@2x.png differ
diff --git a/assets/images/guide/payments/receive/enter-details-amount.png b/assets/images/guide/payments/receive/enter-details-amount.png
new file mode 100644
index 000000000..6fa89a6f9
Binary files /dev/null and b/assets/images/guide/payments/receive/enter-details-amount.png differ
diff --git a/assets/images/guide/payments/receive/enter-details-amount@2x.png b/assets/images/guide/payments/receive/enter-details-amount@2x.png
new file mode 100644
index 000000000..710f8950a
Binary files /dev/null and b/assets/images/guide/payments/receive/enter-details-amount@2x.png differ
diff --git a/assets/images/guide/payments/receive/enter-details-compact.png b/assets/images/guide/payments/receive/enter-details-compact.png
new file mode 100644
index 000000000..240b9c312
Binary files /dev/null and b/assets/images/guide/payments/receive/enter-details-compact.png differ
diff --git a/assets/images/guide/payments/receive/enter-details-compact@2x.png b/assets/images/guide/payments/receive/enter-details-compact@2x.png
new file mode 100644
index 000000000..58aa943e7
Binary files /dev/null and b/assets/images/guide/payments/receive/enter-details-compact@2x.png differ
diff --git a/assets/images/guide/payments/receive/enter-details-from.png b/assets/images/guide/payments/receive/enter-details-from.png
new file mode 100644
index 000000000..99e7d8208
Binary files /dev/null and b/assets/images/guide/payments/receive/enter-details-from.png differ
diff --git a/assets/images/guide/payments/receive/enter-details-from@2x.png b/assets/images/guide/payments/receive/enter-details-from@2x.png
new file mode 100644
index 000000000..4c0bfbb44
Binary files /dev/null and b/assets/images/guide/payments/receive/enter-details-from@2x.png differ
diff --git a/assets/images/guide/payments/receive/enter-details-purpose.png b/assets/images/guide/payments/receive/enter-details-purpose.png
new file mode 100644
index 000000000..f5f2a45c8
Binary files /dev/null and b/assets/images/guide/payments/receive/enter-details-purpose.png differ
diff --git a/assets/images/guide/payments/receive/enter-details-purpose@2x.png b/assets/images/guide/payments/receive/enter-details-purpose@2x.png
new file mode 100644
index 000000000..5bddfbe57
Binary files /dev/null and b/assets/images/guide/payments/receive/enter-details-purpose@2x.png differ
diff --git a/assets/images/guide/payments/receive/receive-pending-details.png b/assets/images/guide/payments/receive/receive-pending-details.png
new file mode 100644
index 000000000..095205116
Binary files /dev/null and b/assets/images/guide/payments/receive/receive-pending-details.png differ
diff --git a/assets/images/guide/payments/receive/receive-pending-details@2x.png b/assets/images/guide/payments/receive/receive-pending-details@2x.png
new file mode 100644
index 000000000..f5b0e0dd5
Binary files /dev/null and b/assets/images/guide/payments/receive/receive-pending-details@2x.png differ
diff --git a/assets/images/guide/payments/receive/receive-with-pending.png b/assets/images/guide/payments/receive/receive-with-pending.png
new file mode 100644
index 000000000..7e9d9d666
Binary files /dev/null and b/assets/images/guide/payments/receive/receive-with-pending.png differ
diff --git a/assets/images/guide/payments/receive/receive-with-pending@2x.png b/assets/images/guide/payments/receive/receive-with-pending@2x.png
new file mode 100644
index 000000000..fa8c322ae
Binary files /dev/null and b/assets/images/guide/payments/receive/receive-with-pending@2x.png differ
diff --git a/assets/images/guide/payments/receive/share-sharesheet.png b/assets/images/guide/payments/receive/share-sharesheet.png
new file mode 100644
index 000000000..e2c4bda1e
Binary files /dev/null and b/assets/images/guide/payments/receive/share-sharesheet.png differ
diff --git a/assets/images/guide/payments/receive/share-sharesheet@2x.png b/assets/images/guide/payments/receive/share-sharesheet@2x.png
new file mode 100644
index 000000000..0826b1da9
Binary files /dev/null and b/assets/images/guide/payments/receive/share-sharesheet@2x.png differ
diff --git a/assets/images/guide/payments/receive/share.png b/assets/images/guide/payments/receive/share.png
new file mode 100644
index 000000000..7ac640f34
Binary files /dev/null and b/assets/images/guide/payments/receive/share.png differ
diff --git a/assets/images/guide/payments/receive/share@2x.png b/assets/images/guide/payments/receive/share@2x.png
new file mode 100644
index 000000000..a6ec44bae
Binary files /dev/null and b/assets/images/guide/payments/receive/share@2x.png differ
diff --git a/assets/images/guide/payments/receive/simple-share-address-settings.png b/assets/images/guide/payments/receive/simple-share-address-settings.png
new file mode 100644
index 000000000..5b01995f3
Binary files /dev/null and b/assets/images/guide/payments/receive/simple-share-address-settings.png differ
diff --git a/assets/images/guide/payments/receive/simple-share-address-settings@2x.png b/assets/images/guide/payments/receive/simple-share-address-settings@2x.png
new file mode 100644
index 000000000..8a6a1f773
Binary files /dev/null and b/assets/images/guide/payments/receive/simple-share-address-settings@2x.png differ
diff --git a/assets/images/guide/payments/receive/simple-share.png b/assets/images/guide/payments/receive/simple-share.png
new file mode 100644
index 000000000..51b4dac04
Binary files /dev/null and b/assets/images/guide/payments/receive/simple-share.png differ
diff --git a/assets/images/guide/payments/receive/simple-share@2x.png b/assets/images/guide/payments/receive/simple-share@2x.png
new file mode 100644
index 000000000..ea569e02a
Binary files /dev/null and b/assets/images/guide/payments/receive/simple-share@2x.png differ
diff --git a/assets/images/guide/payments/receive/transactions-no-label-context.png b/assets/images/guide/payments/receive/transactions-no-label-context.png
new file mode 100644
index 000000000..7abb0c219
Binary files /dev/null and b/assets/images/guide/payments/receive/transactions-no-label-context.png differ
diff --git a/assets/images/guide/payments/receive/transactions-no-label-context@2x.png b/assets/images/guide/payments/receive/transactions-no-label-context@2x.png
new file mode 100644
index 000000000..edf774425
Binary files /dev/null and b/assets/images/guide/payments/receive/transactions-no-label-context@2x.png differ
diff --git a/assets/images/guide/payments/receive/transactions-with-label-context.png b/assets/images/guide/payments/receive/transactions-with-label-context.png
new file mode 100644
index 000000000..17b86ef32
Binary files /dev/null and b/assets/images/guide/payments/receive/transactions-with-label-context.png differ
diff --git a/assets/images/guide/payments/receive/transactions-with-label-context@2x.png b/assets/images/guide/payments/receive/transactions-with-label-context@2x.png
new file mode 100644
index 000000000..442084d36
Binary files /dev/null and b/assets/images/guide/payments/receive/transactions-with-label-context@2x.png differ
diff --git a/guide/glossary.md b/guide/glossary.md
index d341094ca..3995b3b62 100644
--- a/guide/glossary.md
+++ b/guide/glossary.md
@@ -40,14 +40,12 @@ https://www.figma.com/file/qzvCvqhSRx3Jq8aywaSjlr/Bitcoin-Design-Guide-Illustrat
---
### Address
-
-An identifier of 26-35 alphanumeric characters that is used to receive bitcoin. There are [several address formats](https://en.bitcoin.it/wiki/List_of_address_prefixes) based on different specifications. Users need to know this information during backup for future recovery so applications should inform users which format it uses as support varies across applications.
+A Bitcoin address is an identifier of 26-35 alphanumeric characters that is used to receive bitcoin. There are [several address formats](https://en.bitcoin.it/wiki/List_of_address_prefixes) based on different specifications. Users need to know this information during backup for future recovery so applications should inform users which format it uses as support varies across applications.
When users enter an address, these formats have specific prefixes so it is possible to instantly determine which format is being used.
These are the three most common ones:
-
**Legacy address - [P2PKH](https://en.bitcoin.it/wiki/Transaction#Pay-to-PubkeyHash)**
Stands for pay-to-pubkey-hash, i.e pay to a hash of the recipient’s public key. This was the original address format for bitcoin and is often called *legacy address*.
@@ -71,6 +69,35 @@ For example: `bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq`
**Change address**
When the output of a transaction is used as the input of another transaction, it must be spent in its entirety. Sometimes the value of the output is higher than what the user wishes to pay. In this case, the bitcoin client generates a new Bitcoin address, and sends the difference back to this address. This is known as *change address*.
+##### Address compatibility
+Since "legacy" addresses are still in use[^1], and some older applications have yet to upgrade. Script addresses can be used to resolve incompatibility issues that can arise when the sender's application does not recognize the SegWit address provided by the receiver.
+
+To illustrate the problem, suppose the sender is using a legacy wallet and paying to the receiver's SegWit address. In this case, the sender's wallet may incorrectly warn them that the address is invalid or not supported. This can confuse the sender’s end, leading them to think that the receiver provided an incorrect address.
+
+The receiver should then have the ability to switch to a Script address that does not have all the benefits of SegWit, like cheaper transactions but will be compatible with the sender's wallet.
+
+
+
+{% include picture.html
+ image = "/assets/images/guide/payments/receive/address-switch.png"
+ retina = "/assets/images/guide/payments/receive/address-switch@2x.png"
+ alt-text = "Screen with modal of invoice details, and address switcher"
+ caption = "Allow the receiver to switch to a legacy compatible address"
+ width = 250
+ height = 541
+%}
+
+{% include picture.html
+ image = "/assets/images/guide/payments/receive/address-info.png"
+ retina = "/assets/images/guide/payments/receive/address-info@2x.png"
+ alt-text = "Screen explaining SegWit and Legacy addresses"
+ caption = "Provide information about the different address types"
+ width = 250
+ height = 541
+%}
+
+
+
### Account
Just like wallet, the term account can also be used for very different things. In bitcoin wallets that follow the hierarchy described in [BIP44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki), a bitcoin wallet can have multiple accounts, with each one having its own addresses. However, account is also oftentimes used for accounts with third-party service providers.
@@ -376,4 +403,6 @@ With a custodial wallet-application, the users are not exposed to and in charge
- [Bitcoin Q + A glossary](https://www.bitcoinqna.com/glossary)
- [Bitcoin Wiki](https://en.bitcoin.it/wiki/Main_Page)
- [Bitcoin Optech style guide](https://github.com/bitcoinops/bitcoinops.github.io/blob/master/STYLE.md)
-- [Bitcoin Optech topics](https://bitcoinops.org/en/topics/)
\ No newline at end of file
+- [Bitcoin Optech topics](https://bitcoinops.org/en/topics/)
+
+[^1]: [SegWit Usage Trends](https://dashboard.bitcoinops.org/d/xVQwtADiz/segwit-usage-trends?refresh=1h&orgId=1)
\ No newline at end of file
diff --git a/guide/payments/introduction.md b/guide/payments/introduction.md
index 616257dcb..f6bd1d50a 100644
--- a/guide/payments/introduction.md
+++ b/guide/payments/introduction.md
@@ -23,23 +23,23 @@ At its core, the Bitcoin protocol enables transactions between people without in
This chapter is meant to give an overview of bitcoin transactions, including sending, receiving, and transaction privacy, with advice and best practices. After this chapter, you should be able to design payment solutions that are well suited to your product's use case and understand best-practices for its implementation.
-We have already established that [Bitcoin is money](https://bitcoin.design/guide/getting-started/why-bitcoin-is-unique/#its-money-but-digital), so let's dive into how it can be used to facilitate payments.
+We have already established that [Bitcoin is money]({{ '/guide/getting-started/why-bitcoin-is-unique/#its-money-but-digital' | relative_url }}), so let's dive into how it can be used to facilitate payments.
---
-### [Transactions overview](/guide/payments/transactions/)
+### [Transactions overview]({{ '/guide/payments/transactions/' | relative_url }})
An overview of Bitcoin payments, common concepts and the transaction lifecycle.
---
-### [Sending bitcoin](/guide/payments/send/)
+### [Sending bitcoin]({{ '/guide/payments/send/' | relative_url }})
An introduction to how sending bitcoin works.
---
-### Receiving bitcoin (coming soon)
+### [Receiving bitcoin]({{ '/guide/payments/receive/' | relative_url }})
An introduction to how receiving and requesting bitcoin works.
diff --git a/guide/payments/receive.md b/guide/payments/receive.md
new file mode 100644
index 000000000..4c1f2b9fc
--- /dev/null
+++ b/guide/payments/receive.md
@@ -0,0 +1,230 @@
+---
+layout: guide
+title: Receiving bitcoin
+description: An introduction to how receiving bitcoin works.
+nav_order: 3
+parent: Payments
+permalink: /guide/payments/receive/
+main_classes: -no-top-padding
+# image: /assets/images/guide/payments/receive/header.svg
+---
+
+# Receiving bitcoin
+
+
+
+For someone to receive bitcoin, they must provide the sender with a payment destination. They can do this by generating an address in their Bitcoin wallet application. A new address should be generated for every payment, as addresses should only be used once. This helps safeguards the receiver’s privacy.
+
+
+
+## Requesting bitcoin
+The simplest way to receive bitcoin is by generating and sharing a Bitcoin address with the sender. Receivers can share the address by either as a scannable QR code, or as plain text via any regular communication tool like email, instant messaging, SMS, etc.
+
+
+
+{% include picture.html
+ image = "/assets/images/guide/payments/receive/simple-share.png"
+ retina = "/assets/images/guide/payments/receive/simple-share@2x.png"
+ alt-text = "Screen showing how receiver is able to share a bitcoin address as soon as they enter the request flow"
+ width = 250
+ height = 541
+ layout = "background -shadow"
+%}
+
+
+
+{% include tip/tip.html %}
+There are several types of addresses. Sharing one that is incompatible with the sender's wallet application can prevent a successful payment. Read more about [address compatibility]({{ '/guide/glossary/#address-compatibility' | relative_url }}) issues in the glossary.
+{% include tip/close.html %}
+
+## Inputting additional payment details
+
+Many Bitcoin wallet applications provide only this most basic interface with an address for requesting payments. This is convenient in the short-term as it is fast and simple, but may not be in the user’s best interest longer-term. Lists of transactions without information about who they are from and their purpose make it hard to manage personal finances and future transaction privacy.
+
+
+
+{% include picture.html
+ image = "/assets/images/guide/payments/receive/transactions-no-label-context.png"
+ retina = "/assets/images/guide/payments/receive/transactions-no-label-context@2x.png"
+ alt-text = "Screen showing a list of transactions with no context just amounts and transaction IDs"
+ caption = "When no additional information is gathered from the receiver, only what is stored on the blockchain can be shown."
+ width = 250
+ height = 541
+ layout = "shadow"
+%}
+
+{% include picture.html
+ image = "/assets/images/guide/payments/receive/transactions-with-label-context.png"
+ retina = "/assets/images/guide/payments/receive/transactions-with-label-context@2x.png"
+ alt-text = "Screen showing a list of transactions with details about the payment"
+ caption = "While more information can be helpful it requires manual input. Ask which are priorities, and how can you make their entry easier?"
+ width = 250
+ height = 541
+ layout = "shadow"
+%}
+
+
+
+Since the Bitcoin blockchain only stores a limited amount of information, such as the amount and addresses involved, any additional information must be stored in your application. This additional information can be vital in providing context to wallet owners on their spending habits and payment histories. These details have to be manually added. It is possible for receivers to share some of these extra details with senders by encoding them in [payment links]({{ '/guide/foundations/wallet-interoperability/' | relative_url }}).
+
+The following are the standard properties of a payment link:
+
+- **Address** – The destination of the payment
+- **Amount** – How much is being requested (optional)
+- **Label** – For example, the name of who is sending the payment (optional)
+- **Message** – For example, the purpose of payment (optional)
+
+Not all applications support storing additional information, or sharing payment links with these details. When providing this functionality, find the right balance between convenience and usefulness for your target audience. Consider ways that can make the input of these details easy, not burdensome.
+
+
+
+{% include picture.html
+ image = "/assets/images/guide/payments/receive/enter-details-amount.png"
+ retina = "/assets/images/guide/payments/receive/enter-details-amount@2x.png"
+ alt-text = "Screen asking the receiver to enter the amount being requested"
+ caption = "The receiver can specify the amount that they are requesting. This could be shared in payment links which would auto-fill the amount for the sender."
+ width = 250
+ height = 541
+ layout = "shadow"
+%}
+
+{% include picture.html
+ image = "/assets/images/guide/payments/receive/enter-details-from.png"
+ retina = "/assets/images/guide/payments/receive/enter-details-from@2x.png"
+ alt-text = "Screen asking the receiver to enter the name of the sender"
+ caption = "The receiver can use a label to specify who the payment is from. This can be stored and used in suggestions when making future payment requests."
+ width = 250
+ height = 541
+ layout = "shadow"
+%}
+
+{% include picture.html
+ image = "/assets/images/guide/payments/receive/enter-details-purpose.png"
+ retina = "/assets/images/guide/payments/receive/enter-details-purpose@2x.png"
+ alt-text = "Screen asking the receiver to enter the purpose of the payment"
+ caption = "Sometimes the purpose can be determined by identifying who the payment is from. Be mindful of that, and consider easy ways to help the receiver add more context."
+ width = 250
+ height = 541
+ layout = "shadow"
+%}
+
+
+
+
+
+
+
+## Sharing the payment request
+Whether it’s just an address, or a payment link containing additional information, the two primary methods of sharing requests are via QR codes or as plain text.
+
+
+
+{% include picture.html
+ image = "/assets/images/guide/payments/receive/share.png"
+ retina = "/assets/images/guide/payments/receive/share@2x.png"
+ alt-text = "Screen showing the invoice with a share button"
+ caption = ""
+ width = 250
+ height = 541
+ layout = "shadow"
+%}
+
+{% include picture.html
+ image = "/assets/images/guide/payments/receive/share-sharesheet.png"
+ retina = "/assets/images/guide/payments/receive/share-sharesheet@2x.png"
+ alt-text = "Screen showing the invoice overlayed with a share sheet"
+ caption = ""
+ width = 250
+ height = 541
+ layout = "shadow"
+%}
+
+
+
+
+**Text**
+
+Sharing a request as text is as straightforward as copying and pasting. It is also typical for Bitcoin applications to provide the receiver with a “share” button - allowing them to conveniently share addresses or payment links via other applications, with “share sheets” being offered by most mobile operating systems.
+
+**QR codes**
+
+QR codes are commonly used when the sender and receiver are near one another. It is not without its faults though, as some people may not be familiar with QR Codes, and lower-end phones may have difficulty reading them.
+
+Here are some constraints to consider when displaying QR codes:
+
+- Complex QR codes can be difficult for devices with low-resolution cameras to read.
+- Use high contrast between the QR code blocks and their background.
+- Display the QR code at the largest size so that the scanner can detect it easily.
+
+_For more technical details about optimizing QR codes, [see this article](https://bitcoinops.org/en/bech32-sending-support/#creating-more-efficient-qr-codes-with-bech32-addresses)._
+
+## Awaiting the payment
+Once the request has been shared, the sender still has to create and broadcast their transaction, leaving room for uncertainty as to when the payment will be completed and received. Think about how to keep the receiver informed whilst they await their payment.
+
+
+
+{% include picture.html
+ image = "/assets/images/guide/payments/receive/receive-with-pending.png"
+ retina = "/assets/images/guide/payments/receive/receive-with-pending@2x.png"
+ alt-text = "Screen showing a list of incoming payments"
+ caption = "By labeling addresses and storing them, you will be able to indicate the state of incoming payments."
+ width = 250
+ height = 541
+ layout = "shadow"
+%}
+
+{% include picture.html
+ image = "/assets/images/guide/payments/receive/receive-pending-details.png"
+ retina = "/assets/images/guide/payments/receive/receive-pending-details@2x.png"
+ alt-text = "Screen showing details of an incoming payment that is pending"
+ caption = "Consider some users who are new to Bitcoin may not know how its transactions get processed."
+ width = 250
+ height = 541
+ layout = "shadow"
+%}
+
+
+
+If your application has a list of their payment requests or transaction history, show the status and what stage of completion the transaction is at.
+
+Once the payment has been finalized, consider what the receiver may want to do with those funds. You may want to help facilitate those follow-up activities, for example moving the funds to a shared multi-key wallet or doing a [coinjoin]({{ '/guide/glossary/#coinjoin' | relative_url }}).
+
+
+
+
diff --git a/guide/payments/send.md b/guide/payments/send.md
index 816f46bea..b4d124e2b 100644
--- a/guide/payments/send.md
+++ b/guide/payments/send.md
@@ -79,9 +79,9 @@ The receiver does this by generating a new address in their wallet application,
Once you have gotten the address, it's time to enter the payment details. Bitcoin transactions are irreversible, so both the sender and receiver should take great care in correctly sharing and inputting addresses.
-**QR Code** -- Access will need to be granted to your application to enable scanning of QR Codes. Once the camera detects a valid address in the QR Code, it should automatically fill the address field.
+**QR Code** -- Camera access will need to be granted to your Bitcoin application to enable scanning of QR Codes. Once the camera detects a valid address in the QR Code, it should automatically fill the address field.
-**Copy Paste** -- When the sender receives the address or payment link as text, your application can detect a valid address in the clipboard and prompt the sender to press a button to paste it.
+**Copy/Paste** -- When the sender receives the address or payment link as text, your application can detect a valid address in the clipboard and prompt the sender to press a button to paste it.
@@ -120,7 +120,7 @@ Applications sometimes also allow the sender to select fractions of their total
- Payment links and QR Codes can contain an amount. When they do, your application should populate the amount field automatically
- Indicate if an amount entered is more than the available balance
-## Transaction fee
+## Setting the transaction fee
{% include image.html
@@ -162,9 +162,9 @@ Human error with fee selection can lead to costly mistakes, and fee estimations
layout = "float-right-desktop"
%}
-A valid transaction that is broadcast to the network cannot be reversed, so it is critical that the sender is given a chance to double check the payment details (amount, recipient address, total fee, etc) before submitting the transaction.
+A valid transaction that is broadcast to the network cannot be reversed, so it is critical that the sender is given a chance to double-check the payment details (amount, recipient address, total fee, etc) before submitting the transaction.
-If your application allows setting spending limits, and the current transaction exceeds it, make sure they go through some security check (biometric, enter PIN, 2FA password, etc). This technique can also be employed if the transaction is attempting to use the max wallet balance.
+If your application allows setting spending limits, and the current transaction exceeds it, make sure they go through some security check (biometric, enter a PIN, 2FA password, etc). This technique can also be employed if the transaction is attempting to use the max wallet balance.
**Do's**
@@ -199,3 +199,7 @@ Let us look at how we communicate to the sender about the [processing of a trans
**Don'ts**
- Show the transaction as confirmed until it has received ***at least*** one confirmation, but preferably six
+
+---
+
+Sending is one side of the process. Let's look at things from the [receiver's perspective](/guide/payments/receive).