XMTP V3 alpha docs for building an inbox

docs/pages/consent/broadcast.md

@@ -5,9 +5,9 @@ Broadcasting with XMTP allows you to send a single message to multiple recipient
 ## Prerequisites
 
 - Wallet is XMTP-enabled  
-Before sending a broadcast message, [use `canMessage`](/get-started/developer-quickstart#check-if-the-recipient-address-is-xmtp-enabled) to verify that each recipient's wallet is enabled on the XMTP network. Only XMTP-enabled wallets can receive and view messages.
+Before sending a broadcast message, [use `canMessage`](https://docs.xmtp.org/get-started/developer-quickstart#check-if-the-recipient-address-is-xmtp-enabled) to verify that each recipient's wallet is enabled on the XMTP network. Only XMTP-enabled wallets can receive and view messages.
 - User consent  
-In accordance with data privacy laws, [obtain explicit consent](/consent/user-consent) from users before sending them broadcast messages.
+In accordance with data privacy laws, [obtain explicit consent](/inboxes/support-consent) from users before sending them broadcast messages.
 
 :::warning
 Broadcast messages delivered to users who haven't provided explicit consent to receive them are more likely to be treated as spam, which significantly reduces the chances that recipients will see them.

docs/pages/consent/build-engagement.mdx

@@ -10,7 +10,7 @@ Here are examples of these features at work in real-world scenarios, delivering
 
 ## Engage and reengage your audience with subscriptions
 
-Put a **Subscribe** button built with XMTP on your site, in your app, or anywhere you want to invite people to receive your newsletters, alerts, and any other [content type](/content-types/content-types) that can be delivered in a message.
+Put a **Subscribe** button built with XMTP on your site, in your app, or anywhere you want to invite people to receive your newsletters, alerts, and any other [content type](https://docs.xmtp.org/content-types/content-types) that can be delivered in a message.
 
 When a user clicks Subscribe, they’re signed up to receive your messages in the inbox associated with their connected wallet address.
 
@@ -76,10 +76,10 @@ Your inbox for the sending wallet address provides access to secure, private, an
 With these use cases for subscriptions, user consent, and broadcasts in mind, it’s time to build and start fostering quality engagement with your audience through trusted and scalable messaging.
 
 - To learn to build a subscribe button with user consent, see [Enable subscriptions using consent proofs](/consent/subscribe).
-- To learn more about how user consent works, see [Understand user consent preferences](/consent/user-consent).
+- To learn more about how user consent works, see [Understand user consent preferences](/inboxes/support-consent).
 - To learn how to send broadcast messages, see [Broadcast messages](/consent/broadcast).
 
-Want to explore code in consent, subscribe, and broadcast quickstart repos? See [Quickstart repos for building audience engagement](/consent/consent-quickstarts)
+Want to explore code in consent, subscribe, and broadcast quickstart repos? See [Quickstart repos for building audience engagement](#TODO)
 
 Prefer to use a ready-made solution? Consider using a third-party service, such as: