From 4254b51771100f0e18187ae2ff518a722283a046 Mon Sep 17 00:00:00 2001 From: Rome Reginelli Date: Tue, 6 Jul 2021 23:33:12 -0700 Subject: [PATCH] Tickets: fix typo --- content/concepts/payment-system-basics/accounts/tickets.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/concepts/payment-system-basics/accounts/tickets.md b/content/concepts/payment-system-basics/accounts/tickets.md index 907fbb42c8..863be5d203 100644 --- a/content/concepts/payment-system-basics/accounts/tickets.md +++ b/content/concepts/payment-system-basics/accounts/tickets.md @@ -15,7 +15,7 @@ A Ticket in the XRP Ledger is a way of setting aside a [sequence number][Sequenc ## Background -[Transactions](transaction-basics.html) have sequence numbers so that any given transaction can execute no more than once. Sequence numbers also make sure any given transaction is unique: if you send the exact same amount of money to the same person multiple times, the Sequence Number is one detail that is guaranteed to be different each time. Finally, Sequence Numbers provide an elegant way to put transactions in a consistent order, even if some of them to arrive out of order when sent throughout the network. +[Transactions](transaction-basics.html) have sequence numbers so that any given transaction can execute no more than once. Sequence numbers also make sure any given transaction is unique: if you send the exact same amount of money to the same person multiple times, the Sequence Number is one detail that is guaranteed to be different each time. Finally, Sequence Numbers provide an elegant way to put transactions in a consistent order, even if some of them tarrive out of order when sent throughout the network. However, there are some situations where sequence numbers are too limiting. For example: