acrolinx

Author: Mikejo5000

docs/profiling/perf-insights-loh-allocations.md

@@ -23,8 +23,8 @@ Frequent temporary LOH object allocations force unproductive full generation 2 (
 
 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). These allocations are assumed to survive longer due to their allocation cost and are therefore only collected during full [Gen2 GCs](/dotnet/standard/garbage-collection/fundamentals#generations).
 
-When this assumption is not true and an application frequently allocates temporary large objects, the LOH space is quickly used up. This causes many Gen2 GCs to regain space which can impact performance and responsiveness of an application.
+When this assumption isn't true, and an application frequently allocates temporary large objects, the LOH space is quickly used up. This causes many Gen2 GCs to regain space which can impact performance and responsiveness of an application.
 
 ## 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 **Iinvestigate** 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.