From fcae5f39de4688f1c11cb241e04b545180f93a93 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Wed, 20 Oct 2021 12:56:12 -0700 Subject: [PATCH] Fix broken links --- .../transaction-basics/transaction-cost.md | 2 +- dactyl-config.yml | 6 +++++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/content/concepts/payment-system-basics/transaction-basics/transaction-cost.md b/content/concepts/payment-system-basics/transaction-basics/transaction-cost.md index 90c1fd9ab5..95e6ead2c7 100644 --- a/content/concepts/payment-system-basics/transaction-basics/transaction-cost.md +++ b/content/concepts/payment-system-basics/transaction-basics/transaction-cost.md @@ -124,7 +124,7 @@ The `Fee` field is one of the things that can be [auto-filled](transaction-commo - To prevent a transaction from getting stuck in a state of being neither definitively confirmed or rejected, be sure to provide a `LastLedgerSequence` parameter so it eventually expires. Alternatively, you can try to [cancel a stuck transaction](about-canceling-a-transaction.html) by reusing the same `Sequence` number. See [reliable transaction submission](reliable-transaction-submission.html) for best practices. - You have to be careful that the automatically provided value isn't too high. You don't want to burn a large fee to send a small transaction. - If you are using `rippled`, you can also use the `fee_mult_max` and `fee_div_max` parameters of the [sign method][] to set a limit to the load scaling you are willing to sign. - - Some client libraries (like [xrpl.js](https://js.xrpl.org/) and [xrpl-py](xrpl-py.readthedocs.io/)) have configurable maximum `Fee` values, and raise an error instead of signing a transaction whose `Fee` value is higher than the maximum. + - Some client libraries (like [xrpl.js](https://js.xrpl.org/) and [xrpl-py](https://xrpl-py.readthedocs.io/)) have configurable maximum `Fee` values, and raise an error instead of signing a transaction whose `Fee` value is higher than the maximum. - You cannot auto-fill from an offline machine nor when [multi-signing](multi-signing.html). diff --git a/dactyl-config.yml b/dactyl-config.yml index 13e61a4c13..c0584fd097 100644 --- a/dactyl-config.yml +++ b/dactyl-config.yml @@ -96,12 +96,14 @@ targets: # Fix 2 links from untranslated demurrage.html: "currency-formats.html#issued-currency-precision": "currency-formats.html#発行済み通貨の計算" "currency-formats.html#currency-codes": "currency-formats.html#通貨コード" - # Fix 5 links from untranslated become-an-xrp-ledger-gateway.html + # Fix links from untranslated become-an-xrp-ledger-gateway.html "paths.html#default-paths": "paths.html#デフォルトパス" "payment.html#payment-flags": "payment.html#paymentのフラグ" "accountroot.html#accountroot-flags": "accountroot.html#accountrootのフラグ" "trustset.html#trustset-flags": "trustset.html#trustsetのフラグ" "basic-data-types.html#ledger-index": "basic-data-types.html#レジャーインデックス" + # nearest approximation. this translation is also out of date + "rippled-server-modes.html#validators": "rippled-server-modes.html#バリデータを運用する理由" # Fix links from untranslated open-a-payment-channel-to-enable-an-inter-exchange-network.html "use-payment-channels.html#1-the-payer-creates-a-payment-channel-to-a-particular-recipient": "use-payment-channels.html#1-支払人が特定の受取人へのpayment-channelを作成します" "use-payment-channels.html#2-the-payee-checks-specifics-of-the-payment-channel": "use-payment-channels.html#2-受取人がpayment-channelの特性を確認します" @@ -165,6 +167,8 @@ targets: # Fix links from untranslated xrpl.js 2.0 migration guide: "basic-data-types.html#specifying-ledgers": "basic-data-types.html#レジャーの指定" "subscribe.html#ledger-stream": "subscribe.html#レジャーストリーム" + # the updates to ledger_entry aren't translated either + "ledger_entry.html#get-paychannel-object": "ledger_entry.html" pages: