diff --git a/docs/zkapps/writing-a-zkapp/introduction-to-zkapps/how-zkapps-work.mdx b/docs/zkapps/writing-a-zkapp/introduction-to-zkapps/how-zkapps-work.mdx
index 3fb94639c..10c369141 100644
--- a/docs/zkapps/writing-a-zkapp/introduction-to-zkapps/how-zkapps-work.mdx
+++ b/docs/zkapps/writing-a-zkapp/introduction-to-zkapps/how-zkapps-work.mdx
@@ -123,7 +123,7 @@ The end user's privacy is maintained because their interaction occurs locally in
 
 ### How state is updated on-chain
 
-The zkApp account gets updated on-chain. See [How state is updated on-chain](/zkapps/writing-a-zkapp/introduction-to-zkapps/how-zkapps-work#how-state-is-updated-on-chain)
+The zkApp account gets updated on-chain. 
 
 When the prover function runs in a web browser, the smart contract outputs a proof and some associated data called "account updates" that are sent to a zkApp address as part of the transaction. The account updates are a JSON plain text description that describes how to update the state on a zkApp account.