[PROF-13293]feat: update memory leak text

Author: c-moller

content/en/profiler/guide/solve-memory-leaks.md

@@ -25,17 +25,16 @@ The walkthrough guides you through several steps to:
 1. Scope to the relevant data.
 2. Recommend Datadog integrations and upgrades that assist in the investigation.
 3. Explain how memory management works in your runtime.
-4. Confirm potential memory leaks by inspecting retained objects through [Profile Comparisons][2].
+4. Confirm potential memory leaks by inspecting retained objects using profile comparisons.
 
 ## Requirements
 
 To use this walkthrough, you need:
 * A containerized service with either the Datadog Kubernetes integration or the Datadog Container integration installed.
 * [Continuous Profiler enabled][3].
   * Ensure that your profiles are tagged with `container_id`. This is necessary to link between container memory utilization metrics and profiling data.
-  * For Java and .NET ensure that heap profiling is enabled so that heap data is available for analysis.
-    * For Java: [Enabling the heap histogram metrics][6]
-    * For .NET: [Heap snapshot][7]
+  * For Java ([Enabling the heap histogram metrics][6]) and .NET ([Heap snapshot][7]) ensure that heap profiling is enabled so that heap data is available for analysis.
+
 
 ## Get started
 
@@ -48,7 +47,6 @@ To investigate a memory leak using the guided walkthrough:
 
 
 [1]: /profiler/enabling/supported_versions/#profile-types
-[2]: /profiler/compare_profiles
 [3]: /profiler/enabling
 [4]: https://app.datadoghq.com/services
 [5]: /tracing/services/service_page/#memory-leaks