Skip to content

Commit e453474

Browse files
committed
terNO_RIPPLE: reword description for simplicity
1 parent 9cbca12 commit e453474

File tree

1 file changed

+1
-1
lines changed
  • docs/references/protocol/transactions/transaction-results

1 file changed

+1
-1
lines changed

docs/references/protocol/transactions/transaction-results/ter-codes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Transactions with `ter` codes have not been applied to the current ledger and ha
2323
| `terNO_AMM` | The AMM-related transaction specifies an asset pair that does not currently have an AMM instance. _(Added by the [AMM amendment][])_ |
2424
| `terNO_AUTH` | The transaction would involve adding currency issued by an account with `lsfRequireAuth` enabled to a trust line that is not authorized. For example, you placed an offer to buy a currency you aren't authorized to hold. |
2525
| `terNO_LINE` | Used internally only. This code should never be returned. |
26-
| `terNO_RIPPLE` | The transaction can't succeed because of No Ripple settings on trust lines. For example, the Check tried to send a token payment that would be blocked because of No Ripple flags. Alternatively, the transaction tried to create an AMM even though the issuer of at least one of the tokens has not enabled the [Default Ripple flag](/docs/concepts/tokens/fungible-tokens/rippling/#the-default-ripple-flag). |
26+
| `terNO_RIPPLE` | The transaction can't succeed because of [rippling settings](/docs/concepts/tokens/fungible-tokens/rippling/). For example, the transaction tried to create an AMM even though the issuer of at least one of the tokens has not enabled the Default Ripple flag. |
2727
| `terOWNERS` | The transaction requires that account sending it has a nonzero "owners count", so the transaction cannot succeed. For example, an account cannot enable the [`lsfRequireAuth`](../types/accountset.md#accountset-flags) flag if it has any trust lines or available offers. |
2828
| `terPRE_SEQ` | The `Sequence` number of the current transaction is higher than the current sequence number of the account sending the transaction. |
2929
| `terPRE_TICKET` | The transaction attempted to use a [Ticket](../../../../concepts/accounts/tickets.md), but the specified `TicketSequence` number does not exist in the ledger. However, the Ticket could still be created by another transaction. |

0 commit comments

Comments
 (0)