feat(crons): Add product docs for environments (#6679)

Co-authored-by: Liza Mock <[email protected]>

Author: evanpurkhiser

src/docs/product/crons/getting-started/cli.mdx

@@ -54,3 +54,9 @@ sentry-cli monitors run my-monitor-slug -- python path/to/file.py
 ```bash {tabTitle: Node.JS}
 sentry-cli monitors run my-monitor-slug -- node path/to/file.js
 ```
+
+### Specifying Monitor Environments (Optional)
+
+<Alert level="info">
+    The `sentry-cli` doesn't currently support the ability to specify monitor environment for check-ins.
+</Alert>

src/docs/product/crons/job-monitoring.mdx

@@ -21,7 +21,27 @@ This is where you'll find a daily historical bar chart showing successful, faile
 
 The "Issues" section shows the issues created from this Cron Monitor. Issues are created when a cron monitor job execution is missed or failed. If you have configured the Sentry SDK for your job, any errors thrown during the job runtime will be shown here as well.
 
-The table of recent check-ins lists previously scheduled jobs and their status.
+The table of recent check-ins lists previously scheduled jobs and their statuses.
+
+## Multiple Environments
+
+To monitor the same job in different environments, use a shared schedule to send check-ins for multiple environments to one monitor. Each environment will have its own status and set of check-ins.
+
+### Alerting on Specific Environments
+
+To only receive failing or missed monitor alerts for a specific environment or set of environments, [configure the
+environment](/product/alerts/create-alerts/issue-alert-config/#environment) for
+your monitor alert.
+
+### Existing Limitations:
+
+- It's not currently possible to pause an individual monitor environment.
+
+- It's not currently possible to see an aggregate view of a monitors' status
+  across all environments. Each environment will appear as its own row in the
+  monitor list.
+
+- Currently, only entire monitors can be removed. Individual monitor environments can't be deleted. 
 
 ## Pausing Your Cron Monitor
 

src/docs/product/security-policy-reporting.mdx

@@ -62,7 +62,8 @@ In addition to the `sentry_key` parameter, you may also pass the following withi
 
 `sentry_environment`
 
-: The environment name (e.g. production). The environment name can't contain newlines, spaces, or forward slashes, can't be the string "None", or exceed 64 characters. Also, environments are case sensitive.
+: The environment name (for example, production). 
+The environment name is case sensitive, can't contain new lines, spaces, or forward slashes. It can't be the string "None" or exceed 64 characters. 
 
 `sentry_release`