diff --git a/content/concepts/payment-system-basics/transaction-basics/transaction-basics.md b/content/concepts/payment-system-basics/transaction-basics/transaction-basics.md
index 3c63f9095e..d8d3df69aa 100644
--- a/content/concepts/payment-system-basics/transaction-basics/transaction-basics.md
+++ b/content/concepts/payment-system-basics/transaction-basics/transaction-basics.md
@@ -51,6 +51,8 @@ Sending a transaction to the XRP Ledger involves several steps:
 5. The `rippled` servers apply those transactions to the previous ledger in a canonical order and share their results.
 6. If enough [trusted validators](rippled-server-modes.html#reasons-to-run-a-validator) created the exact same ledger, that ledger is declared _validated_ and the [results of the transactions](transaction-results.html) in that ledger are immutable.
 
+See [Send XRP](send-xrp.html) for an interactive tutorial in sending XRP payments.
+
 
 ### Example Unsigned Transaction
 
@@ -93,7 +95,7 @@ Signing a transaction generates a binary blob that can be submitted to the netwo
 
 ## Example Executed Transaction with Metadata
 
-After a transaction has been submitted, you can check its status using the API, for example using the [tx command](tx.html).
+After a transaction has been submitted, you can check its status using the API, for example using the [tx command](tx.html). This shows the transaction instructions, its outcome, and the [metadata](transaction-metadata.html) of all changes that were made in the process of executing it.
 
 **Caution:** The success of a transaction is not final unless the transaction appears in a **validated** ledger with the result code `tesSUCCESS`. See also: [Finality of Results](finality-of-results.html).
 
diff --git a/content/tutorials/use-simple-xrp-payments/send-xrp.md b/content/tutorials/use-simple-xrp-payments/send-xrp.md
index fa2e4175b9..23b7a2d1e4 100644
--- a/content/tutorials/use-simple-xrp-payments/send-xrp.md
+++ b/content/tutorials/use-simple-xrp-payments/send-xrp.md
@@ -599,6 +599,18 @@ api.connect()
 
 **Tip:** The local connection uses the WebSocket protocol (`ws`) unencrypted rather than the TLS-encrypted version (`wss`). This is secure only because the communications never leave the same machine, and is easier to set up because it does not require a TLS certificate. For connections on an outside network, always use `wss`.
 
+## Next Steps
+
+After completing this tutorial, you may want to try the following:
+
+- Build [Reliable transaction submission](reliable-transaction-submission.html) for production systems.
+- Consult the [RippleAPI JavaScript Reference](rippleapi-reference.html) for the full range of XRP Ledger functionality.
+- Customize your [Account Settings](manage-account-settings.html).
+- Learn how [Transaction Metadata](transaction-metadata.html) describes the outcome of a transaction in detail.
+- Explore [Complex Payment Types](complex-payment-types.html) like escrow and payment channels.
+- Read best practices for [XRP Ledger Businesses](xrp-ledger-businesses.html).
+
+
 
 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}