diff --git a/docs/zkapps/zkapp-development-frameworks.mdx b/docs/zkapps/zkapp-development-frameworks.mdx
index 1a1ad9c25..7d1470fe9 100644
--- a/docs/zkapps/zkapp-development-frameworks.mdx
+++ b/docs/zkapps/zkapp-development-frameworks.mdx
@@ -39,7 +39,7 @@ There are some key considerations when choosing to build a zkApp with o1js on Mi
   - Where more than the eight on-chain field elements are required to manage state, and access to that state is not shared between users, the experimental [Offchain Storage API](/zkapps/writing-a-zkapp/feature-overview/offchain-storage) offers a solution.
   - Where concurrent access to _shared global state_ is required, the required architecture is available **out of the box** when using the Protokit framework to build your zkApp as an zkApp-chain (L2). There is currently no easy-to-use equivalent for shared state in o1js L1 contracts.
 
-Start here
+Start here:
 
 - [Developer documentation](/zkapps/o1js)
 - [o1js repository](https://github.com/o1-labs/o1js)