Adjust language around an account submitting multiple transactions pe… (

#1229)

* Adjust language around an account submitting multiple transactions per ledger

* wording

docs/learn/fundamentals/transactions/operations-and-transactions.mdx

@@ -127,15 +127,15 @@ The source account must exist on the ledger.
 
 #### Fee
 
-The fee must be greater than or equal to the network minimum fee for the number of operations submitted as part of the transaction. This does not guarantee that the transaction will be applied, only that it is valid. In addition, the source account must be able to pay the fee specified. If multiple transactions are submitted but only a subset of them can be paid for, they are checked for validity in order of sequence number.
+The fee must be greater than or equal to the network minimum fee for the number of operations submitted as part of the transaction. This does not guarantee that the transaction will be applied, only that it is valid. In addition, the source account must be able to pay the fee specified.
 
 #### Fee-bump (if applicable)
 
 See Validity of a [Fee-Bump Transaction section](../../encyclopedia/transactions-specialized/fee-bump-transactions.mdx#validity-of-a-fee-bump-transaction)
 
 #### Sequence number
 
-The sequence number must be one greater than the sequence number stored in the source account entry when the transaction is applied unless sequence number preconditions are set. When checking the validity of multiple transactions with the same source account in a candidate transaction set, they must all be valid transactions and their sequence numbers must be offset by one. Then they are ordered and applied according to their sequence number.
+The sequence number must be one greater than the sequence number stored in the source account entry when the transaction is applied unless sequence number preconditions are set. An account can only have one transaction (and, therefore, one sequence number) consumed per ledger.
 
 #### List of operations
 

docs/learn/fundamentals/transactions/transaction-lifecycle.mdx

@@ -19,7 +19,7 @@ Once the transaction is complete, it becomes a transaction envelope containing t
 
 ### 3. Submitting (Transaction Submitter)
 
-After signing, the transaction can now be submitted to the Stellar network. If the transaction is invalid, it will be rejected immediately by Stellar Core, the account’s sequence number will not be incremented, and no fee will be consumed from the source account. Multiple transactions for the same account can be submitted, provided each sequence number is off by one (unless minimum sequence number preconditions are set). If they are all valid, Stellar Core will craft a transaction set with each of those transactions applied in sequence number order. Transactions are typically submitted using Horizon, but you can also submit the transaction directly to an instance of Stellar Core.
+After signing, the transaction can now be submitted to the Stellar network. If the transaction is invalid, it will be rejected immediately by Stellar Core, the account’s sequence number will not be incremented, and no fee will be consumed from the source account. Only one transaction (and one sequence number) for the same account can be consumed per ledger. Transactions are typically submitted using Horizon, but you can also submit the transaction directly to an instance of Stellar Core.
 
 ### 4. Propagating (Validator)
 
@@ -43,7 +43,7 @@ If a transaction is kept in memory after a certain number of ledger closes, it w
 
 ### 8. Transaction apply order is determined (Validator Network)
 
-Once SCP agrees on a particular transaction set, the apply order is computed for the transaction set. This shuffles the set's order to create uncertainty for competing transactions and maintains the order of sequence numbers for multiple transactions per account.
+Once SCP agrees on a particular transaction set, the apply order is computed for the transaction set. This shuffles the set's order to create uncertainty for competing transactions.
 
 ### 9. Fees are collected (Validator)