From fb2c5b5ba28fb257473ea4fbc8154a6b39ce37be Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Fri, 11 May 2018 19:20:04 -0700 Subject: [PATCH] Fix time links in tuts, etc. --- .../use-escrows/send-a-time-held-escrow.md | 4 ++-- .../use-complex-payment-types/use-payment-channels.md | 8 +++++--- 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/content/tutorials/use-complex-payment-types/use-escrows/send-a-time-held-escrow.md b/content/tutorials/use-complex-payment-types/use-escrows/send-a-time-held-escrow.md index 421ffb9a4d..dd1140412e 100644 --- a/content/tutorials/use-complex-payment-types/use-escrows/send-a-time-held-escrow.md +++ b/content/tutorials/use-complex-payment-types/use-escrows/send-a-time-held-escrow.md @@ -4,7 +4,7 @@ The [EscrowCreate transaction][] type can create an escrow whose only condition ## 1. Calculate release time -You must [specify the time](reference-rippled.html#specifying-time) as whole **seconds since the Ripple Epoch**, which is 946684800 seconds after the UNIX epoch. For example, to release funds at midnight UTC on November 13, 2017: +You must specify the time as whole **[seconds since the Ripple Epoch][]**, which is 946684800 seconds after the UNIX epoch. For example, to release funds at midnight UTC on November 13, 2017: @@ -133,7 +133,7 @@ Response: ## 6. Submit EscrowFinish transaction -[Sign and submit](reference-transaction-format.html#signing-and-submitting-transactions) an [EscrowFinish transaction][] to execute the release of the funds after the `FinishAfter` time has passed. Set the `Owner` field of the transaction to the `Account` address from the EscrowCreate transaction, and the `OfferSequence` to the `Sequence` number from the EscrowCreate transaction. For an escrow held only by time, omit the `Condition` and `Fulfillment` fields. +[Sign and submit](transaction-basics.html#signing-and-submitting-transactions) an [EscrowFinish transaction][] to execute the release of the funds after the `FinishAfter` time has passed. Set the `Owner` field of the transaction to the `Account` address from the EscrowCreate transaction, and the `OfferSequence` to the `Sequence` number from the EscrowCreate transaction. For an escrow held only by time, omit the `Condition` and `Fulfillment` fields. **Tip:** The EscrowFinish transaction is necessary because the XRP Ledger's state can only be modified by transactions. The sender of this transaction may be the recipient of the escrow, the original sender of the escrow, or any other XRP Ledger address. diff --git a/content/tutorials/use-complex-payment-types/use-payment-channels.md b/content/tutorials/use-complex-payment-types/use-payment-channels.md index 71ab519c22..db889292cf 100644 --- a/content/tutorials/use-complex-payment-types/use-payment-channels.md +++ b/content/tutorials/use-complex-payment-types/use-payment-channels.md @@ -471,7 +471,7 @@ Example `account_channels` response: } } -In this example, the `expiration` value 547073182 in [seconds since the Ripple Epoch](reference-rippled.html#specifying-time) maps to 2017-05-02T20:46:22Z, so any claims not redeemed by that time are no longer valid. +In this example, the `expiration` value 547073182 in [seconds since the Ripple Epoch][] maps to 2017-05-02T20:46:22Z, so any claims not redeemed by that time are no longer valid. ## 10. Anyone can close the expired channel. @@ -601,5 +601,7 @@ This concludes the tutorial of Payment Channel usage. Ripple encourages users to - -{% include '_snippets/tx-type-links.md' %} + +{% include '_snippets/rippled-api-links.md' %} +{% include '_snippets/tx-type-links.md' %} +{% include '_snippets/rippled_versions.md' %}