ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-28 07:35:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix some filename/URL issues.

Browse Source 
- Change transaction-results/transaction-results/ to not repeat itself,
  adding a redirect from the old URL.
- Fix Japanese localization of 'tasks' not being updated to 'how-tos'.
  (Translated pages in this subfolder were not being shown as translated
  due to the mismatch.)
- Fix unparsed `[base58][]` link in addresses snippet.
This commit is contained in:
mDuo13
2024-03-20 17:34:24 -07:00
parent d3177a9940
commit ae891dc925
111 changed files with 106 additions and 103 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/concepts/transactions/transaction-queue.md
View File

@@ -64,7 +64,7 @@ Within the transaction queue, transactions are ranked so that transactions payin
The precise order of transactions in the queue decides which transactions get added to the next in-progress ledger version in cases where there are more transactions in the queue than the expected size of the next ledger version. The order of the transactions **does not affect the order the transactions are executed within a validated ledger**. In each validated ledger version, the transaction set for that version executes in [canonical order](../consensus-protocol/consensus-structure.md#calculate-and-share-validations).
**Note:** When `rippled` queues a transaction, the provisional [transaction response code](../../references/protocol/transactions/transaction-results/transaction-results.md) is `terQUEUED`. This means that the transaction is likely to succeed in a future ledger version. As with all provisional response codes, the outcome of the transaction is not final until the transaction is either included in a validated ledger, or [rendered permanently invalid](finality-of-results/index.md).
**Note:** When `rippled` queues a transaction, the provisional [transaction response code](../../references/protocol/transactions/transaction-results/index.md) is `terQUEUED`. This means that the transaction is likely to succeed in a future ledger version. As with all provisional response codes, the outcome of the transaction is not final until the transaction is either included in a validated ledger, or [rendered permanently invalid](finality-of-results/index.md).
## See Also