Repo sync for protected CLA branch

docs/ide/not-in-toc/default.md

@@ -3,7 +3,7 @@ title: F1 help no-match fallback
 description: "Oops! No F1 match found."
 ms.prod: visual-studio
 ms.technology: 
-ms.date: 07/20/2021
+ms.date: 08/06/2021
 ms.topic: error-reference
 ms.custom: contperf-fy21q4
 recommendations: false
@@ -30,14 +30,12 @@ ms.author: mikejo
 ---
 # Oops! No `F1` help match was found
 
-:::image type="content" source="../media/search-error-page-sm.png" alt-text="Sorry we couldn't find a match" border="false":::
-
 ## Now what?
 
 We're sorry! It looks like we couldn't find what you were looking for. 
 
 **Looking for `F1` help on a window, a keyword, or an API name?**
-- Try your favorite search engine **[Recommended]**
+- **Try your favorite search engine [Recommended]**
 - Use the [docs.microsoft.com](/) toolbar to search 
 - Search the [.NET API browser](/dotnet/api/) or read our [text code editor overview](../../ide/writing-code-in-the-code-and-text-editor.md)
 - Browse the Knowledge Base for [Visual Studio troubleshooting](/troubleshoot/visualstudio/welcome-visual-studio/)
@@ -52,3 +50,5 @@ We'd love to get your feedback on how to provide the help you need.
 
 > [!div class="nextstepaction"]
 > [Share your feedback (5 minute survey)](https://www.surveymonkey.com/r/F1_Help_Visual_Studio)
+
+:::image type="content" source="../media/search-error-page-sm.png" alt-text="Sorry we couldn't find a match" border="false":::

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

@@ -2,7 +2,7 @@
 title: "Measure CPU usage in your apps"
 description: "Analyze CPU performance issues in your application using the debugger-integrated diagnostics tools."
 ms.custom: "seodec18"
-ms.date: 04/03/2019
+ms.date: 04/03/2021
 ms.topic: tutorial
 f1_keywords:
   - "vs.performance.wizard.intropage"
@@ -25,7 +25,7 @@ Find performance issues while you're debugging with the debugger-integrated **CP
 When the debugger pauses, the **CPU Usage** tool in the Diagnostic Tools window collects information about the functions that are executing in your application. The tool lists the functions that were performing work, and provides a timeline graph you can use to focus on specific segments of the sampling session.
 
 > [!Important]
-> The debugger-integrated Diagnostics Tools are supported for .NET development in Visual Studio, including ASP.NET, ASP.NET Core, and for native/C++ development. Windows 8 and later is required to run profiling tools with the debugger (**Diagnostic Tools** window).
+> The debugger-integrated Diagnostics Tools are supported for .NET development in Visual Studio, including ASP.NET, ASP.NET Core, and for native/C++ development. The corresponding Visual Studio [workload](../install/modify-visual-studio.md) is required. Windows 8 and later is required to run profiling tools with the debugger (**Diagnostic Tools** window).
 
 In this tutorial, you will:
 

docs/toc.yml

@@ -1434,21 +1434,13 @@
   - name: "What's new in Docs"
     href: ide/whats-new-visual-studio-docs.md
   - name: Release notes
-    items:
-    - name: Release rhythm
-      href: /visualstudio/productinfo/release-rhythm/
-    - name: Visual Studio 2022 notes
-      href: /visualstudio/releases/2022/release-notes-preview/
-    - name: Visual Studio 2019 notes
-      href: /visualstudio/releases/2019/release-notes/
-    - name: Visual Studio 2017 notes
-      href: /visualstudio/releasenotes/vs2017-relnotes/
-    - name: Visual Studio 2015 docs
-      href: vs-2015-archive.md
-    - name: License terms
-      href: https://visualstudio.microsoft.com/license-terms/
-    - name: Support lifecycle and servicing
-      href: /visualstudio/productinfo/vs-servicing-vs/
+    href: /visualstudio/releases/
+  - name: Release rhythm
+    href: /visualstudio/productinfo/release-rhythm/
+  - name: License terms
+    href: https://visualstudio.microsoft.com/license-terms/
+  - name: Support lifecycle and servicing
+    href: /visualstudio/productinfo/vs-servicing-vs/
   - name: Customer Experience Improvement
     items:
     - name: About the program