docs: correct Traceroute monitor minimum frequency to 30 seconds (SIM-283)

Traceroute monitors floor at 30s; EVERY_10S/EVERY_20S are not available.

Author: danielpaulus

constructs/traceroute-monitor.mdx

@@ -231,7 +231,7 @@ new TracerouteMonitor("my-traceroute", {
 })
 ```
 
-**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_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`. Traceroute monitors do not support sub-30-second frequencies (`EVERY_10S` / `EVERY_20S`).
 </ResponseField>
 
 <ResponseField name="locations" type="string[]" default="[]">

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

@@ -95,7 +95,7 @@ The Traceroute response is available as structured JSON. All responses share thi
 
 ### Frequency
 
-Set how often the monitor runs (every 10 seconds to 24 hours).
+Set how often the monitor runs. Traceroute monitors run at most **once every 30 seconds** (every 30 seconds to 24 hours) — the two sub-30-second frequencies aren't available.
 
 ### Scheduling & Locations