Update intro

Author: Mikejo5000

docs/profiling/memory-usage-without-debugging2.md

@@ -20,6 +20,8 @@ The **Memory Usage** tool monitors your app's memory use. You can use the tool t
 
 The Memory Usage tool can run [on release or debug builds](../profiling/running-profiling-tools-with-or-without-the-debugger.md). In this article, we show how to use the Memory Usage tool in the Visual Studio **Performance Profiler**, which is recommended for release builds. For information on choosing the best memory analysis tool for your needs, see [Choose a memory analysis tool](../profiling/analyze-memory-usage.md).
 
+For the best experience with this documentation, choose your preferred development language or runtime from the list at the top of the article.
+
 ::: zone pivot="programming-language-dotnet,programming-language-dotnetf,programming-language-cpp"
 ## Memory Usage diagnostic sessions
 

docs/profiling/profiling-feature-tour.md

@@ -21,6 +21,8 @@ Application performance measuring tools are essential for developers who want to
 
 For help with choosing the correct tool, or to see profiling tool support for different app types, see [Which tool should I use?](../profiling/choose-performance-tool.md) For a tutorial that shows a general approach to optimizing code using the profiling tools, see [Case study: Beginner's guide to optimizing code](../profiling/optimize-code-using-profiling-tools.md).
 
+For the best experience with this documentation, choose your preferred development language or runtime from the list at the top of the article.
+
 ## <a name="post_mortem"></a> Measure performance in release builds
 
 Tools in the Performance Profiler are intended to provide analysis for **Release** builds. In the Performance Profiler, you can collect diagnostic info while the app is running, and then examine the collected information after the app is stopped (a post-mortem analysis).