edits

Author: Mikejo5000

docs/profiling/running-profiling-tools-with-or-without-the-debugger.md

@@ -20,7 +20,7 @@ To help you decide between using the profiling tools in release or debug builds,
 
   - Release builds provide optimizations like inlining function calls and constants, pruning unused code paths, and storing variables in ways that can't be used by the debugger. Performance numbers in debug builds are less accurate, because debug builds lack these optimizations.
   - In addition to differences between release builds and debug builds, the debugger itself changes performance times, as it does necessary debugger operations like intercepting exception and module load events.
-  - For performance problems caused by CPU-intensive calls, there might be considerable performance differences between release and debug builds. Check to see whether the CPU issue exists in release builds.
+  - For performance problems caused by CPU-intensive calls, there might be considerable performance differences between release and debug builds. Check to see whether the CPU performance issue exists in release builds.
   - External performance problems, like file I/O or network responsiveness issues, won't look much different in a release build or a debug build.
   - If the problem occurs only with debug builds, you probably don't need to run the tools with release builds.
   - Some tools, such as the .NET Object Allocation tool, are only available in the Performance Profiler (non-debugger scenarios).

docs/test/debug-unit-tests-with-test-explorer.md

@@ -42,7 +42,7 @@ To diagnose why a test method is taking more time than you'd like, or using more
 1. Right-click the method in Test Explorer, and then select **Profile**.
 1. In the Performance Profiler, select a profiling tool to test your code.
 
-For more information, see [this blog post](https://devblogs.microsoft.com/visualstudio/a-unit-of-profiling-makes-the-allocations-go-away/) or see [Collect profiling data without debugging](../profiling/running-profiling-tools-with-or-without-the-debugger.md#collect-profiling-data-without-debugging).
+For more information, see [this blog post](https://devblogs.microsoft.com/visualstudio/a-unit-of-profiling-makes-the-allocations-go-away/) or see [Collect profiling data on release builds](../profiling/running-profiling-tools-with-or-without-the-debugger.md#collect-profiling-data-on-release-builds).
 ::: moniker-end
 
 ::: moniker range="vs-2019"