diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/common-issues.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/common-issues.mdx
index 732c89439f2034..003e27713bb34f 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/common-issues.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/common-issues.mdx
@@ -191,4 +191,4 @@ Some applications require traffic to flow either all inside or all outside of th
 
 ## Troubleshooting
 
-- [Troubleshooting](/cloudflare-one/faq/troubleshooting/) - Review Troubleshooting for other WARP-related troubleshooting errors and solutions.
+- [Troubleshooting](/cloudflare-one/faq/troubleshooting/) - Browse other Cloudflare One-related troubleshooting errors and solutions.
diff --git a/src/content/docs/cloudflare-one/connections/connect-networks/index.mdx b/src/content/docs/cloudflare-one/connections/connect-networks/index.mdx
index 1e66ac3c1dc7cb..56ead972736552 100644
--- a/src/content/docs/cloudflare-one/connections/connect-networks/index.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-networks/index.mdx
@@ -14,3 +14,10 @@ Refer to our [reference architecture](/reference-architecture/architectures/sase
 Cloudflared establishes outbound connections (tunnels) between your resources and Cloudflare's global network. Tunnels are persistent objects that route traffic to DNS records. Within the same tunnel, you can run as many 'cloudflared' processes (connectors) as needed. These processes will establish connections to Cloudflare and send traffic to the nearest Cloudflare data center.
 
 ![How an HTTP request reaches a private application connected with Cloudflare Tunnel](~/assets/images/cloudflare-one/connections/connect-apps/handshake.jpg)
+
+## Next steps
+
+- Create a tunnel using the [Cloudflare dashboard](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/) or [API](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel-api/).
+- Learn more about [`cloudflared`](/cloudflare-one/connections/connect-networks/downloads/), the server-side daemon that connects your infrastructure to Cloudflare.
+- Review useful [Tunnel terms](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/) to familiarize yourself with the concepts used in Tunnel documentation.
+- [Troubleshoot](/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/) your Tunnel by reviewing available logs and common errors.
\ No newline at end of file
diff --git a/src/content/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors.mdx b/src/content/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors.mdx
index 887b7985dfeaf6..1a6a793376fa14 100644
--- a/src/content/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors.mdx
@@ -178,3 +178,7 @@ By default the [`cloudflared` Docker container](https://github.com/cloudflare/cl
 ## Cloudflare Tunnel is buffering my streaming response instead of streaming it live.
 
 Proxied traffic through Cloudflare Tunnel is buffered by default unless the origin server includes the response header `Content-Type: text/event-stream`. The `Content-Type: text/event-stream` response header tells `cloudflared` to stream data as it arrives instead of buffering the entire response.
+
+## Troubleshooting
+
+[Troubleshooting](/cloudflare-one/faq/troubleshooting/) - Browse other Cloudflare One-related troubleshooting errors and solutions.