diff --git a/components/StarkNet/modules/architecture_and_concepts/pages/Account_Abstraction/deploying_new_accounts.adoc b/components/StarkNet/modules/architecture_and_concepts/pages/Account_Abstraction/deploying_new_accounts.adoc
index 559be180c1..1cee06d443 100644
--- a/components/StarkNet/modules/architecture_and_concepts/pages/Account_Abstraction/deploying_new_accounts.adoc
+++ b/components/StarkNet/modules/architecture_and_concepts/pages/Account_Abstraction/deploying_new_accounts.adoc
@@ -1,9 +1,8 @@
 [id="deploying_new_accounts"]
 = Deploying new accounts
 
-Since xref:documentation:starknet_versions:version_notes.adoc#version0.10.1[StarkNet version 0.10.1] the historical method of deploying accounts on StarkNet, the `deploy` transaction, has been removed.
-
-It has now been replaced with the `deploy_account` transaction which allows you to deploy an account and pay fees from a pre-funded address (thus solving the issue of how to pay fees while not yet having a deployed account).
+Starknet provides the `deploy_account` transaction in order to deploy new accounts to the
+network.
 
 ## Deploy account transaction
 
diff --git a/components/StarkNet/modules/architecture_and_concepts/pages/Fees/fee-mechanism.adoc b/components/StarkNet/modules/architecture_and_concepts/pages/Fees/fee-mechanism.adoc
index 17886d8426..f4f4288c70 100644
--- a/components/StarkNet/modules/architecture_and_concepts/pages/Fees/fee-mechanism.adoc
+++ b/components/StarkNet/modules/architecture_and_concepts/pages/Fees/fee-mechanism.adoc
@@ -15,7 +15,8 @@ The only limitation on the sequencer (enforced by the Starknet OS) is that the a
 Presently, the sequencer only takes into account L1 costs involving proof submission. There are two components affecting the L1 footprint of a transaction:
 
 * xref:computation[Computational complexity]: the heavier the transaction, the larger its portion in the proof verification cost.
-* xref:on-chain-data[On chain data]: L1 calldata cost originating from xref:../Data_Availability/on_chain_data.adoc[data availability] and L2→L1 messages.
+* xref:on-chain-data[On chain data]: L1 calldata cost originating from xref:Data_Availability/on-chain-data.adoc[data availability]
+and L2→L1 messages.
 
 == Fee Units
 
@@ -98,7 +99,8 @@ The on chain data associated with a transaction is composed of three parts
 
 ==== Storage Updates
 
-Whenever a transaction updates a key at the storage of some contract, the following xref:../Data_Availability/on-chain-data.adoc[data] reaches L1:
+Whenever a transaction updates a key at the storage of some contract, the following xref:Data_Availability/on-chain-data.adoc[data]
+reaches L1:
 
 * Contract_address
 * Number of updated keys in that contract