edits

Author: Mikejo5000

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

@@ -12,13 +12,15 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: debug-diagnostics
+zone_pivot_groups: programming-languages-set-two
 ---
 # Analyze memory usage in release builds (C#, Visual Basic, C++, F#)
 
 The **Memory Usage** tool monitors your app's memory use. You can use the tool to study the real-time memory effects of scenarios you're actively developing in Visual Studio. You can take detailed snapshots of the app's memory states, and compare snapshots to find the root causes of memory issues. The Memory Usage tool is supported on .NET, ASP.NET, C++, or mixed mode (.NET and native) apps.
 
 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).
 
+::: zone pivot="programming-language-dotnet,programming-language-dotnetf,programming-language-cpp"
 ## Memory Usage diagnostic sessions
 
 **To start a Memory Usage diagnostic session:**
@@ -40,6 +42,7 @@ The Memory Usage tool can run [on release or debug builds](../profiling/running-
    ::: moniker range="vs-2019"
    ![Start a Memory Usage diagnostic session.](../profiling/media/memory-usage-start-diagnostics-session.png "Start a Memory Usage diagnostic session")
    ::: moniker-end
+::: zone-end
 
 ### Monitor memory use
 
@@ -121,6 +124,7 @@ For C++, the **Objects (Diff)** column is named **Allocations (Diff)**.
 |![Step 4](../profiling/media/process-guide-4.png "Process Guide-4")|The difference between the total number of memory objects in this snapshot and the previous snapshot. Select this link to display a snapshot diff report. It’s sorted by the difference in the total count of instances of the types.|
 ::: moniker-end
 
+::: zone pivot="programming-language-dotnet,programming-language-dotnetf"
 ## Managed types reports
 
 [!INCLUDE [managed-types-report](../profiling/includes/managed-types-report.md)]
@@ -142,7 +146,9 @@ Many types in apps aren't required for app developers to investigate memory issu
 - <a name="BKMK_Just_My_Code"></a> Select **Show Just My Code** in the **Filter** dropdown to hide most instances that are generated by external code. External types belong to the operating system or framework components, or are generated by the compiler.
 
 - <a name="BKMK_Collapse_Small_Objects"></a> Select **Collapse Small Objects** in the **Filter** dropdown to hide types whose **Size (Bytes)** is less than 0.5 percent of the total memory.
+::: zone-end
 
+::: zone pivot="programming-language-cpp"
 ## Native types reports
 
 [!INCLUDE [native-types-report](../profiling/includes/native-types-report.md)]
@@ -152,6 +158,7 @@ Many types in apps aren't required for app developers to investigate memory issu
 
 [!INCLUDE [memory-usage-insights](../profiling/includes/memory-usage-insights.md)]
 ::: moniker-end
+::: zone-end
 
 ## Change (Diff) reports
 

docs/profiling/profiling-feature-tour.md

@@ -21,7 +21,7 @@ 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).
 
-::: zone pivot="programming-language-dotnet,programming-language-cpp,programming-language-all"
+::: zone pivot="programming-language-dotnet,programming-language-dotnetf,programming-language-cpp"
 ## <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).
@@ -271,7 +271,7 @@ The tool shows each event in a list view. Columns provide information about each
 You can programatically create custom events that appear as icons in the timeline graphs such as the CPU utilization and memory usage timeline graphs. For more information, see [Add user marks to timeline](../profiling/add-timeline-graph-user-marks.md).
 ::: moniker-end
 
-::: zone pivot="programming-language-dotnet"
+::: zone pivot="programming-language-dotnet,programming-language-dotnetf"
 ## Analyze resource consumption (XAML)
 
 In XAML apps, such as Windows desktop WPF apps and UWP apps, you can analyze resource consumption using the Application Timeline tool. For example, you can analyze the time spent by your application preparing UI frames (layout and render), servicing network and disk requests, and in scenarios like application startup, page load, and Window resize. To use the tool, choose **Application Timeline** in the Performance Profiler, and then choose **Start**. In your app, go through the scenario with a suspected resource consumption issue, and then choose **Stop collection** to generate the report.

docs/zone-pivot-groups.yml

@@ -20,10 +20,10 @@ groups:
   pivots:
   - id: programming-language-dotnet
     title: .NET
+  - id: programming-language-dotnetf
+    title: .NET Framework
   - id: programming-language-cpp
     title: C++
-  - id: programming-language-all
-    title: Other languages
 # Notice how the ids, titles, and prompts are
 # consistent and in order.
 # Note: This set is not used currently, but is present as an example.