From 7423827eca1f40d3f42af298aeacb55f2bda388f Mon Sep 17 00:00:00 2001 From: Steve Goodman <39279277+stoobie@users.noreply.github.com> Date: Thu, 8 Feb 2024 15:45:52 +0200 Subject: [PATCH] Update components/Starknet/modules/architecture_and_concepts/pages/Smart_Contracts/contract-classes.adoc Co-authored-by: odednaor --- .../pages/Smart_Contracts/contract-classes.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/Starknet/modules/architecture_and_concepts/pages/Smart_Contracts/contract-classes.adoc b/components/Starknet/modules/architecture_and_concepts/pages/Smart_Contracts/contract-classes.adoc index 9eb7d59645..29076e1e90 100644 --- a/components/Starknet/modules/architecture_and_concepts/pages/Smart_Contracts/contract-classes.adoc +++ b/components/Starknet/modules/architecture_and_concepts/pages/Smart_Contracts/contract-classes.adoc @@ -20,7 +20,7 @@ A contract class does not necessarily have a deployed instance in Starknet. A contract class does not necessarily require a deployed instance in Starknet. ==== -#A contract instance has a nonce, the value of which is the number of transactions originating from this address plus 1. For example, when you deploy an account with a `DEPLOY_ACCOUNT` transaction, the nonce of the account contract in the transaction is `0`. After the transaction, until the account contract sends its first transaction, the nonce is `1`.# +A contract instance has a nonce, the value of which is the number of transactions originating from this address plus 1. For example, when you deploy an account with a `DEPLOY_ACCOUNT` transaction, the nonce of the account contract in the transaction is `0`. After the `DEPLOY_ACCOUNT` transaction, until the account contract sends its next transaction, the nonce is `1`. == Working with classes