comment out broken links

Signed-off-by: Jess Chitas <[email protected]>

Author: jessicachitas

docs/developer/architecture/alerts.md

@@ -291,7 +291,7 @@ The alert exporter exposes comprehensive metrics on port 8081:
 - Checkpoint operation metrics
 - System health and uptime
 
-See [metrics.md](../metrics.md) for complete metrics documentation.
+<!-- See [metrics.md](../metrics.md) for complete metrics documentation. -->
 
 ### Logging
 

docs/user/managing-devices.md

@@ -716,7 +716,7 @@ The Flight Control Agent comes with a built-in set of rules defined in `/usr/lib
 
 You can set up monitors for device resources and define alerts when the utilization of these resources crosses a defined threshold. When the agent alerts the Flight Control service, the service sets the device status to "degraded" or "error" (depending on the severity level) and may suspend the rollout of updates and alarm the user as a result.
 
-Note this is not meant to replace an observability solution. If your use case requires streaming logs and metrics from devices into an observability stack and the device's network bandwidth allows this, see [Adding Device Observability](adding-device-observability.md) for ways to approach that.
+<!-- Note this is not meant to replace an observability solution. If your use case requires streaming logs and metrics from devices into an observability stack and the device's network bandwidth allows this, see [Adding Device Observability](adding-device-observability.md) for ways to approach that. -->
 
 Resource monitors take the following parameters: