Merge pull request #10741 from MicrosoftDocs/main638820040647411678sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/data-tools/how-to-add-update-or-remove-a-wcf-data-service-reference.md

@@ -1,7 +1,7 @@
 ---
 title: Add, update, or remove WCF data service reference
 description: Explore how to add, update, or remove a Windows Communication Foundation (WCF) data service reference for .NET Framework applications in Visual Studio.
-ms.date: 04/17/2024
+ms.date: 5/2/2025
 ms.topic: how-to
 helpviewer_keywords:
 - service references [Visual Studio]

docs/debugger/debugger-feature-tour.md

@@ -1,5 +1,5 @@
 ---
-title: "First look at the debugger"
+title: "Overview of the debugger"
 description: Get started debugging your applications by using the Visual Studio debugger and see what your code is doing while it runs.
 ms.topic: conceptual
 ms.date: 3/11/2025
@@ -10,7 +10,7 @@ ms.author: mikejo
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
-# First look at the Visual Studio Debugger
+# Overview of the Visual Studio debugger
 
 This topic introduces the debugger tools provided by Visual Studio. In the Visual Studio context, when you *debug your app*, it usually means that you are running the application with the debugger attached (that is, in debugger mode). When you do this, the debugger provides many ways to see what your code is doing while it runs. You can step through your code and look at the values stored in variables, you can set watches on variables to see when values change, you can examine the execution path of your code, et al. If this is the first time that you've tried to debug code, you may want to read [Debugging for absolute beginners](../debugger/debugging-absolute-beginners.md) before going through this topic. If you are trying to perform a specific task and need to know what feature to use, see [Debugger feature finder](../debugger/find-your-debugging-task.yml). To try AI-assisted debugging, see [Debug with Copilot](../debugger/debug-with-copilot.md).
 

docs/debugger/toc.yml

@@ -4,7 +4,7 @@
   items:
   - name: What is debugging?
     href: what-is-debugging.md
-  - name: First look at the debugger
+  - name: Overview of the debugger
     href: debugger-feature-tour.md
   - name: Debugging techniques and tools
     href: write-better-code-with-visual-studio.md

docs/ide/adding-visual-studio-editor-support-for-other-languages.md

@@ -1,7 +1,7 @@
 ---
 title: Add editor support for other languages
 description: Learn about how the Visual Studio editor supports reading and navigating through different computer languages and how you can add support for other languages.
-ms.date: 11/04/2016
+ms.date: 5/02/2025
 ms.topic: conceptual
 helpviewer_keywords:
 - syntax colorization
@@ -68,31 +68,26 @@ Visual Studio currently provides syntax colorization and basic statement complet
 In addition to syntax colorization and basic statement completion, Visual Studio also has a feature called [Navigate To](/archive/blogs/benwilli/visual-studio-tip-3-use-navigate-to). This feature enables you to quickly search code files, file paths, and code symbols. Visual Studio provides Navigate To support for the following languages.
 
 - C#
-
 - C++
-
 - TypeScript
-
 - JavaScript
-
 - Visual Basic
-
 - Go
-
 - Java
-
 - PHP
 
-All of these file types have the features described earlier even if support for a given language hasn't yet been installed. Installing specialized support for some languages may provide additional language support, such as IntelliSense or other advanced language features like light bulbs.
+All of these file types have the features described earlier even if support for a given language isn't yet installed. Installing specialized support for some languages may provide additional language support, such as IntelliSense or other advanced language features like light bulbs.
 
