ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-12-05 08:48:11 +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/consensus-protocol/consensus-structure.md
View File

@@ -51,7 +51,7 @@ _Figure 3: Transactions Applied to Ledger Version_
The set of transactions included in a ledger instance are recorded in that ledger and allow audits of the XRP Ledger history. If an account balance is different in ledger N+1 than it was in ledger N, then ledger N+1 contains the transaction(s) responsible for the change.
Transactions that appear in a validated ledger may have succeeded in changing the ledger, or may have been processed without doing the requested action. Successful transactions have the **`tesSUCCESS`** [result code](../../references/protocol/transactions/transaction-results/transaction-results.md) which indicates the requested changes are applied to the ledger. Failed transactions in the ledger have **`tec`** class result codes.<a href="#footnote_1" id="from_footnote_1"><sup>1</sup></a>
Transactions that appear in a validated ledger may have succeeded in changing the ledger, or may have been processed without doing the requested action. Successful transactions have the **`tesSUCCESS`** [result code](../../references/protocol/transactions/transaction-results/index.md) which indicates the requested changes are applied to the ledger. Failed transactions in the ledger have **`tec`** class result codes.<a href="#footnote_1" id="from_footnote_1"><sup>1</sup></a>
All transactions included in a ledger destroy some XRP as a [transaction cost](../transactions/transaction-cost.md), regardless of whether they had a **`tes`** or **`tec`** code. The exact amount of XRP to destroy is defined by the signed transaction instructions.