Merge pull request #680 from BitcoinDesign/feature/send-page-offline-error

Add offline error to the send page

Author: Bosch-0

_compress_images_cache.yml

@@ -1669,3 +1669,5 @@ assets/images/guide/payments/activity/activity-bad-example.png: activity-bad-exa
 assets/images/guide/payments/activity/[email protected]: [email protected]
 assets/images/guide/payments/send/enter-pin-before-payment.png: enter-pin-before-payment.png
 assets/images/guide/payments/send/[email protected]: [email protected]
+assets/images/guide/payments/send/offline-error.png: offline-error.png
+assets/images/guide/payments/send/[email protected]: [email protected]

assets/images/guide/payments/send/offline-error.png

@@ -77,6 +77,9 @@ imagesErrors:
     - file: generic-error-details
       alt: A screen showing error details
       caption: Access to error details for problem-solving.
+    - file: offline-error
+      alt: A screen showing error details
+      caption: If the receiving Lightning wallet is offline, let the user know how to address this problem.
 imagesReview:
     - file: confirm
       alt: Invoice approval screen
@@ -114,9 +117,19 @@ layout = "full-width"
 %}
 
 # Sending bitcoin
+{:.no_toc}
 
 Sending bitcoin is one of the most essential user activities in a bitcoin application, and also one of the least structured ones. People may want to send bitcoin to a known contact, transfer it to another wallet on a different device, or make a purchase via a [payment processor]({{ '/guide/getting-started/software/#payment-processors' | relative_url }}).
 
+---
+
+<div class="glossary-toc" markdown="1">
+* Table of contents
+{:toc}
+</div>
+
+---
+
 ## Payment entry points
 
 The need to send bitcoin can be triggered by many different use cases, and initiated by both sender and receiver. Common entry points are: