From 9c49ce1d9c5d0efe17ea72c959a03be48556f620 Mon Sep 17 00:00:00 2001 From: Bri Wylde <92327786+briwylde08@users.noreply.github.com> Date: Wed, 20 Dec 2023 08:47:57 -0700 Subject: [PATCH] Update docs/fundamentals-and-concepts/stellar-data-structures/operations-and-transactions.mdx Co-authored-by: Elliot Voris --- .../stellar-data-structures/operations-and-transactions.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/fundamentals-and-concepts/stellar-data-structures/operations-and-transactions.mdx b/docs/fundamentals-and-concepts/stellar-data-structures/operations-and-transactions.mdx index 40597fbb3..be00be1c3 100644 --- a/docs/fundamentals-and-concepts/stellar-data-structures/operations-and-transactions.mdx +++ b/docs/fundamentals-and-concepts/stellar-data-structures/operations-and-transactions.mdx @@ -5,7 +5,7 @@ sidebar_position: 40 ## Operations and transactions: how they work -To perform actions with an account on the Stellar network, you compose operations, bundle them into a transaction, and then sign and submit the transaction to the network. Smart contract transactions (`InvokeHostFunctionOp`, `ExtendFootprintTTLOp`, and `RestoreFootprintOp`) can only have one operation per transaction. +To perform actions with an account on the Stellar network, you compose operations, bundle them into a transaction, and then sign and submit the transaction to the network. Smart contract transactions (those with `InvokeHostFunctionOp`, `ExtendFootprintTTLOp`, or `RestoreFootprintOp` operations) can only have one operation per transaction. ### Operations