docs: correct SSL monitor minimum frequency to 1 minute (SIM-283)

SSL monitors do not offer sub-minute frequencies; the floor is 1 minute, not 10 seconds.

Author: danielpaulus

constructs/ssl-monitor.mdx

@@ -364,7 +364,7 @@ new SslMonitor("my-ssl-monitor", {
 })
 ```
 
-**Available frequencies**: `EVERY_10S`, `EVERY_20S`, `EVERY_30S`, `EVERY_1M`, `EVERY_2M`, `EVERY_5M`, `EVERY_10M`, `EVERY_15M`, `EVERY_30M`, `EVERY_1H`, `EVERY_2H`, `EVERY_3H`, `EVERY_6H`, `EVERY_12H`, `EVERY_24H`
+**Available frequencies**: `EVERY_1M`, `EVERY_2M`, `EVERY_5M`, `EVERY_10M`, `EVERY_15M`, `EVERY_30M`, `EVERY_1H`, `EVERY_2H`, `EVERY_3H`, `EVERY_6H`, `EVERY_12H`, `EVERY_24H`. SSL monitors do not support sub-minute frequencies (`EVERY_10S` / `EVERY_20S` / `EVERY_30S`).
 </ResponseField>
 
 <ResponseField name="locations" type="string[]" default="[]">

detect/uptime-monitoring/ssl-monitors/configuration.mdx

@@ -97,7 +97,7 @@ Set performance thresholds based on the TLS handshake duration:
 
 ### Frequency
 
-Set how often the monitor runs (every 10 seconds to 24 hours).
+Set how often the monitor runs. SSL monitors run at most **once per minute** (every 1 minute to 24 hours) — sub-minute frequencies aren't available, since certificate state changes slowly.
 
 ### Scheduling & Locations