clarify secrets usage in CLI docs and monitoring overview.

Author: drakirnosslin

site/content/docs/cli/using-environment-variables.md

@@ -146,7 +146,7 @@ npx checkly env ls
 Create a new variable.
 
 ```bash
-npx checkly env add  MY_PASSWORD 123test --locked
+npx checkly env add  MY_PASSWORD 123test --secret
 ```
 
 Pull in the variables from your account and store them in a file.
@@ -171,5 +171,6 @@ For storing and securing environment variables, we advise the following:
 1. Store local environment variables in your shell or in `.env` files that are not committed to your git repo. Add those
 files to your `.gitignore` file.
 2. In a CI context, e.g. GitHub Actions, store sensitive variables as secrets. Almost all CI providers have such a feature.
-3. For remote variables, store sensitive secrets at the Account level and click the lock icon so Read Only users cannot view them.
+3. For remote variables, store sensitive data as secrets in Checkly. For more information on how to manage secrets in Checkly see [variables and secrets](/docs/browser-checks/variables).
+
 All variables are stored encrypted at rest and in transfer.

site/content/docs/monitoring/storing-secrets.md

@@ -12,10 +12,10 @@ Here are our guidelines on using secrets with Checkly:
 **1. Use dedicated test users, test cards** etc. These test users should have minimal privileges in your app. Do not use your 
 `admin` or `root` user. Make sure you can easily disable or block these users without recourse.
 
-**2. Keep secrets separate** from your browser scripts and store them as environment variables in Checkly. This 
+**2. Keep secrets separate** from your browser scripts and store them as environment secrets in Checkly. This 
 way you can reuse secrets in multiple scripts and rotate them as needed.
 
 **3. Checkly encrypts your secrets**: at rest in the database and in flight as we transport it to the check locations. 
 Decryption is only done when we need to read it.
 
-
+To learn how to create and manage variables and secrets in Checkly see see [variables and secrets](/docs/browser-checks/variables).