From 3023e09a44f019eb079f2ec16b8f35f2ac39ff0e Mon Sep 17 00:00:00 2001 From: Bri Wylde <92327786+briwylde08@users.noreply.github.com> Date: Fri, 22 Dec 2023 08:53:16 -0700 Subject: [PATCH] Update docs/fundamentals-and-concepts/stellar-data-structures/contracts.mdx Co-authored-by: Justin Rice --- .../stellar-data-structures/contracts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/fundamentals-and-concepts/stellar-data-structures/contracts.mdx b/docs/fundamentals-and-concepts/stellar-data-structures/contracts.mdx index 89293ca3e..361d5b3f9 100644 --- a/docs/fundamentals-and-concepts/stellar-data-structures/contracts.mdx +++ b/docs/fundamentals-and-concepts/stellar-data-structures/contracts.mdx @@ -13,7 +13,7 @@ A smart contract is a programmed set of executable code and state that can be in ## Wasm Bytecode -Once a smart contract has been written by a developer and compiled into a WebAssembly (Wasm) executable file, it can then be "installed" onto the Stellar network. A `CONTRACT_DATA` [ledger entry](ledgers.mdx) is created to store this binary data and its unique identifier is the hash of the executable file. This binary executable is stored independently from its deployed contract(s). When a Stellar transaction attempts to invoke a contract function, the first thing to take place is this Wasm bytecode is retrieved from the ledger and a secure, isolated runtime virtual machine ("VM") is instantiated so it can run the bytecode for the contract and then exit. +Once a smart contract has been written by a developer and compiled into a WebAssembly (Wasm) executable file, it can then be "installed" onto the Stellar network. A `CONTRACT_DATA` [ledger entry](ledgers.mdx) is created to store this binary data and its unique identifier is the hash of the executable file. This binary executable is stored independently from its deployed contract(s). When a Stellar transaction attempts to invoke a contract function, the Wasm bytecode is first retrieved from the ledger and a secure, isolated runtime virtual machine ("VM") is instantiated so it can run the bytecode for the contract and then exit. ## Contract Instances