diff --git a/docs/guides/README.md b/docs/guides/README.md
index a00cc83e280c91..72ad547975c32e 100644
--- a/docs/guides/README.md
+++ b/docs/guides/README.md
@@ -40,10 +40,6 @@
 -   [Open Thread - Hardware suggestions](./openthread_rcp_nrf_dongle.md)
 -   [Open Thread - Setting up a Pi as a border router](./openthread_border_router_pi.md)
 
-## Troubleshooting Guides
-
--   [Avahi - Troubleshooting](./troubleshooting_avahi.md)
-
 ## Tool Guides
 
 -   [chip-tool](./chip_tool_guide.md)
diff --git a/docs/testing/integration_test_utilities.md b/docs/testing/integration_test_utilities.md
index e50ad511caa28b..019a3cf44bc29b 100644
--- a/docs/testing/integration_test_utilities.md
+++ b/docs/testing/integration_test_utilities.md
@@ -6,9 +6,10 @@ on devices for the purposes of testing.
 When using any of these utilities it is important to inject the errors at the
 point where they are running through the MOST code that they can.
 
-If the cluster uses the [ClusterLogic](./unit_testing_clusters.md) pattern, this
-means injecting errors as close as possible to the driver layer, rather than
-catching errors in the server.
+If the cluster uses the
+[ClusterLogic](../cluster_and_device_type_dev/unit_testing_clusters.md) pattern,
+this means injecting errors as close as possible to the driver layer, rather
+than catching errors in the server.
 
 ## TestEventTriggers