Merge pull request #31 from OpenZeppelin/fix/window-blank-instances

fix: removed instances of window=_blank

Author: stevedylandev

content/defender/dac.mdx

@@ -34,7 +34,7 @@ There are a few ways you can set up the `serverless.yml` configuration:
 
 * Create it from scratch;
 * Use Defender’s 2.0 Serverless export capability;
-* Leverage the example [template, window=_blank](https://github.com/OpenZeppelin/defender-as-code/blob/main/template/serverless.yml) provided in the `defender-as-code` repository.
+* Leverage the example [template](https://github.com/OpenZeppelin/defender-as-code/blob/main/template/serverless.yml) provided in the `defender-as-code` repository.
 
 If you already have resources such as contracts, notifications, relayers, actions, etc. in Defender, you can export a `serverless.yml` configuration file containing these resources from the manage → advanced page.
 

content/defender/faq.mdx

@@ -8,28 +8,28 @@ OpenZeppelin Defender is the evolution of Defender, with an improved user experi
 
 New sign-ups were disabled on June 30, 2025. Until the final shutdown on July 1, 2026, Defender will remain fully operational while we focus on the open source versions of tools like Relayers and Monitor. Detailed migration guides are coming soon to help you transition seamlessly to open source.
 
-[Read more, window=_blank](https://blog.openzeppelin.com/doubling-down-on-open-source-and-phasing-out-defender)
+[Read more](https://blog.openzeppelin.com/doubling-down-on-open-source-and-phasing-out-defender)
 
 ## Once I migrate to Defender, can I continue using Defender legacy?
 
 No, once you migrate to Defender, you will no longer have access to Defender 1.0 UI and API.
 
 ## Are there any breaking changes when migrating?
 
-Yes, there are multiple changes to the API endpoints that will require you to update your integrations. You can find the API docs [here, window=_blank](https://www.api-docs.defender.openzeppelin.com/#defender-sdk).
+Yes, there are multiple changes to the API endpoints that will require you to update your integrations. You can find the API docs [here](https://www.api-docs.defender.openzeppelin.com/#defender-sdk).
 
 ## What are the pricing options for Defender?
 
-You can find the pricing for Defender [here, window=_blank](https://www.openzeppelin.com/pricing).
+You can find the pricing for Defender [here](https://www.openzeppelin.com/pricing).
 
 ## Does Defender offer support?
 
 We offer a Service Level and Support Agreement (SLA) for paid subscriptions. Learn more [here](index#sla).
 
 ## How can I get an upgrade my tenant account?
 
-You can use the billing page to upgrade your tenant account to a higher tier [here, window=_blank](https://defender.openzeppelin.com/v2/#/billing/).
+You can use the billing page to upgrade your tenant account to a higher tier [here](https://defender.openzeppelin.com/v2/#/billing/).
 
 ## Where can I see my tier quota usage?
 
-You can see your tier quota usage in the billing page [here, window=_blank](https://defender.openzeppelin.com/v2/#/billing/usage).
+You can see your tier quota usage in the billing page [here](https://defender.openzeppelin.com/v2/#/billing/usage).

content/defender/guide/factory-monitor.mdx

@@ -7,24 +7,24 @@ The factory-clone pattern can be advantageous for minimizing gas costs. However,
 This guide shows how to use Defender to monitor a factory contract as well as the clone contracts created by it. Monitor automation is achieved through the following structure of Defender modules:
 
 * A Monitor watches for successful event emitted by the factory contract that creates a clone. If detected, it triggers an [Action](module/actions) and [passes along information](module/actions#monitor_invocations) about the transaction.
-* The Action makes use of the [`defender-sdk`, window=_blank](https://www.npmjs.com/package/@openzeppelin/defender-sdk) to add the address of the newly created contract to the [address book](module/address-book) for easier monitoring.
-* Aditionally, the Action uses the [`defender-sdk`, window=_blank](https://www.npmjs.com/package/@openzeppelin/defender-sdk) to add the clone address to the list of addresses watched by a Monitor.
+* The Action makes use of the [`defender-sdk`](https://www.npmjs.com/package/@openzeppelin/defender-sdk) to add the address of the newly created contract to the [address book](module/address-book) for easier monitoring.
+* Aditionally, the Action uses the [`defender-sdk`](https://www.npmjs.com/package/@openzeppelin/defender-sdk) to add the clone address to the list of addresses watched by a Monitor.
 
-In this case, the contract ABI can be pre-supplied since clone contracts will have identical ABIs. Alternatively, you may be able to dynamically retrieve the ABI from a verified contract at a given address using [Etherscan’s API, window=_blank](https://docs.etherscan.io/api-endpoints/contracts).
+In this case, the contract ABI can be pre-supplied since clone contracts will have identical ABIs. Alternatively, you may be able to dynamically retrieve the ABI from a verified contract at a given address using [Etherscan’s API](https://docs.etherscan.io/api-endpoints/contracts).
 
 ## Generate API Key
 
-To programmatically add a contract to the address book, the [`sdk`, window=_blank](https://www.npmjs.com/package/@openzeppelin/defender-sdk) requires credentials in the form of an API key and secret. Create and copy the credentials in the [API keys page, window=_blank](https://defender.openzeppelin.com/v2/#/settings/api-keys/new).
+To programmatically add a contract to the address book, the [`sdk`](https://www.npmjs.com/package/@openzeppelin/defender-sdk) requires credentials in the form of an API key and secret. Create and copy the credentials in the [API keys page](https://defender.openzeppelin.com/v2/#/settings/api-keys/new).
 
 ![Create API credentials](/defender/guide-factory-api.png)
 
-Now, navigate to the [Secrets, window=_blank](https://defender.openzeppelin.com/v2/#/settings/secrets) page in Defender and create a new secret with the name `API_KEY` and paste in the API key. Create another secret with the name `API_SECRET` and paste in the API secret. These secrets will be used by the Action securely.
+Now, navigate to the [Secrets](https://defender.openzeppelin.com/v2/#/settings/secrets) page in Defender and create a new secret with the name `API_KEY` and paste in the API key. Create another secret with the name `API_SECRET` and paste in the API secret. These secrets will be used by the Action securely.
 
 ![Save API credentials](/defender/guide-factory-secrets.png)
 
 ## Create the Action
 
-Navigate to the [Action creation page, window=_blank](https://defender.openzeppelin.com/v2/#/actions/automatic/new?), enter a name, and select `Webhook` as trigger. Then, paste the following Action code and save it:
+Navigate to the [Action creation page](https://defender.openzeppelin.com/v2/#/actions/automatic/new?), enter a name, and select `Webhook` as trigger. Then, paste the following Action code and save it:
 
 ```jsx
 const  Defender  = require('@openzeppelin/defender-sdk');
@@ -113,7 +113,7 @@ Manually triggering this Action will be raise an error, since the Action relies
 
 ## Create the Monitor
 
-This Monitor will watch for an event emitted by the factory contract signaling that a new clone has been created. Navigate to the [Monitor creation page, window=_blank](https://defender.openzeppelin.com/v2/#/monitor/new/custom), choose a name, risk category, and select the Factory contract (add the factory if it’s not already added).
+This Monitor will watch for an event emitted by the factory contract signaling that a new clone has been created. Navigate to the [Monitor creation page](https://defender.openzeppelin.com/v2/#/monitor/new/custom), choose a name, risk category, and select the Factory contract (add the factory if it’s not already added).
 
 ![Monitor General Information](/defender/guide-factory-monitor-general-information.png)
 
@@ -129,7 +129,7 @@ As with any action, the triggering of this Monitor will be recorded in the [Logs
 
 ## Test run
 
-To test the set up, navigate to [Transaction Proposals, window=_blank](https://defender.openzeppelin.com/v2/#/transaction-proposals/new?) to manually create a clone through the factory. Select the factory contract, and call the function that creates a clone with any parameters needed.
+To test the set up, navigate to [Transaction Proposals](https://defender.openzeppelin.com/v2/#/transaction-proposals/new?) to manually create a clone through the factory. Select the factory contract, and call the function that creates a clone with any parameters needed.
 
 ![Transaction Proposal to create clone](/defender/guide-factory-create-clone.png)
 
@@ -139,7 +139,7 @@ Then, execute this this transaction with your preferred approval process, like a
 
 ## Create Monitor for clones
 
-Now that you have a clone contract to serve as a template for all future clone contracts, it’s time to create a Monitor for them. Navigate to the [Monitor creation page, window=_blank](https://defender.openzeppelin.com/v2/#/monitor/new/custom), choose a name, risk category, and select the clone contract.
+Now that you have a clone contract to serve as a template for all future clone contracts, it’s time to create a Monitor for them. Navigate to the [Monitor creation page](https://defender.openzeppelin.com/v2/#/monitor/new/custom), choose a name, risk category, and select the clone contract.
 
 Aditionally, feel free to add any other filters for transactions, events, and functions, or notifications. Save the Monitor and observe the logs/notifications to verify that the Monitor is working as expected.
 

content/defender/guide/forked-network.mdx

@@ -10,16 +10,16 @@ Defender empowers you to harness your customized network forks for deploying and
 
 ## 1. Configure your forked network
 
-You will setup a forked network on [Phalcon, window=_blank](https://phalcon.xyz) and add this network to Defender. To configure a forked network, follow these steps:
+You will setup a forked network on [Phalcon](https://phalcon.xyz) and add this network to Defender. To configure a forked network, follow these steps:
 
-1. Register an account on [Phalcon, window=_blank](https://phalcon.xyz) and create a new fork using Ethereum mainnet as the source network.
+1. Register an account on [Phalcon](https://phalcon.xyz) and create a new fork using Ethereum mainnet as the source network.
 2. Ensure anti-replay protection is activated to use a distinct chain ID for your fork, preventing conflicts with public chain IDs.
 
    ![Phalcon create a fork](/defender/tutorial-forked-network-phalcon-create.png)
 3. Copy the RPC URL and Explorer URL (this can be found under 'Scan') of your forked network. You will need it to add the network to Defender.
 
    ![Phalcon dashboard](/defender/tutorial-forked-networks-phalcon-dashboard.png)
-4. Open [Defender Forked Networks, window=_blank](https://defender.openzeppelin.com/v2/#/settings/networks/forks) in a web browser.
+4. Open [Defender Forked Networks](https://defender.openzeppelin.com/v2/#/settings/networks/forks) in a web browser.
 5. Click on **Add Forked Network**.
 
    ![Forked Networks landing page](/defender/tutorial-forked-networks-intro.png)
@@ -29,14 +29,14 @@ You will setup a forked network on [Phalcon, window=_blank](https://phalcon.xyz)
    ![Forked Networks added network](/defender/tutorial-forked-networks-create.png)
 
 <Callout>
-You may use any provider to fork a network, such as [Conduit, window=_blank](https://conduit.xyz). However, we recommend using Phalcon as it is free and easy to use.
+You may use any provider to fork a network, such as [Conduit](https://conduit.xyz). However, we recommend using Phalcon as it is free and easy to use.
 </Callout>
 
 ## 2. Configure the deploy environment
 
 You will setup a deploy environment for the forked network you just added to Defender. To configure a deploy environment, follow these steps:
 
-1. Open [Defender Deploy, window=_blank](https://defender.openzeppelin.com/v2/#/deploy) in a web browser.
+1. Open [Defender Deploy](https://defender.openzeppelin.com/v2/#/deploy) in a web browser.
 2. Click on **Setup** for your production environment (or setup a test environment if your network is forked from a testnet).
 
    ![Deploy landing page](/defender/tutorial-forked-networks-deploy-intro.png)
@@ -63,7 +63,7 @@ You should fund the relayer account with enough ETH to cover the gas costs of yo
 
 You will deploy a smart contract on the forked network you just added to Defender. To deploy a smart contract, follow these steps:
 
-1. Setup a JavaScript project and install the [defender-sdk-deploy-client, window=_blank](https://www.npmjs.com/package/@openzeppelin/defender-sdk-deploy-client) NPM package. Alternatively, you can use the [defender-sdk delpoy example script, window=_blank](https://github.com/OpenZeppelin/defender-sdk/blob/main/examples/deploy-contract/index.js) provided in the OpenZeppelin Defender SDK repository.
+1. Setup a JavaScript project and install the [defender-sdk-deploy-client](https://www.npmjs.com/package/@openzeppelin/defender-sdk-deploy-client) NPM package. Alternatively, you can use the [defender-sdk delpoy example script](https://github.com/OpenZeppelin/defender-sdk/blob/main/examples/deploy-contract/index.js) provided in the OpenZeppelin Defender SDK repository.
 2. The deployment code will look something like this:
 
    ```js
@@ -85,7 +85,7 @@ const deploymentStatus = await client.deploy.getDeployedContract(deployment.depl
 console.log(deploymentStatus);
 ```
 . Run the script to deploy the contract. **Note** that providing a `salt` will deploy the contract using `CREATE2`. Otherwise, the contract will be deployed using the `CREATE` opcode. Visit the documentation for more information on the [caveats of deployment](https://docs.openzeppelin.com/defender/tutorial/deploy#deploy-caveat).
-. Once deployed, you can track the deployment status on the [Defender Deploy dashboard, window=_blank](https://defender.openzeppelin.com/v2/#/deploy/environment/production).
+. Once deployed, you can track the deployment status on the [Defender Deploy dashboard](https://defender.openzeppelin.com/v2/#/deploy/environment/production).
 
 ## Next steps
 
@@ -100,5 +100,5 @@ After deploying a contract, we recommend creating a Monitor and setting up Actio
 * [Deploy Documentation](:module/deploy)
 * [Actions Documentation](:module/actions)
 * [Monitor Documentation](:module/monitor)
-* [Phalcon, window=_blank](https://phalcon.xyz)
-* [Conduit, window=_blank](https://conduit.xyz)
+* [Phalcon](https://phalcon.xyz)
+* [Conduit](https://conduit.xyz)