diff --git a/components/Starknet/modules/architecture_and_concepts/pages/Cryptography/hash-functions.adoc b/components/Starknet/modules/architecture_and_concepts/pages/Cryptography/hash-functions.adoc
index d24233814d..a1a6dfa15c 100644
--- a/components/Starknet/modules/architecture_and_concepts/pages/Cryptography/hash-functions.adoc
+++ b/components/Starknet/modules/architecture_and_concepts/pages/Cryptography/hash-functions.adoc
@@ -5,13 +5,13 @@
 [id="domain_and_range"]
 == Domain and range
 
-All hashes outputs are eventually mapped to elements in stem:[$\mathbb{F}_p$] with stem:[$p=2^{251}+17\cdot 2^{192}+1$].
+All hashes outputs are eventually mapped to elements in stem:[$\mathbb{F}_P$], where stem:[$P=2^{251}+17\cdot 2^{192}+1$].
 
 There are three hash functions used throughout Starknet's specifications:
 
-* stem:[$sn\_keccak: \{0,1\}^* \rightarrow \mathbb{F}_p$]
-* stem:[$pedersen: \mathbb{F}_p^2\rightarrow\mathbb{F}_p$]
-* stem:[$poseidon: \mathbb{F}_p^*\rightarrow \mathbb{F}_p$]
+* stem:[$sn\_keccak: \{0,1\}^* \rightarrow \mathbb{F}_P$]
+* stem:[$pedersen: \mathbb{F}_P^2\rightarrow\mathbb{F}_P$]
+* stem:[$poseidon: \mathbb{F}_P^*\rightarrow \mathbb{F}_P$]
 
 [id="starknet_keccak"]
 == Starknet Keccak
@@ -22,7 +22,7 @@ in order to fit into a field element.
 [id="pedersen_hash"]
 == Pedersen hash
 
-Pedersen hash makes use of the following STARK friendly elliptic curve over stem:[$\mathbb{F}_p$]:
+Pedersen hash makes use of the following STARK friendly elliptic curve over stem:[$\mathbb{F}_P$]:
 
 [stem]
 ++++
@@ -37,7 +37,7 @@ where
 [id="definition"]
 === Definition
 
-Given an input stem:[$(a,b)\in\mathbb{F}_p^2$], we begin by breaking it into stem:[$a_{low}, a_{high}, b_{low}, b_{high}$],
+Given an input stem:[$(a,b)\in\mathbb{F}_P^2$], we begin by breaking it into stem:[$a_{low}, a_{high}, b_{low}, b_{high}$],
 where the low part consists of the low 248 bits of the element and the high part consists of the high 4 bits of the element. Our Pedersen hash is then defined by:
 
 [stem]
@@ -72,6 +72,7 @@ poseidon_2(x,y) := \left[\text{hades_permutation}(x,y,2)\right]_0
 Where latexmath:[[\cdot\]_j] denotes taking the j'th coordinate of a tuple
 
 .Additional resources
+
 * xref:#poseidon_array_hash[Poseidon hash with an arbitrary number of inputs]
 * link:https://github.com/starkware-industries/poseidon/blob/main/poseidon3.txt[Parameters for defining the Poseidon permutation used in Starknet]
 * link:https://github.com/CryptoExperts/poseidon[Reference implementation in C and assembly of the above by CryptoExperts]
@@ -94,7 +95,7 @@ h(...h(h(0, a_1),a_2),...,a_n),n)
 [id="poseidon_array_hash"]
 === Poseidon
 
