docs: clarify Defender Deploy Environment API keys

Author: robaribas

docs/modules/ROOT/pages/defender-deploy.adoc

@@ -17,6 +17,8 @@ module.exports = {
 }
 ----
 
+NOTE: The API Key and Secret referenced above are specifically for the Production or Test Deploy Environment that you configured in Defender. You can obtain these from the Deploy module in Defender when setting up your environment. For more information, see https://docs.openzeppelin.com/defender/tutorial/deploy#environment_setup.
+
 [[network-selection]]
 == Network Selection
 

docs/modules/ROOT/pages/foundry/pages/foundry-defender.adoc

@@ -26,14 +26,16 @@ extra_output = ["storageLayout"]
 NOTE: Metadata must also be included in the compiler output, which it is by default.  
 
 [start=3]
-3. Set the following environment variables in your `.env` file at your project root, using your Team API key and secret from OpenZeppelin Defender:
+3. Set the following environment variables in your `.env` file at your project root, using your Team API key and secret from the OpenZeppelin Defender Deploy Environment (either Production or Test) that you configured:
 
 [source]
 ----
 DEFENDER_KEY=<Your API key>
 DEFENDER_SECRET=<Your API secret>
 ----
 
+NOTE: These API keys are specifically for the Deploy Environment (Production or Test) that you configured in Defender. You can obtain these keys from the Deploy module in Defender during the environment setup process. For more information, see https://docs.openzeppelin.com/defender/tutorial/deploy#environment_setup.
+
 == Network Selection
 
 The network that is used with OpenZeppelin Defender is determined by the network that Foundry is connected to.