Merge pull request #11433 from Mikejo5000/mikejo-br20

Update get started links for profiling tools

Author: prmerger-automator[bot]

docs/profiling/beginners-guide-to-performance-profiling.md

@@ -207,6 +207,11 @@ Use the search box to find a node that you are looking for, then use the horizon
 
 ## Next steps
 
+In this tutorial, you've learned how to collect and analyze CPU usage data. If you already completed the [tour of the profiler](../profiling/profiling-feature-tour.md), you may want to read about a general approach to optimizing code using the profiling tools.
+
+> [!div class="nextstepaction"]
+> [Reduce compute costs by using profiling tools](../profiling/optimize-code-using-profiling-tools.md)
+
 In this tutorial, you've learned how to collect and analyze CPU usage data while debugging. You may want to find out more about profiling release builds using the Performance Profiler.
 
 > [!div class="nextstepaction"]

docs/profiling/choose-performance-tool.md

@@ -20,7 +20,7 @@ ms.workload:
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
 
-Visual Studio provides a variety of profiling tools to help you diagnose different kinds of app performance issues depending on your app type. In this article, we provide information to help you find the right tool for your scenario and application type.
+Visual Studio provides a variety of profiling tools to help you diagnose different kinds of app performance issues depending on your app type. In this article, we provide information to help you find the right tool for your scenario and application type. For a general approach to optimizing code using the profiling tools, see [Reduce compute costs by using profiling tools](../profiling/optimize-code-using-profiling-tools.md).
 
 ## Which tool should I use?
 

docs/profiling/memory-usage.md

@@ -329,10 +329,10 @@ The change report adds columns (marked with **(Diff)**) to the base report that
 
 ## Next steps
 
-In this tutorial, you've learned how to collect and analyze memory usage data. If you already completed the [tour of the profiler](../profiling/profiling-feature-tour.md), you may want to get a quick look at how to analyze CPU usage in your apps.
+In this tutorial, you've learned how to collect and analyze memory usage data. If you already completed the [tour of the profiler](../profiling/profiling-feature-tour.md), you may want to read about a general approach to optimizing code using the profiling tools.
 
 > [!div class="nextstepaction"]
-> [Analyze CPU usage](../profiling/beginners-guide-to-performance-profiling.md)
+> [Reduce compute costs by using profiling tools](../profiling/optimize-code-using-profiling-tools.md)
 
 In this tutorial, you've learned how to collect and analyze memory usage data while debugging. You may want to find out more about analyzing memory usage in release builds using the Performance Profiler.
 

docs/profiling/optimize-code-using-profiling-tools.md

@@ -70,7 +70,7 @@ SELECT "b"."Url", "b"."BlogId", "p"."PostId", "p"."Author", "p"."BlogId", "p"."C
 FROM "Blogs" AS "b" LEFT JOIN "Posts" AS "p" ON "b"."BlogId" = "p"."BlogId" ORDER BY "b"."BlogId"
 ```
 
-To see what's going on with the app in terms of memory usage, collect a trace using the .NET Object Allocation tool. The **Call Tree** view in the memory trace shows the hot path and helps you identify an area of high memory usage. No surprise at this point, the `GetBlogTitleX` method appears to be generating a lot of objects! Over 900,000 object allocations, in fact.
+To see what's going on with the app in terms of memory usage, collect a trace using the .NET Object Allocation tool (For C++, use the Memory Usage tool instead). The **Call Tree** view in the memory trace shows the hot path and helps you identify an area of high memory usage. No surprise at this point, the `GetBlogTitleX` method appears to be generating a lot of objects! Over 900,000 object allocations, in fact.
 
 :::image type="content" source="./media/optimize-code-dotnet-object-allocations.png" alt-text="Screenshot of Call Tree view in the .NET Object Allocation tool.":::
 

docs/profiling/profiling-feature-tour.md

@@ -33,7 +33,7 @@ There are several ways to diagnose performance issues when you’re working with
 
 In software engineering, a profiler is a tool used to help you analyze the performance of your applications to improve poorly performing code. Profiling and diagnostics tools help you diagnose memory and CPU usage and other application-level issues. With these tools, you can collect performance data while you run your application.
 
-A profiler can help you make informed decisions quickly by providing a visual depiction of execution times and CPU usage for your application. It’s much easier and quicker to understand issues and fix them when you can see a graph of the execution times or the CPU usage. For information on using the tools to help optimize your code, see [Reduce compute costs by using profiling tools](../profiling/optimize-code-using-profiling-tools.md).
+A profiler can help you make informed decisions quickly by providing a visual depiction of execution times and CPU usage for your application. It’s much easier and quicker to understand issues and fix them when you can see a graph of the execution times or the CPU usage. For a general approach to optimizing code using the profiling tools, see [Reduce compute costs by using profiling tools](../profiling/optimize-code-using-profiling-tools.md).
 
 ## Measure performance while debugging
 
@@ -308,4 +308,5 @@ In Visual Studio 2019,  the legacy Performance Explorer and related profiling to
 ## See also
 
 - [Which tool should I use?](../profiling/choose-performance-tool.md)
+- [Reduce compute costs by using profiling tools](../profiling/optimize-code-using-profiling-tools.md)
 - [Run profiling tools with or without the debugger](../profiling/running-profiling-tools-with-or-without-the-debugger.md)