chore: Docs improvements

Author: NicoMolinaOZ

content/defender/index.mdx

@@ -11,6 +11,17 @@ New sign-ups were disabled on June 30, 2025. Until the final shutdown on July 1,
 
 </Callout>
 
+<Callout type='info' title='Migration Guides Available'>
+
+We have comprehensive migration guides to help you transition:
+
+- **[Migrate from Defender Monitor to OpenZeppelin Monitor](/defender/migration#monitor-migration)** - Export configurations, set up infrastructure, and test your monitors
+- **[Migrate from Defender Relayer to OpenZeppelin Relayer](/defender/migration#relayer-migration)** - Transfer relayers, update SDK integration, and migrate transaction handling
+
+View the complete [Migration Guide](/defender/migration) for detailed instructions.
+
+</Callout>
+
 OpenZeppelin Defender is a mission-critical developer security platform to **code**, **audit**, **deploy**, **monitor**, and **operate** blockchain applications with confidence.
 
 Integrating directly into the developer workflow, Defender makes it easy and fast for developers and operators to prevent and fix security issues pre and post-deployment.

content/defender/migration.mdx

@@ -7,8 +7,8 @@ title: Migrating from Defender to Open Source
 Defender is now in maintenance mode. To continue using monitoring and relaying capabilities with the latest features and updates, we recommend migrating to OpenZeppelin's open source tools.
 
 This guide covers:
-- Migrating from **Defender Monitor** to [OpenZeppelin Monitor](/monitor/1.1.x)
-- Migrating from **Defender Relayer** to [OpenZeppelin Relayer](/relayer/1.2.x)
+- Migrating from **Defender Monitor** to [OpenZeppelin Monitor](/monitor)
+- Migrating from **Defender Relayer** to [OpenZeppelin Relayer](/relayer)
 
 Both tools are designed to be self-hosted, giving you full control over your infrastructure while maintaining the functionality you rely on.
 
@@ -32,9 +32,9 @@ Both tools are designed to be self-hosted, giving you full control over your inf
 
 ## Monitor Migration
 
-### From Defender Monitor to OpenZeppelin Open Source Monitor
+### From Defender Monitor to OpenZeppelin Monitor
 
-The open source Monitor offers similar functionality to Defender Monitor:
+OpenZeppelin Monitor offers similar functionality to Defender Monitor:
 
 - **Event and function monitoring**: Monitor smart contract events and function calls
 - **Custom filtering**: Write custom JavaScript, Python or Bash filters to match specific conditions
@@ -45,20 +45,20 @@ The open source Monitor offers similar functionality to Defender Monitor:
 To begin your Monitor migration:
 
 1. **Review your existing monitors**: Export your Defender Monitor configurations using the "Download OpenZeppelin Monitor Configurations" button
-2. **Import your configurations**: Use the exported configurations to recreate your monitors in the open source version
-3. **Set up the open source Monitor**: Follow the [installation guide](/monitor/1.1.x) to deploy Monitor on your infrastructure
+2. **Import your configurations**: Use the exported configurations to recreate your monitors in OpenZeppelin Monitor
+3. **Set up OpenZeppelin Monitor**: Follow the [installation guide](/monitor) to set up the Monitor.
 
 ![Defender Monitor Migration Button](/defender/monitor-migration-information.png)
 
-The "Download OpenZeppelin Monitor Configurations" button will download a .zip file containing configuration files for every active monitor in your Defender account. These configurations are ready to copy and paste directly into the open source Monitor. Before running the monitors, make sure to review and update any placeholder values in the configuration files, such as:
+The "OpenZeppelin Monitor Configurations" button will download a .zip file containing configuration files for every monitor in your Defender account (if you don't have to download some monitor, first delete it). These configurations are ready to copy and paste directly into OpenZeppelin Monitor. Before running the monitors, make sure to review and update any placeholder values in the configuration files, such as:
 
 - API keys and secrets
 - RPC URLs and endpoint addresses
 - Webhook URLs for notifications
 - Service integration credentials (Slack, Telegram, Discord, etc.)
 
 <Callout type='warn'>
-Custom Actions attached to your Defender monitors will not be automatically migrated. You will need to manually recreate any custom action logic following the [OpenZeppelin Monitor documentation](/monitor/1.1.x) for trigger handlers and custom notifications.
+Custom Actions attached to your Defender monitors will not be automatically migrated. You will need to manually recreate any custom action logic following the [OpenZeppelin Monitor documentation](/monitor) for trigger handlers and custom notifications.
 </Callout>
 
 Alternatively, if you don't want to download all monitor configurations at once, you can navigate to each individual monitor and download its configuration separately. This gives you more control over which monitors to migrate and when.
@@ -69,15 +69,15 @@ Here's a video with the process step by step: https://www.loom.com/share/6de3d26
 
 4. **Test your monitors**: Verify that alerts trigger correctly before decommissioning Defender monitors
 
-For detailed migration instructions and support, visit the [OpenZeppelin Monitor documentation](/monitor/1.1.x).
+For detailed migration instructions and support, visit the [OpenZeppelin Monitor documentation](/monitor).
 
 ---
 
 ## Relayer Migration
 
-### From Defender Relayer to OpenZeppelin Open Source Relayer
+### From Defender Relayer to OpenZeppelin Relayer
 
-The open source Relayer offers similar functionality to Defender Relayer:
+OpenZeppelin Relayer offers similar functionality to Defender Relayer:
 
 - **Transaction relaying**: Submit transactions to supported blockchain networks efficiently
 - **Transaction signing**: Securely sign transactions using configurable key management
@@ -91,22 +91,22 @@ The open source Relayer offers similar functionality to Defender Relayer:
 
 To begin your Relayer migration:
 
-1. **Review your existing relayers**: Export your Defender Relayer configurations using the "Download OpenZeppelin Relayer Configurations" button
+1. **Review your existing relayers**: Export your Defender Relayer configurations using the "OpenZeppelin Relayer Configurations" button
 
-The "Download OpenZeppelin Relayer Configurations" button will download a .zip file containing configuration files for every active relayer in your Defender account. These configurations are ready to copy and paste directly into the open source Relayer. Before running the relayers, make sure to review and update any placeholder values in the configuration files, such as:
+![Defender Relayer Migration Button](/defender/relayer-migration-button.png)
 
-![Defender Relayer Migration Button](/defender/defender-relayer-migration-button.png)
+The "Download OpenZeppelin Relayer Configurations" button will download a .zip file containing configuration files for every relayer in your Defender account (if you don't want to download some relayer, first delete it). These configurations are ready to copy and paste directly into OpenZeppelin Relayer. Before running the relayers, make sure to review and update any placeholder values in the configuration files, such as:
 
-2. **Set up the open source Relayer**: Follow the [installation guide](/relayer/1.2.x) to deploy the Relayer on your infrastructure
-3. **Import your configurations**: Use the exported configurations to recreate your relayers in the open source version
+2. **Set up OpenZeppelin Relayer**: Follow the [installation guide](/relayer) to deploy the Relayer on your infrastructure
+3. **Import your configurations**: Use the exported configurations to recreate your relayers in OpenZeppelin Relayer
 
 - RPC URLs and endpoint addresses
 - Signer configurations and private keys
 - Network-specific policies
 - Webhook URLs for notifications
 
 4. **Test your relayers**: Verify that transactions are processed correctly before decommissioning Defender relayers
-5. **Transfer funds**: Once your open source relayers are fully configured and running, transfer the funds from your Defender relayers to your new open source relayer addresses using the Withdraw functionality
+5. **Transfer funds**: Once your OpenZeppelin Relayers are fully configured and running, transfer the funds from your Defender relayers to your new OpenZeppelin Relayer addresses using the Withdraw functionality
 6. **Gradually move volume**: Shift traffic from Defender relayer to OpenZeppelin Relayer incrementally
 
 Here's a video with the process step by step: https://www.loom.com/share/cb5e0f5d8c064a71abc8c18fac273cf0
@@ -236,15 +236,15 @@ const relayers = await relayerApi.listRelayers();
 | `relayer.getRelayer()` | `relayerApi.getRelayer()` |
 | `relayer.getRelayerStatus()` | `relayerApi.getRelayerStatus()` |
 
-For detailed migration instructions and support, visit the [OpenZeppelin Relayer documentation](/relayer/1.2.x).
+For detailed migration instructions and support, visit the [OpenZeppelin Relayer documentation](/relayer).
 
 ---
 
 ## Support and Resources
 
 ### Documentation
-- [OpenZeppelin Monitor Documentation](/monitor/1.1.x)
-- [OpenZeppelin Relayer Documentation](/relayer/1.2.x)
+- [OpenZeppelin Monitor Documentation](/monitor)
+- [OpenZeppelin Relayer Documentation](/relayer)
 
 ### Getting Help
 If you encounter issues during migration or have questions:
@@ -259,7 +259,7 @@ Use this checklist to track your migration progress:
 #### Monitor Migration
 - [ ] Export Monitor configurations from Defender
 - [ ] Review and update placeholder values (API keys, RPC URLs, etc.)
-- [ ] Set up open source Monitor infrastructure
+- [ ] Set up OpenZeppelin Monitor infrastructure
 - [ ] Import and configure monitors
 - [ ] Recreate custom action logic
 - [ ] Test alert triggers
@@ -269,12 +269,12 @@ Use this checklist to track your migration progress:
 #### Relayer Migration
 - [ ] Export Relayer configurations from Defender
 - [ ] Review and update placeholder values (signers, RPC URLs, policies)
-- [ ] Set up open source Relayer infrastructure
+- [ ] Set up OpenZeppelin Relayer infrastructure
 - [ ] Import and configure relayers
 - [ ] Update SDK integration code (if applicable)
 - [ ] Test transaction processing
 - [ ] Run in parallel with Defender Relayers
 - [ ] Transfer funds from Defender Relayers
-- [ ] Gradually move traffic to open source Relayers
+- [ ] Gradually move traffic to OpenZeppelin Relayers
 - [ ] Decommission Defender Relayers
 

content/defender/module/monitor.mdx

@@ -2,6 +2,14 @@
 title: Monitor
 ---
 
+<Callout type='warn' title='Defender is in Maintenance Mode'>
+
+Defender is now in maintenance mode. To continue monitoring your smart contracts with the latest features and updates, we recommend migrating to [OpenZeppelin Monitor](/monitor).
+
+See the complete [Migration Guide](/defender/migration#monitor-migration) for detailed instructions on exporting your configurations.
+
+</Callout>
+
 Monitors allow you to gain full visibility into your smart contracts' risks and behaviors. You can detect threats, get alerts on threats and anomalies, and automatically respond and resolve issues.
 
 ## Use cases
@@ -443,10 +451,3 @@ Saving a monitor as a template stores its configuration and parameters, which ca
 We provide a quickstart tutorial to monitor a smart contract using Defender. Check it out [here](/defender/tutorial/monitor)!
 </Callout>
 
-## Migration to Open Source
-
-<Callout type='warn'>
-Defender is now in maintenance mode. To continue monitoring your smart contracts with the latest features and updates, we recommend migrating to the [OpenZeppelin open source Monitor](/monitor/1.1.x).
-
-See the complete [Migration Guide](/defender/migration#monitor-migration) for detailed instructions on exporting your configurations, setting up the open source Monitor, and testing your migration.
-</Callout>

content/defender/module/relayers.mdx

@@ -2,7 +2,15 @@
 title: Relayers
 ---
 
-Relayers allow you to send on-chain transactions via regular API requests or through other Defender modules, like Actions, Workflows, and Deploy. Relayers also automate the payment of gas fees and take care of private key secure storage, transaction signing, nonce management, gas pricing estimation, and resubmissions. With Relayers, you don’t have to worry about storing private keys on your back-end servers or monitoring gas prices and transactions to ensure they get confirmed.
+<Callout type='warn' title='Defender is in Maintenance Mode'>
+
+Defender is now in maintenance mode. To continue relaying transactions with the latest features and updates, we recommend migrating to [OpenZeppelin Relayer](/relayer).
+
+See the complete [Migration Guide](/defender/migration#relayer-migration) for detailed instructions on exporting your configurations.
+
+</Callout>
+
+Relayers allow you to send on-chain transactions via regular API requests or through other Defender modules, like Actions, Workflows, and Deploy. Relayers also automate the payment of gas fees and take care of private key secure storage, transaction signing, nonce management, gas pricing estimation, and resubmissions. With Relayers, you don't have to worry about storing private keys on your back-end servers or monitoring gas prices and transactions to ensure they get confirmed.
 
 ## Use cases
 
@@ -725,11 +733,3 @@ When sending transactions to a rollup chain, such as Arbitrum or Optimism, Relay
 ## Inactivity
 
 Testnet relayers are considered inactive if they haven’t sent any transactions in more than 60 days. When a testnet relayer is inactive, we provide a 14-day grace period to mark the relayer as active. If users don’t take any action, the relayer will be automatically deleted once the period is over.
-
-## Migration to Open Source
-
-<Callout type='warn'>
-Defender is now in maintenance mode. To continue relaying transactions with the latest features and updates, we recommend migrating to the [OpenZeppelin open source Relayer](/relayer/1.2.x).
-
-See the complete [Migration Guide](/defender/migration#relayer-migration) for detailed instructions on exporting your configurations, setting up the open source Relayer, SDK migration, and testing your migration.
-</Callout>