-## Add support for non-supported languages
+## Add support for nonsupported languages
 
 Visual Studio provides language support in the editor by using [TextMate Grammars](https://manual.macromates.com/en/language_grammars). If your favorite programming language currently isn't supported in the Visual Studio editor, first, search the web—a TextMate bundle for the language may already exist. If you can't find one, though, you can add support for it yourself by creating a TextMate bundle model for language grammars and snippets.
 
 Add any new TextMate Grammars for Visual Studio in the following folder:
 
 *%userprofile%\\.vs\Extensions*
 
+> In Windows, *%userprofile%* resolves to the path: *c:\Users\\\<user name>*. If the *Extensions* folder does not exist on your system, you need to create it. If the folder already exists, it is hidden.
+
 Under this base path, add the following folders if they apply to your situation:
 
 |Folder Name|Description|
@@ -106,12 +101,12 @@ In Windows, *%userprofile%* resolves to the path: *c:\Users\\\<user name>*. If t
 > [!TIP]
 > If you have any files open in the editor, you'll need to close and reopen them to see syntax highlighting after you add the TextMate Grammars.
 
-For details about how to create TextMate Grammars, see [TextMate - Introduction to Language Grammars](https://developmentality.wordpress.com/2011/02/08/textmate-introduction-to-language-grammars/) and [Notes on how to create a Language Grammar and Custom Theme for a Textmate Bundle](https://benparizek.com/notebook/notes-on-how-to-create-a-language-grammar-and-custom-theme-for-a-textmate-bundle).
+For details about how to create TextMate Grammars, see [TextMate - Introduction to Language Grammars](https://developmentality.wordpress.com/2011/02/08/textmate-introduction-to-language-grammars/) and [Notes on how to create a Language Grammar and Custom Theme for a TextMate Bundle](https://benparizek.com/notebook/notes-on-how-to-create-a-language-grammar-and-custom-theme-for-a-textmate-bundle).
 
 ## Related content
 
 - [Add a Language Server Protocol extension](../extensibility/adding-an-lsp-extension.md)
-- [Walkthrough: Create a code snippet](../ide/walkthrough-creating-a-code-snippet.md)
-- [Walkthrough: Display statement completion](../extensibility/walkthrough-displaying-statement-completion.md)
-- [Example code: TextMate Grammar](https://github.com/microsoft/VSSDK-Extensibility-Samples/tree/master/TextmateGrammar)
-- [Example code: Custom language support](https://github.com/microsoft/VSSDK-Extensibility-Samples/tree/master/Ook_Language_Integration)
+- [Create a code snippet](../ide/walkthrough-creating-a-code-snippet.md)
+- [Display statement completion](../extensibility/walkthrough-displaying-statement-completion.md)
+- [Ship TextMate grammars inside Visual Studio extensions](https://github.com/microsoft/VSSDK-Extensibility-Samples/tree/master/TextmateGrammar)
+- [Implement custom language support](https://github.com/microsoft/VSSDK-Extensibility-Samples/tree/master/Ook_Language_Integration)

docs/ide/how-to-configure-projects-to-target-platforms.md

@@ -1,7 +1,7 @@
 ---
 title: 'Configure projects to target platforms'
 description: Set up your applications to target different platforms, including the ARM64 platform in Visual Studio with the Configuration Manager.
-ms.date: 05/06/2024
+ms.date: 5/2/2025
 ms.subservice: compile-build
 ms.topic: how-to
 helpviewer_keywords:

docs/ide/how-to-track-your-code-by-customizing-the-scrollbar.md

@@ -1,7 +1,7 @@
 ---
 title: Scroll bar map mode and bar mode
 description: Learn how to track changes in your code through the customization of the scroll bar and also learn how to use Bar mode and Map mode.
-ms.date: 03/20/2020
+ms.date: 05/2/2025
 ms.topic: how-to
 author: anandmeg
 ms.author: meghaanand
@@ -44,7 +44,7 @@ Curious as to which scroll bar annotations and their associated colors match whi
 
 #### Code changes
 
-Code changes are annotated in the far-left side of the vertical scroll bar. 
+Code changes are annotated in the far-left side of the vertical scroll bar. To modify the **Track changes** setting, go to **Tools** > **Options** > **Text Editor** > **Settings**.
 
 **Tracked files (in a Git repository)**
 

docs/ide/media/vs-2022/view-menu-bookmarks-window.png

@@ -1,7 +1,7 @@
 ---
 title: Reference an MSBuild Project SDK
 description: Use the MSBuild project SDKs to simplify working with software development kits that require properties and targets to be imported.
-ms.date: 05/16/2024
+ms.date: 5/1/2025
 ms.topic: how-to
 helpviewer_keywords:
 - MSBuild, SDKs, SDK
@@ -44,7 +44,7 @@ There are many SDKs distributed by Microsoft. The project SDK referenced in the
 
 There are three ways to reference a project SDK:
 
-### Use the `Sdk` attribute on the `<Project/>` element
+### Use the `Sdk` attribute on the `Project` element
 
 ```xml
 <Project Sdk="My.Custom.Sdk">
@@ -62,7 +62,7 @@ To specify a specific version of the SDK, append it to the `Sdk` attribute:
 </Project>
 ```
 
-### Use the top-level `<Sdk/>` element
+### Use the top-level `Sdk` element
 
 ```xml
 <Project>
@@ -75,7 +75,7 @@ An implicit import is added to the top and bottom of the project as discussed pr
 
 The `Version` attribute isn't required.
 
-### Use the `<Import/>` element anywhere in your project
+### Use the `Import` element anywhere in your project
 
 ```xml
 <Project>
@@ -90,10 +90,10 @@ The `Version` attribute isn't required.
 
 When you explicitly include the imports in your project, you have full control over the order.
 
-When using the `<Import/>` element, you can specify an optional `Version` attribute as well. For example, you can specify `<Import Project="Sdk.props" Sdk="My.Custom.Sdk" Version="1.2.3" />`.
+When using the `Import` element, you can specify an optional `Version` attribute as well. For example, you can specify `<Import Project="Sdk.props" Sdk="My.Custom.Sdk" Version="1.2.3" />`.
 
 > [!WARNING]
-> If you change your project to use `<Import/>` elements, make sure you add both `.props` and `.targets` imports, and that you remove the SDK from the `<Project/>` element and `<Sdk/>` elements. Failure to do so will result in doubled imports and an [`MSB4011`](./errors/msb4011.md) warning.
+> If you change your project to use `Import` elements, make sure you add both `.props` and `.targets` imports, and that you remove the SDK from the `Project` element and `Sdk` elements. Failure to do so will result in duplicaate imports and an [`MSB4011`](./errors/msb4011.md) warning.
 
 ## How project SDKs are resolved
 

docs/msbuild/how-to-use-project-sdk.md

@@ -1,5 +1,5 @@
 ---
-title: "First look at profiling tools"
+title: "Overview of the profiling tools"
 description: Review the different diagnostic tools available in Visual Studio for profiling your C#, Visual Basic, C++, and F# applications.
 ms.date: 1/17/2025
 ms.topic: conceptual
@@ -15,7 +15,7 @@ manager: mijacobs
 ms.subservice: debug-diagnostics
 zone_pivot_groups: programming-languages-set-two
 ---
-# First look at profiling tools (C#, Visual Basic, C++, F#)
+# Overview of the profiling tools (C#, Visual Basic, C++, F#)
 
 Application performance measuring tools are essential for developers who want to optimize their code and improve application performance. Visual Studio offers a range of profiling and diagnostics tools that can help you diagnose memory and CPU usage and other application-level issues. With these tools, you can accumulate performance data while you run your application. A profiler can help you make informed decisions quickly by providing a visual depiction of execution times and CPU usage for your application. In this article, we give a quick look at the most common profiling tools.
 

docs/profiling/profiling-feature-tour.md

@@ -2,10 +2,10 @@
   href: index.yml
 - name: Overview
   items:
-  - name: First look at profiling tools
-    href: profiling-feature-tour.md
   - name: What is a profiler?
     href: what-is-a-profiler.md
+  - name: Overview of the profiling tools
+    href: profiling-feature-tour.md
   - name: Which tool should I use?
     href: choose-performance-tool.md
   - name: Run profiling tools on release or debug builds