Update components/Starknet/modules/architecture_and_concepts/pages/Sm…

…art_Contracts/contract-classes.adoc Co-authored-by: odednaor <odednaor@gmail.com>
starknet-io · Feb 8, 2024 · 7423827 · 7423827
1 parent 41383a4
commit 7423827
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/...t/modules/architecture_and_concepts/pages/Smart_Contracts/contract-classes.adoc b/...t/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