diff --git a/docs/architecture/accounts.md b/docs/architecture/accounts.md
index e918c3daa..30c057ce5 100644
--- a/docs/architecture/accounts.md
+++ b/docs/architecture/accounts.md
@@ -27,11 +27,11 @@ In Miden every account is a smart contract. The diagram below illustrates the ba
 
 A `~63` bits long identifier for the account ID (one field element `felt`). 
 
-The four most significant bits specify the [account type](#account-types) - regular or faucet - and the [storage mode](#account-storage-modes) - public or private.
+The four most significant bits specify the [account type](#account-types) - regular or faucet - and the account-storage-modes - public or private.
 
 ### Account data storage
 
-A storage for user-defined data that is composed of two components.
+Storage for user-defined data that is composed of two components.
 
 1. A simple sparse Merkle tree of depth `8` which is index addressable. This provides the user with `256` `word` slots.
 
@@ -91,7 +91,7 @@ There is a standard for a basic user account. It exposes three functions via its
   ```
 </details>
 
-[Note scripts](notes.md#the-note-script) or [transaction scripts](transactions/kernel.md#the-transaction-script-processing) can call `receive_asset` and `send_asset`. 
+[Note scripts](notes.md#the-note-script) or transaction scripts can call `receive_asset` and `send_asset`. 
 
 Transaction scripts can also call `auth_tx_rpo_falcon512` and authenticate the transaction. 
 
diff --git a/docs/architecture/notes.md b/docs/architecture/notes.md
index 12b6640cf..7f3b081d9 100644
--- a/docs/architecture/notes.md
+++ b/docs/architecture/notes.md
@@ -25,7 +25,7 @@ The concept of notes is a key divergence from Ethereum’s account-based model.
 
 New notes are created by executing transactions. 
 
-After verifying the transaction proof the operator adds either only the note hash (private notes) or the full note data (public notes) to the [note database](state.md#notes-database). 
+After verifying the transaction proof the operator adds either only the note hash (private notes) or the full note data (public notes) to the note database. 
 
 Notes can be produced and consumed locally by users in local transactions or by the operator in a network transaction. 
 
diff --git a/docs/architecture/state.md b/docs/architecture/state.md
index 4dc09d900..bbb55217b 100644
--- a/docs/architecture/state.md
+++ b/docs/architecture/state.md
@@ -41,7 +41,7 @@ The latest account states - and data for on-chain accounts - are recorded in a s
 ![Architecture core concepts](../img/architecture/state/account-db.png){ width="80%" }
 </center>
 
-As described in the [accounts section](accounts.md##account-storage-modes), there are two types of accounts:
+As described in the [accounts section](accounts.md), there are two types of accounts:
 
 * Public accounts where all account data is stored on-chain.
 * Private accounts where only the hashes of accounts are stored on-chain.
@@ -61,7 +61,7 @@ Notes are recorded in an append-only accumulator, a [Merkle Mountain Range](http
 ![Architecture core concepts](../img/architecture/state/note-db.png){ width="80%" }
 </center>
 
-As described in [the notes section](notes.md#note-storage-modes), there are two types of notes:
+As described in [the notes section](notes.md, there are two types of notes:
 
 * Public notes where the entire note content is recorded in the state.
 * Private notes where only a note's hash is recorded in the state.