From 97606bb85a780670677ed14a539680faa8f274f9 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Wed, 17 Jul 2019 17:03:02 -0700 Subject: [PATCH] Payments: fix broken links --- content/concepts/payment-types/direct-xrp-payments.md | 2 +- .../transaction-formats/transaction-types/payment.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/concepts/payment-types/direct-xrp-payments.md b/content/concepts/payment-types/direct-xrp-payments.md index d3360aacd2..047d9437bf 100644 --- a/content/concepts/payment-types/direct-xrp-payments.md +++ b/content/concepts/payment-types/direct-xrp-payments.md @@ -59,7 +59,7 @@ From a relatively high level, the XRP Ledger's transaction processing engine app If necessary, it creates a new account ([AccountRoot object](accountroot.html)) for the receiving address. The new account's starting balance is equal to the `Amount` of the payment. - The engine adds a `delivered_amount` field to the [transaction's metadata](transaction-metadata.html) to indicate how much was delivered. You should always use `delivered_amount`, **not** the `Amount` field, to avoid being tricked about how much XRP you received. (Cross-currency "Partial Payments" can deliver less XRP than stated in the `Amount` field.) For more information, see [Partial Payments](partial-payment.html#partial-payments-exploit). + The engine adds a `delivered_amount` field to the [transaction's metadata](transaction-metadata.html) to indicate how much was delivered. You should always use `delivered_amount`, **not** the `Amount` field, to avoid being tricked about how much XRP you received. (Cross-currency "Partial Payments" can deliver less XRP than stated in the `Amount` field.) For more information, see [Partial Payments](partial-payments.html). ## Comparison to Other Payment Types diff --git a/content/references/rippled-api/transaction-formats/transaction-types/payment.md b/content/references/rippled-api/transaction-formats/transaction-types/payment.md index a86135d79c..b18fd11480 100644 --- a/content/references/rippled-api/transaction-formats/transaction-types/payment.md +++ b/content/references/rippled-api/transaction-formats/transaction-types/payment.md @@ -49,7 +49,7 @@ The Payment transaction type is a general-purpose tool that can represent severa | [Partial payments][] | Object (non-XRP) / String (XRP) | Object (non-XRP) / String (XRP) | Usually required | No | Sends _up to_ a specific amount of any currency. Uses the [tfPartialPayment flag](#payment-flags). May include a `DeliverMin` amount specifying the minimum that the transaction must deliver to be successful; if the transaction does not specify `DeliverMin`, it can succeed by delivering _any positive amount_. | | Currency conversion | Object (non-XRP) / String (XRP) | Object (non-XRP) / String (XRP) | Required | Yes | Consumes offers in the [decentralized exchange](decentralized-exchange.html) to convert one currency to another, possibly taking [arbitrage](https://en.wikipedia.org/wiki/Arbitrage) opportunities. The `Amount` and `SendMax` cannot both be XRP. Also called a _circular payment_ because it delivers money to the sender. The [Data API](data-api.html) tracks this type of transaction as an "exchange" and not a "payment". | -[Direct XRP-to-XRP Payment]: payments.html +[Direct XRP-to-XRP Payment]: direct-xrp-payments.html [Creating or redeeming issued currency]: issued-currencies-overview.html [Cross-currency Payment]: cross-currency-payments.html [Partial payments]: partial-payments.html