docs: fix Traceroute private locations — monitors support public and private locations

Remove incorrect statement that private locations are unsupported;
update the Scheduling & Locations bullet to match ICMP/TCP docs.

Author: danielpaulus

constructs/traceroute-monitor.mdx

@@ -235,7 +235,7 @@ new TracerouteMonitor("my-traceroute", {
 </ResponseField>
 
 <ResponseField name="locations" type="string[]" default="[]">
-Array of [public location codes](/concepts/locations/#public-locations) where the Traceroute Monitor should run from. Multiple locations help detect regional routing differences.
+Array of [public location codes](/concepts/locations/#public-locations) where the Traceroute Monitor should run from. Use `privateLocations` for [private locations](/platform/private-locations/overview). Multiple locations help detect regional routing differences.
 
 **Usage:**
 

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

@@ -100,7 +100,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours).
 ### Scheduling & Locations
 
 * **Strategy:** Choose between round-robin or parallel execution. Learn more about [scheduling strategies](/concepts/scheduling)
-* **Locations:** Select [public locations](/concepts/locations/#public-locations) to run the monitor from
+* **Locations:** Select [public](/concepts/locations/#public-locations) or [private](/platform/private-locations/overview) locations to run the monitor from
 
 ### Additional Settings