diff --git a/docs/product/insights/requests.mdx b/docs/product/insights/requests.mdx
index 44b04ac56fb80..85a745814352d 100644
--- a/docs/product/insights/requests.mdx
+++ b/docs/product/insights/requests.mdx
@@ -24,6 +24,8 @@ On the [**Requests** page](#requests-page), you get an overview of the domains t
   ></iframe>
 </div>
 
+<br />
+
 ## Prerequisites and Limitations
 
 <Note>
@@ -32,7 +34,12 @@ Network requests using non-HTTP protocols (FTP, WebSocket, etc.) are not support
 
 Availability of HTTP request monitoring depends on the SDK your application uses. In most cases, Sentry's SDKs automatically enable HTTP request tracking. You can check your SDK's <PlatformLink to="/tracing/instrumentation/automatic-instrumentation">automatic instrumentation documentation</PlatformLink> to see if it includes tracking HTTP requests.
 
-If the SDK you're using doesn't automatically instrument HTTP requests, you can instrument your application by following the <PlatformLink to="/tracing/instrumentation/custom-instrumentation/">custom instrumentation</PlatformLink> instructions. Because all the concepts are the same, if your platform doesn't have dedicated custom instrumentation instructions, you can try adapting the code from another platform.
+If the SDK you're using doesn't automatically instrument HTTP requests, you can set up custom instrumentation. Dedicated platform documentation is available for these platforms:
+
+- [Python SDK](/platforms/python/tracing/instrumentation/custom-instrumentation/requests-module/)
+- [JavaScript SDK](/platforms/javascript/guides/node/tracing/instrumentation/custom-instrumentation/requests-module/)
+
+If your platform doesn't have dedicated custom instrumentation instructions, you can try adapting the code from one of the supported platforms. In addition, you can also reference the [Requests Modules SDK development guide](https://develop.sentry.dev/sdk/performance/modules/requests/), which lists required span properties and their expected format.
 
 ## Requests Page