diff --git a/site/docs/pages/xmtpkit/introduction.mdx b/site/docs/pages/xmtpkit/introduction.mdx
index a593ba875b..e1b7930a32 100644
--- a/site/docs/pages/xmtpkit/introduction.mdx
+++ b/site/docs/pages/xmtpkit/introduction.mdx
@@ -23,14 +23,14 @@ yarn add @coinbase/onchainkit @xmtp/frames-validator
 pnpm add @coinbase/onchainkit @xmtp/frames-validator
 ```
 
+:::
+
 [XMTP](https://xmtp.org/) is a wallet to wallet messaging protocol, and many XMTP client applications are adding Frames support.
 
 When a user interacts with a Frame inside an XMTP client application, you will need to handle the payload slightly differently from an interaction coming from Farcaster. The primary identifier for a user on Farcaster is the `fid`, while in XMTP it is the `verifiedWalletAddress`.
 
 You can learn more about how XMTP works with frames in [their documentation here](https://xmtp.org/docs/build/frames).
 
-:::
-
 To assist you in handling interactions from XMTP, and extracting the `verifiedWalletAddress` from a POST payload, here is the XMTP Kit which includes:
 
 - [XMTP Kit](/xmtpkit/introduction)