link fixes, edits

Author: Mikejo5000

docs/profiling/perf-insights-excessive-induced-gcs.md

@@ -17,7 +17,7 @@ This article describes performance insights for excessive induced garbage collec
 
 ## Cause
 
-It's rarely justified to induce GCs as GC manages its own schedule. The only rare cases are mostly from framework but even that should be very rare. If you are seeing too many induced GCs it's something to investigate especially if you are worried about your GC time or if you are surprised by the fact there are induced GCs.
+It's rarely justified to induce GCs as the garbage collector manages its own schedule. The only rare cases are mostly from framework but even that should be very rare. If you are seeing too many induced GCs it's something to investigate especially if you are worried about your GC time or if you are surprised by the fact there are induced GCs.
 
 ## Rule description
 
@@ -27,4 +27,4 @@ When an application frequently forces GC collections, it might impact performanc
 
 ## How to investigate a warning
 
-Look for (GC.Collect Method (System) | Microsoft Docs) and check if they are really needed.
+Look for <xref:System.GC.Collect%2A> and check whether the method calls are really needed.

docs/profiling/perf-insights-high-loh-fragmentation.md

@@ -21,8 +21,8 @@ The [large object heap (LOH)](/dotnet/standard/garbage-collection/large-object-h
 
 ## Rule description
 
-The [.NET Garbage Collector (GC)](/dotnet/standard/garbage-collection/) puts large objects in a specific region of memory known as the [large object heap (LOH)](https://docs.microsoft.com/dotnet/standard/garbage-collection/large-object-heap). Because the LOH is not compacted, sometimes the LOH can be the source of fragmentation.
+The [.NET Garbage Collector (GC)](/dotnet/standard/garbage-collection/) puts large objects in a specific region of memory known as the [large object heap (LOH)](/dotnet/standard/garbage-collection/large-object-heap). Because the LOH is not compacted, sometimes the LOH can be the source of fragmentation.
 
 ## How to investigate a warning
 
-Clicking on the "investigate" link will take you to the [Allocation](../profiling/dotnet-alloc-tool.md#allocation) view showing allocations grouped by heap type. Objects under the Large Object Heap node are contributing to the frequent GCs, consider reducing these allocations through reuse or pooling techniques.
+Click the **Investigate** link to go to the [Allocation](../profiling/dotnet-alloc-tool.md#allocation) view showing allocations grouped by heap type. Objects under the Large Object Heap node are contributing to the frequent GCs. Consider reducing these allocations through reuse or pooling techniques.