diff --git a/troubleshoot/ingest/opentelemetry/edot-collector/enable-debug-logging.md b/troubleshoot/ingest/opentelemetry/edot-collector/enable-debug-logging.md
index c421b690b7..fa94469390 100644
--- a/troubleshoot/ingest/opentelemetry/edot-collector/enable-debug-logging.md
+++ b/troubleshoot/ingest/opentelemetry/edot-collector/enable-debug-logging.md
@@ -86,3 +86,6 @@ Debug logging for the Collector is not currently configurable through {{fleet}}.
 :::
 
 
+## Resources
+
+To learn how to enable debug logging for the EDOT SDKs, refer to [Enable debug logging for EDOT SDKs](../edot-sdks/enable-debug-logging.md).
diff --git a/troubleshoot/ingest/opentelemetry/edot-sdks/enable-debug-logging.md b/troubleshoot/ingest/opentelemetry/edot-sdks/enable-debug-logging.md
index f1702e2f9a..fa7f7ac1fc 100644
--- a/troubleshoot/ingest/opentelemetry/edot-sdks/enable-debug-logging.md
+++ b/troubleshoot/ingest/opentelemetry/edot-sdks/enable-debug-logging.md
@@ -27,7 +27,8 @@ Enabling debug logging can help surface common problems such as:
 
 ## Verify you're looking at the right logs
 
-* Ensure you’re checking logs for the same process that starts your app (systemd service, container entrypoint, IIS worker, etc.).
+Ensure you’re checking logs for the same process that starts your app (systemd service, container entrypoint, IIS worker, and so on):
+
 * For containerized environments such as Kubernetes/Docker:  
   * `kubectl logs <pod> -c <container>` (correct container name matters if there are sidecars)  
   * Check the new Pod after a rollout, as old Pods may show stale environment without your debug flags.