[PROF-13394] Improve setup source code integration documentation

content/en/profiler/enabling/dotnet.md

@@ -229,9 +229,12 @@ To install the .NET Profiler per-webapp:
 
 4. For standalone applications, manually restart the application as you normally would.
 
-5. A minute or two after starting your application, your profiles appear on the [Datadog APM > Profiler page][1].
+5. Optional: Set up [Source Code Integration][2] to connect your profiling data with your Git repositories.
+
+6. A minute or two after starting your application, your profiles appear on the [Datadog APM > Profiler page][1].
 
 [1]: https://app.datadoghq.com/profiling
+[2]: /integrations/guide/source-code-integration/?tab=net
 {{% /tab %}}
 
 {{% tab "Internet Information Services (IIS)" %}}
@@ -283,9 +286,12 @@ To install the .NET Profiler per-webapp:
      <strong>Note:</strong> Use <code>stop</code> and <code>start</code> commands. A reset or restart does not always work.
    </div>
 
-5. A minute or two after starting your application, your profiles appear on the [Datadog APM > Profiler page][1].
+5. Optional: Set up [Source Code Integration][2] to connect your profiling data with your Git repositories.
+
+6. A minute or two after starting your application, your profiles appear on the [Datadog APM > Profiler page][1].
 
 [1]: https://app.datadoghq.com/profiling
+[2]: /integrations/guide/source-code-integration/?tab=net
 {{% /tab %}}
 
 {{% tab "Windows services" %}}
@@ -351,9 +357,12 @@ To install the .NET Profiler per-webapp:
    Set-ItemProperty HKLM:SYSTEM\CurrentControlSet\Services\MyService -Name Environment -Value $v
    ```
 
-4. A minute or two after you start your application, your profiles appear on the [Datadog APM > Profiler page][1].
+4. Optional: Set up [Source Code Integration][2] to connect your profiling data with your Git repositories.
+
+5. A minute or two after you start your application, your profiles appear on the [Datadog APM > Profiler page][1].
 
 [1]: https://app.datadoghq.com/profiling
+[2]: /integrations/guide/source-code-integration/?tab=net
 {{% /tab %}}
 
 {{% tab "Windows Standalone applications" %}}
@@ -390,9 +399,12 @@ To install the .NET Profiler per-webapp:
    REM start the application here
    ```
 
-4. A minute or two after you start your application, your profiles appear on the [Datadog APM > Profiler page][1].
+4. Optional: Set up [Source Code Integration][2] to connect your profiling data with your Git repositories.
+
+5. A minute or two after you start your application, your profiles appear on the [Datadog APM > Profiler page][1].
 
 [1]: https://app.datadoghq.com/profiling
+[2]: /integrations/guide/source-code-integration/?tab=net
 {{% /tab %}}
 
 {{% tab "NuGet" %}}
@@ -496,3 +508,4 @@ The [Getting Started with Profiler][4] guide takes a sample service with a perfo
 [13]: /profiler/connect_traces_and_profiles/#break-down-code-performance-by-api-endpoints
 [14]: /profiler/enabling/supported_versions/
 [15]: /profiler/guide/solve-memory-leaks/
+[16]: /integrations/guide/source-code-integration/?tab=net

content/en/profiler/enabling/nodejs.md

@@ -76,7 +76,7 @@ const tracer = require('dd-trace/init')
 {{% /tab %}}
 {{< /tabs >}}
 
-4. Optional: Set up [Source Code Integration][4].
+4. Optional: Set up [Source Code Integration][4] to connect your profiling data with your Git repositories.
 
 5. A minute or two after starting your Node.js application, your profiles will appear on the [APM > Profiler page][5]. If they do not, refer to the [Troubleshooting][9] guide.
 

content/en/profiler/enabling/php.md

@@ -109,7 +109,9 @@ To begin profiling applications:
         with datadog-profiling v1.13.0, Copyright Datadog, by Datadog
     ```
 
-5. A minute or two after receiving a request, profiles appear on the [APM > Profiler page][5].
+6. Optional: Set up [Source Code Integration][16] to connect your profiling data with your Git repositories.
+
+7. A minute or two after receiving a request, profiles appear on the [APM > Profiler page][5].
 
 ## Not sure what to do next?