Merging changes synced from https://github.com/MicrosoftDocs/visualstudio-docs-pr (branch live)

Author: Learn Build Service GitHub App

docs/debugger/debug-dotnet-core-in-wsl-2.md

@@ -18,7 +18,7 @@ ms.workload:
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
 
-You can easily run and debug your .NET apps in Linux without leaving Visual Studio using WSL. If you are a cross-platform developer, you can use this method as a simple way to test more of your target environments.
+You can easily run and debug your .NET Core and .NET 5+ apps in Linux without leaving Visual Studio using WSL. If you are a cross-platform developer, you can use this method as a simple way to test more of your target environments.
 
 For a Windows .NET user targeting Linux, WSL lives in a sweet spot between production realism and productivity. In Visual Studio, you can already debug in a remote Linux environment using the [remote debugger](../debugger/remote-debugging-dotnet-core-linux-with-ssh.md), or with containers using the [Container Tools](../containers/overview.md). When production realism is your main concern, you should use one of those options. When an easy and fast inner-loop is more important, WSL is a great option.
 

docs/debugger/decompilation.md

@@ -65,7 +65,7 @@ Extracted source files appear in the miscellaneous files in **Solution Explorer*
 
 ## SourceLink
 
-For .NET libraries or for NuGet packages enabled for SourceLink, you can also step into source code, set breakpoints, and use all the debugger’s features. For more information, see [Improving debug-time productivity with SourceLink](https://devblogs.microsoft.com/dotnet/improving-debug-time-productivity-with-source-link/).
+For .NET libraries or for NuGet packages enabled for SourceLink, you can also step into source code, set breakpoints, and use all the debugger’s features. For more information, see [Enable debugging and diagnostics with Source Link](../debugger/how-to-improve-diagnostics-debugging-with-sourcelink.md) and [Improving debug-time productivity with SourceLink](https://devblogs.microsoft.com/dotnet/improving-debug-time-productivity-with-source-link/).
 
 ## Known limitations
 

docs/debugger/remote-debugging-dotnet-core-linux-with-ssh.md

@@ -1,6 +1,6 @@
 ---
 title: "Debug .NET Core on Linux"
-description: Debug .NET Core on Linux using Secure Shell (SSH) by attaching to a process. Prepare your app for debugging. Build and deploy the app. Attach the debugger.
+description: Debug .NET Core and .NET 5+ on Linux using Secure Shell (SSH) by attaching to a process. Prepare your app for debugging. Build and deploy the app. Attach the debugger.
 ms.date: "03/20/2023"
 ms.topic: "conceptual"
 helpviewer_keywords:
@@ -16,7 +16,7 @@ ms.workload:
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
 
-Starting in Visual Studio 2017, you can attach to .NET Core processes running on a local or remote Linux deployment over Secure Shell (SSH). This article describes how to set up debugging and how to debug. For debugging scenarios using Docker containers, see [Attach to a process running on a Docker container](../debugger/attach-to-process-running-in-docker-container.md) and the [container tools](../containers/edit-and-refresh.md) articles instead. To debug Linux on WSL 2 from Visual Studio (no attach to process), see [Debug .NET Core Apps in WSL 2 with Visual Studio](../debugger/debug-dotnet-core-in-wsl-2.md).
+Starting in Visual Studio 2017, you can attach to .NET Core and .NET 5+ processes running on a local or remote Linux deployment over Secure Shell (SSH). This article describes how to set up debugging and how to debug. For debugging scenarios using Docker containers, see [Attach to a process running on a Docker container](../debugger/attach-to-process-running-in-docker-container.md) and the [container tools](../containers/edit-and-refresh.md) articles instead. To debug Linux on WSL 2 from Visual Studio (no attach to process), see [Debug .NET Core Apps in WSL 2 with Visual Studio](../debugger/debug-dotnet-core-in-wsl-2.md).
 
 > [!NOTE]
 > For debugging Linux running on Azure Kubernetes Service (AKS), [Bridge to Kubernetes](/visualstudio/bridge/overview-bridge-to-kubernetes) is recommended instead of attach to process.

docs/debugger/toc.yml

@@ -392,11 +392,11 @@
       href: debug-live-azure-virtual-machines-time-travel-debugging.md
   - name: Linux debugging
     items:
-    - name: Debug .NET Core apps in WSL 2
+    - name: Debug .NET apps in WSL 2
       href: debug-dotnet-core-in-wsl-2.md
-    - name: Debug .NET Core on Linux using SSH
+    - name: Debug .NET on Linux using SSH
       href: remote-debugging-dotnet-core-linux-with-ssh.md
-    - name: Debug .NET Core on AKS >>
+    - name: Debug .NET on AKS >>
       href: /visualstudio/bridge/bridge-to-kubernetes-vs
     - name: Debug with Container Tools >>
       href: ../containers/edit-and-refresh.md

docs/debugger/using-tracepoints.md

@@ -19,6 +19,9 @@ ms.workload:
 Tracepoints allow you to log information to the Output window under configurable conditions without modifying or stopping your
 code. This feature is supported for both managed languages (C#, Visual Basic, F#) and native code as well as languages such as JavaScript and Python.
 
+> [!NOTE]
+> For information on logging information to the Output window programmatically using .NET APIs, see [Send messages to the Output window](../debugger/diagnostic-messages-in-the-output-window.md).
+
 ## Let's take an example
 
 ::: moniker range="vs-2019"

docs/ide/visual-studio-github-copilot-extension.md

@@ -1,7 +1,7 @@
 ---
 title: About the GitHub Copilot extension for Visual Studio
 description: Use Visual Studio and the GitHub Copilot extension together to take advantage of AI and generate detailed info about your code, along with suggested edits, and even new code snippets, too. 
-ms.date: 06/09/2023
+ms.date: 08/03/2023
 ms.topic: overview 
 ms.custom: template-overview
 author: TerryGLee
@@ -57,6 +57,9 @@ GitHub Copilot supports several programming languages and frameworks, including
 1. Select the **GitHub Copilot** extension, and then select the **Download** button.
 1. Restart Visual Studio to complete the installation process.
 
+   > [!NOTE]
+   > For more information about activation & authorization, see the [Installing the Visual Studio extension](https://docs.github.com/en/copilot/getting-started-with-github-copilot?tool=visualstudio#installing-the-visual-studio-extension) section in GitHub Docs.
+
 After installation, you can start using GitHub Copilot by typing code in the editor and observing the suggestions provided by AI.
 
 ## Next steps