Update docs/product/crons/monitor-details.mdx

Author: lizokm

docs/product/crons/monitor-details.mdx

@@ -16,18 +16,18 @@ Just below, you'll find the table of "Recent Check-Ins" which lists previously s
 
 ## Check-in Status
 
-Sentry's Cron Monitoring service can notify you and store a timeline of the following check-in events:
+Sentry's Cron Monitoring can notify you and store a timeline of the following check-in events:
 
-- **Missed check-in:** The job didn't execute in the predicted timeframe or frequency. This can happen for various reasons, such as:
-  - The job scheduler is misconfigured, skipped, or failed to initiate your job.
-  - A timeout failure event when a job sent an initial check-in but failed to send a final check-in.
-  - Network issues, such as an outbound firewall or an unstable connection.
+- **Missed check-in:** The job didn't execute within the expected timeframe or frequency because:
+  - The job scheduler is misconfigured and skipped or failed to initiate your job.
+  -  A job sent an initial check-in, but failed to send a final check-in due to a timeout failure event.
+  - There were network issues, such as an outbound firewall or an unstable connection.
   - An invalid request format.
-- **Failed check-in:** The job has reported its execution as unsuccessful.
-- **Successful check-in:** The job has reported its execution as successful.
-- **Unknown check-in:** In rare occasions, it is possible that Sentry is unable to identify a check-in status. This can happen during outages or maintenance periods.
+  
+- **Failed check-in:** The job reported its execution as unsuccessful.
+- **Successful check-in:** The job reported its execution as successful.
+- **Unknown check-in:** In rare cases, Sentry may be unable to identify a check-in status due to an outages or maintenance period.
 
-To see information about your cron monitor, select "Crons" from the sidebar menu and click on your cron monitor's name.
 
 ## Monitor State