From 4c4a7cdfdce350263bd34ec87f1ef77bdd5b1b5d Mon Sep 17 00:00:00 2001 From: Lawal Abubakar Babatunde Date: Wed, 27 Sep 2023 07:37:30 +0100 Subject: [PATCH] fixed minor typo --- src/ch00-08-visibility-mutability.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/ch00-08-visibility-mutability.md b/src/ch00-08-visibility-mutability.md index cf0c5539..e832b1c5 100644 --- a/src/ch00-08-visibility-mutability.md +++ b/src/ch00-08-visibility-mutability.md @@ -12,7 +12,7 @@ These functions are also typically divided into two different implementations bl ## State Mutability Regardless of whether a function is internal or external, it can either modify the contract's state or not. When we declare functions that interact with storage variables inside a smart contract, -we need to explicitly state that we are accessing the `ContractState` by adding it as the first parameter of the function. This is can be done in two different ways: +we need to explicitly state that we are accessing the `ContractState` by adding it as the first parameter of the function. This can be done in two different ways: - If we want our function to be able to mutate the state of the contract, we pass it by reference like this: `ref self: ContractState`. - If we want our function to be read-only and not mutate the state of the contract, we pass it by snapshot like this: `self: @ContractState`.