Merge pull request #8516 from MicrosoftDocs/main638000898142464345sync_temp

Jak-MS · web-flow · commit 1f337691d704 · 2022-09-30T07:55:25.000-07:00
Repo sync for protected CLA branch
diff --git a/docs/ide/reference/options-text-editor-fsharp-intellisense.md b/docs/ide/reference/options-text-editor-fsharp-intellisense.md
@@ -6,8 +6,8 @@ ms.date: 01/16/2019
 ms.topic: reference
 f1_keywords:
   - "VS.ToolsOptionsPages.Text_Editor.FSharp.IntelliSense"
-author: jillre
-ms.author: jillfra
+author: TerryGLee
+ms.author: tglee
 manager: jmartens
 ms.technology: vs-ide-general
 ms.workload:
@@ -36,4 +36,4 @@ Use the **IntelliSense** options page to modify some text editor settings for F#
 ## See also
 
 - [General, Environment, Options Dialog Box](../../ide/reference/general-environment-options-dialog-box.md)
-- [Using IntelliSense](../../ide/using-intellisense.md)
+- [Using IntelliSense](../../ide/using-intellisense.md)
diff --git a/docs/profiling/analyze-memory-usage.md b/docs/profiling/analyze-memory-usage.md
@@ -19,7 +19,7 @@ To find memory leaks and inefficient memory usage, you can use tools such as the
 
 The Memory Usage tool lets you take one or more *snapshots* of the managed and native memory heap. You can collect snapshots of .NET, ASP.NET, C++, or mixed mode (.NET and native) apps. The **Memory Usage** tool can run on an open Visual Studio project, on an installed Microsoft Store app, or attached to a running app or process. You can run the **Memory Usage** tool with or without debugging. For more information, see [Run profiling tools with or without the debugger](../profiling/running-profiling-tools-with-or-without-the-debugger.md). In the debugger, you can turn memory profiling on and off, and see a per-object breakdown of memory usage. You can view memory usage results when execution is paused, for example at a breakpoint.
 
-.NET developers may choose between either the .NET Object Allocation tool or the [Memory usage](../profiling/memory-usage.md) tool.
+.NET developers may choose between either the .NET Object Allocation tool or the Memory usage tool.
 
 - The [.NET Object Allocation tool](../profiling/dotnet-alloc-tool.md) helps you identify allocation patterns and anomalies in your .NET code, and helps identify common issues with garbage collection. This tool runs only as a post-mortem tool. You can run this tool on local or remote machines.
 - The [Memory Usage tool](../profiling/memory-usage-without-debugging2.md) is helpful in identifying memory leaks, which are not typically common in .NET apps. If you need to use debugger features while checking memory, such as stepping through code, the [debugger-integrated Memory usage](../profiling/memory-usage.md) tool is recommended.
diff --git a/docs/profiling/index.yml b/docs/profiling/index.yml
@@ -11,7 +11,7 @@ metadata:
   author: mikejo5000
   ms.author: mikejo
   manager: jmartens
-  ms.date: 06/03/2020
+  ms.date: 09/29/2022
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 
@@ -53,22 +53,22 @@ landingContent:
         links:
           - text: CPU Usage
             url: cpu-usage.md
+          - text: Memory Usage
+            url: memory-usage-without-debugging2.md
+          - text: CPU Insights
+            url: cpu-insights.md
+          - text: File I/O
+            url: use-file-io.md
           - text: Database
             url: analyze-database.md
           - text: Events Viewer
             url: events-viewer.md
-          - text: Memory Usage
-            url: memory-usage-without-debugging2.md
           - text: .NET Object Allocation Tracking
             url: dotnet-alloc-tool.md
           - text: .NET Async
             url: analyze-async.md
-          - text: File I/O
-            url: use-file-io.md
           - text: .NET Counters
             url: dotnet-counters-tool.md  
-          - text: GPU Usage (Direct3D)
-            url: gpu-usage.md
           - text: Analyze resource consumption (XAML)
             url: application-timeline.md
 
diff --git a/docs/profiling/memory-usage-without-debugging2.md b/docs/profiling/memory-usage-without-debugging2.md
@@ -22,7 +22,7 @@ ms.workload:
 
 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 [with or without the debugger](../profiling/running-profiling-tools-with-or-without-the-debugger.md). In this article, we show how to use the Memory Usage tool without the debugger 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/memory-usage.md).
+The Memory Usage tool can run [with or without the debugger](../profiling/running-profiling-tools-with-or-without-the-debugger.md). In this article, we show how to use the Memory Usage tool without the debugger 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).
 
 ## Memory Usage diagnostic sessions
 
diff --git a/docs/profiling/memory-usage.md b/docs/profiling/memory-usage.md
@@ -15,7 +15,7 @@ ms.workload:
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
 
-Find memory leaks and inefficient memory while you're debugging with the debugger-integrated **Memory Usage** diagnostic tool. The Memory Usage tool lets you take one or more *snapshots* of the managed and native memory heap to help understand the memory usage impact of object types. You can also analyze memory usage without a debugger attached or by targeting a running app. For more information, see [Run profiling tools with or without the debugger](../profiling/running-profiling-tools-with-or-without-the-debugger.md). For information on choosing the best memory analysis tool for your needs, see [Choose a memory analysis tool](../profiling/memory-usage.md).
+Find memory leaks and inefficient memory while you're debugging with the debugger-integrated **Memory Usage** diagnostic tool. The Memory Usage tool lets you take one or more *snapshots* of the managed and native memory heap to help understand the memory usage impact of object types. You can also analyze memory usage without a debugger attached or by targeting a running app. For more information, see [Run profiling tools with or without the debugger](../profiling/running-profiling-tools-with-or-without-the-debugger.md). For information on choosing the best memory analysis tool for your needs, see [Choose a memory analysis tool](../profiling/analyze-memory-usage.md).
 
 Although you can collect memory snapshots at any time in the **Memory Usage** tool, you can use the Visual Studio debugger to control how your application executes while investigating performance issues. Setting breakpoints, stepping, Break All, and other debugger actions can help you focus your performance investigations on the code paths that are most relevant. Performing those actions while your app is running can eliminate the noise from the code that doesn't interest you and can significantly reduce the amount of time it takes you to diagnose an issue.
 