-Let stem:[$\text{hades}:\mathbb{F}_p^3\rightarrow\mathbb{F}_p^3$] denote the Hades permutation (with Starknet's parameters), then given an array stem:[$a_1,...,a_n$] of stem:[$n$] field elements
+Let stem:[$\text{hades}:\mathbb{F}_P^3\rightarrow\mathbb{F}_P^3$] denote the Hades permutation, with Starknet's parameters, then given an array stem:[$a_1,...,a_n$] of stem:[$n$] field elements
 we define stem:[$poseidon(a_1,...,a_n)$] to be the first coordinate of stem:[$H(a_1,...,a_n;0,0,0)$], where:
 
 [stem]
@@ -106,5 +107,5 @@ H\big(a_3,...,a_n;\text{hades}(s_1+a_1, s_2+a_2, s_3)\big), & \text{if  } n\ge 2
 \end{cases}
 ++++
 
-You can find an implementation of the above in Python link:https://github.com/starkware-libs/cairo-lang/blob/12ca9e91bbdc8a423c63280949c7e34382792067/src/starkware/cairo/common/poseidon_hash.py#L46[here],
-and an equivalent Cairo implementation link:https://github.com/starkware-libs/cairo-lang/blob/12ca9e91bbdc8a423c63280949c7e34382792067/src/starkware/cairo/common/builtin_poseidon/poseidon.cairo#L28[here].
+For an implementation of the above in Python, see link:https://github.com/starkware-libs/cairo-lang/blob/12ca9e91bbdc8a423c63280949c7e34382792067/src/starkware/cairo/common/poseidon_hash.py#L46[poseidon_hash.py],
+and for an equivalent Cairo implementation, see link:https://github.com/starkware-libs/cairo-lang/blob/12ca9e91bbdc8a423c63280949c7e34382792067/src/starkware/cairo/common/builtin_poseidon/poseidon.cairo#L28[poseidon.cairo] in the cairo-lang Github repository.
diff --git a/components/Starknet/modules/architecture_and_concepts/pages/Cryptography/p-value.adoc b/components/Starknet/modules/architecture_and_concepts/pages/Cryptography/p-value.adoc
index 85422f6c9c..487a4cd66e 100644
--- a/components/Starknet/modules/architecture_and_concepts/pages/Cryptography/p-value.adoc
+++ b/components/Starknet/modules/architecture_and_concepts/pages/Cryptography/p-value.adoc
@@ -2,7 +2,7 @@
 
 // The field element type in Starknet is based on the STARK field in the underlying Cairo VM. In other words, a value stem:[$$x$$] of a field element type is an integer in the range of stem:[$$0≤x<P$$].
 
-The _STARK field_ is the finite field stem:[\mathbb{F}_P], where stem:[$$P$$] is a prime number, calculated as follows:
+The _STARK field_ is the finite field stem:[$$\mathbb{F}_P$$], where stem:[$$P$$] is a prime number, calculated as follows:
 
 [stem]
 ++++
diff --git a/components/Starknet/modules/architecture_and_concepts/pages/Network_Architecture/starknet-state.adoc b/components/Starknet/modules/architecture_and_concepts/pages/Network_Architecture/starknet-state.adoc
index 64a912f727..28998f7dec 100644
--- a/components/Starknet/modules/architecture_and_concepts/pages/Network_Architecture/starknet-state.adoc
+++ b/components/Starknet/modules/architecture_and_concepts/pages/Network_Architecture/starknet-state.adoc
@@ -31,9 +31,9 @@ according to the execution of the contract instance's constructor.
 [id="state_commitment"]
 == State commitment
 
-The state commitment is a digest that uniquely represents the state.
+The state commitment is a digest that represents the state.
 
-In Starknet, the commitment combines the roots of two binary xref:#merkle_patricia_trie[Merkle-Patricia tries] of height 251 in the following manner:
+In Starknet, the state commitment combines the roots of two binary xref:#merkle_patricia_trie[Merkle-Patricia tries] of height 251 in the following manner:
 
 [,,subs="quotes"]
 ----
@@ -46,7 +46,7 @@ state_commitment = _h_~Pos~(
 
 Where:
 
-* `_h_~Pos~ is the xref:Cryptography/hash-functions.adoc#poseidon_hash[Poseidon] hash
+* `_h_~Pos~` is the xref:Cryptography/hash-functions.adoc#poseidon_hash[Poseidon] hash
 function.
 * `STARKNET_STATE_V0` is a constant prefix string encoded in ASCII (and represented as a field element).
 * `contract_trie_root` is the root of the xref:#contracts_trie[_contract trie_], a Merkle-Patricia trie whose leaves are the contracts' states.
@@ -55,7 +55,9 @@ function.
 [id="contracts_trie"]
 === The contract trie
 
-As with Ethereum, this trie is a two-level structure where the contract address determines the path from the root to the leaf encoding the contract state. The information stored in the leaf is as follows:
+As with Ethereum, this trie is a two-level structure, whose leaves correspond to distinct contracts. The address of each contract determines the path from the trie’s root to its corresponding leaf, whose content encodes the contract’s state.
+
+The information stored in the leaf is as follows:
 
 // [stem]
 // ++++
@@ -104,13 +106,13 @@ Where:
 
 [NOTE]
 ====
-Cairo classes that are part of the commitment are defined with Sierra, an intermediate representation between Cairo and Cairo assembly. For more information, see xref:Smart_Contracts/system-calls-cairo1.adoc[System calls].
+Cairo classes that are part of the state commitment are defined with Sierra, an intermediate representation between Cairo and Cairo assembly. For more information, see xref:Smart_Contracts/system-calls-cairo1.adoc[System calls].
 
 However, the prover only deals with Cairo assembly (Casm).
 
-So in order to prevent needing to compile from Sierra to Casm in every block in which the class is used, the commitment must have some information about the corresponding Cairo assembly.
+So in order to prevent needing to compile from Sierra to Casm in every block in which the class is used, the state commitment must have some information about the corresponding Cairo assembly.
 
-Today, the user signs the compiled class hash as part of a xref:Network_Architecture/transactions.adoc#declare_v2[declare] transaction. If the transaction is included in a block, then the compiled class hash becomes part of the commitment.
+Today, the user signs the compiled class hash as part of a xref:Network_Architecture/transactions.adoc#declare_v2[declare] transaction. If the transaction is included in a block, then the compiled class hash becomes part of the state commitment.
 
 In the future, when Sierra-to-Casm compilation becomes part of the Starknet OS, this value might be updated via a proof of the Sierra-to-Casm compiler execution, showing that compiling the same class with a newer compiler version results in some new compiled class hash.
 ====
@@ -118,7 +120,7 @@ In the future, when Sierra-to-Casm compilation becomes part of the Starknet OS,
 [merkle_patricia_trie]
 == Merkle-Patricia trie
 
-The commitment scheme uses a binary Merkle-Patricia trie with the Pedersen hash function.
+The state commitment scheme uses a binary Merkle-Patricia trie with the Pedersen hash function.
 
 === About nodes
 
@@ -182,17 +184,17 @@ parent=
 [#example_trie]
 === Example trie
 
-The diagram xref:#3-level-high_trie[] illustrates  the construction of a three-level-high Merkle-Patricia trie from the leaves whose values are stem:[$(0,0,1,0,0,1,0,0)$]:
+The diagram xref:#3-level_trie[] illustrates  the construction of a three-level-high Merkle-Patricia trie from the leaves whose values are stem:[$(0,0,1,0,0,1,0,0)$]:
 
-[#3-level-high_trie]
-.A three-level-high Merkle-Patricia trie
+[#3-level_trie]
+.A three-level Merkle-Patricia trie
 image::trie.png[3-level-high Merkle-Patricia trie]
 
-Where stem:[$r=h_{Ped}(H(2,2,1),H((2,1,1))$]. Notice that the example does not skip from the root, whose length is zero, so the final commitment to the trie is stem:[$H((0,0,r))=r$].
+Where stem:[$r=h_{Ped}(H(2,2,1),H((2,1,1))$]. Notice that the example does not skip from the root, whose length is zero, so the final state commitment to the trie is stem:[$H((0,0,r))=r$].
 
-Suppose that you want to prove, with respect to the commitment just computed, that the value of the leaf whose path is given by stem:[$101$] is stem:[$1$]. In a standard Merkle trie, the proof would consist of data from three nodes, which are siblings along the path to the root.
+Suppose that you want to prove, with respect to the state commitment just computed, that the value of the leaf whose path is given by stem:[$101$] is stem:[$1$]. In a standard Merkle trie, the proof would consist of data from three nodes, which are siblings along the path to the root.
 
-In a Merkle-Patricia trie, because the trie is sparse, you only need to send the two children of the root, which are stem:[$(2,2,1)$] and stem:[$(2,1,1)$]. These two children are enough to reproduce the commitment stem:[$r$], and because you know that the height of the trie is three, and that it is fixed, you know that the path stem:[$01$] of length stem:[$2$] specified by the right-hand child, stem:[$(2,1,1)$], leads to the desired leaf.
+In a Merkle-Patricia trie, because the trie is sparse, you only need to send the two children of the root, which are stem:[$(2,2,1)$] and stem:[$(2,1,1)$]. These two children are enough to reproduce the state commitment stem:[$r$], and because you know that the height of the trie is three, and that it is fixed, you know that the path stem:[$01$] of length stem:[$2$] specified by the right-hand child, stem:[$(2,1,1)$], leads to the desired leaf.
 
 == Special addresses