Merge pull request #10320 from MicrosoftDocs/main638573798977651828sync_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/containers/container-tools-react.md

@@ -9,9 +9,9 @@ ms.subservice: container-tools
 ms.topic: quickstart
 ---
 
-# Quickstart: Use Docker with a React Single-page App in Visual Studio
+# Quickstart: Use Docker with a React Single-page application in Visual Studio
 
-With Visual Studio, you can easily build, debug, and run containerized ASP.NET Core apps, including those with client-side JavaScript such as React.js single-page app, and publish them to Azure Container Registry, Docker Hub, Azure App Service, or your own Container Registry. In this article, we publish to Azure Container Registry.
+With Visual Studio, you can easily build, debug, and run containerized ASP.NET Core apps, including those with client-side JavaScript such as React.js single-page application (SPA), and publish them to Azure Container Registry, Docker Hub, Azure App Service, or your own Container Registry. In this article, we publish to Azure Container Registry.
 
 ## Prerequisites
 
@@ -239,7 +239,7 @@ Use the following steps for Visual Studio 2022 version 17.0 to 17.7:
 ## Debug
 
 :::moniker range=">=vs-2022"
-With Visual Studio 2022 version 17.9 or later and the **React and ASP.NET Core** template that uses `vite.js`, the projects are already configured to start both the client and server projects with debugging support, but you need to set up the right port for the SPA proxy to use to access the ASP.NET Core server running in the container. You can get the host port from the **Containers** window in Visual Studio and set it in the React project as described in [Create a React app - Docker](../javascript/tutorial-asp-net-core-with-react.md#docker).
+With Visual Studio 2022 version 17.9 or later and the **React and ASP.NET Core** template that uses `vite.js`, the projects are already configured to start both the client and server projects with debugging support, but you need to set up the right port for the single-page application (SPA) proxy to use to access the ASP.NET Core server running in the container. You can get the host port from the **Containers** window in Visual Studio and set it in the React project as described in [Create a React app - Docker](../javascript/tutorial-asp-net-core-with-react.md#docker).
 
 You can also disable the launch in the browser for the server, which is set up to open with Swagger, which is not required for this scenario. To disable the browser launch, open the **Properties** (**Alt**+**Enter**), go to the **Debug** tab, and click on the link **Open debug launch profiles UI**, and clear the **Launch browser** checkbox.
 

docs/containers/container-tools.md

@@ -104,7 +104,7 @@ The **Container Tools** option in the **Output** window shows what actions are t
 
 After the build completes, the browser opens and displays your app's home page. In the browser address bar, you can see the `localhost` URL and port number for debugging.
 
->[!NOTE]
+> [!NOTE]
 > If you need to change ports for debugging, you can do that in the `launchSettings.json` file. See [Container Launch Settings](container-launch-settings.md).
 
 ## Containers window

docs/containers/docker-compose-properties.md

@@ -93,7 +93,7 @@ services:
 
 Typically *docker-compose.override.yml* is used to override certain settings in *docker-compose.yml*. Additionally, Visual Studio generates override files *docker-compose.vs.debug.g.yml* (for **Fast** mode) and *docker-compose.vs.release.g.yml* (for **Regular** mode) files with settings that are specific to running the application inside Visual Studio. You can override these Visual Studio settings by placing a file named *docker-compose.vs.debug.yml* (for **Fast** mode) or *docker-compose.vs.release.yml* (for **Regular** mode) in the same directory as your *docker-compose.yml* file. Right click the Docker Compose project and select **Open Folder in File Explorer** , then use **Add** > **Existing Item** to add the file to your Docker Compose project.
 
->[!TIP]
+> [!TIP]
 > To find out the default values for any of the Visual Studio settings, look in the intermediate output directory (for example, *obj/Docker*) for *docker-compose.vs.debug.g.yml* or *docker-compose.vs.release.g.yml*. These files are generated by Visual Studio and should not be modified.
 
 ### Docker Compose file labels
@@ -125,8 +125,8 @@ Use double quotes around the values, as in the preceding example, and use the ba
 |com.microsoft.visualstudio.debuggee.arguments|The arguments passed to the program when starting debugging. For .NET Core apps, these arguments are typically additional search paths for NuGet packages followed by the path to the project's output assembly.|
 |com.microsoft.visualstudio.debuggee.workingdirectory|The directory used as the starting directory when starting debugging. This setting is typically */app* for Linux containers, or *C:\app* for Windows containers.|
 |com.microsoft.visualstudio.debuggee.killprogram|This command is used to stop the debuggee program that's running inside of the container (when necessary).|
-|com.microsoft.visualstudio.debuggee.noattach.program|The program launched when you use **Start without debugging** (**Ctrl**+**F5**) in an Azure Functions project that runs in an [isolated process](/azure/azure-functions/dotnet-isolated-process-guide). Typically both **F5** and **Ctrl**+**F5** uses the same program, but if any project type like Azure Functions in an isolated process requires a different program than **F5**, then this will be used.|
-|com.microsoft.visualstudio.debuggee.noattach.arguments|The arguments passed to the program when you use **Start without debugging** (**Ctrl**+**F5**) in an Azure Functions project that runs in an isolated process.|
+|com.microsoft.visualstudio.debuggee.noattach.program|The program launched when you use **Start without debugging** (**Ctrl**+**F5**) in an Azure functions project that runs in an [isolated process](/azure/azure-functions/dotnet-isolated-process-guide). Typically both **F5** and **Ctrl**+**F5** uses the same program, but if any project type like Azure Functions in an isolated process requires a different program than **F5**, then this will be used.|
+|com.microsoft.visualstudio.debuggee.noattach.arguments|The arguments passed to the program when you use **Start without debugging** (**Ctrl**+**F5**) in an Azure functions project that runs in an isolated process.|
 :::moniker-end
 
 ### Customize the Docker build process

docs/containers/edit-and-refresh.md

@@ -49,7 +49,7 @@ If you have a project and you've added Docker support as described in the [overv
 
 ### Edit your Razor pages and refresh
 
-To quickly iterate changes in your Razor pages, you can start your application in a container. Then, continue to make changes, viewing them as you would with IIS Express.
+To quickly iterate changes in your Razor pages, you can start your application in a container. Then, continue to make changes, viewing them as you would with Internet Information Services (IIS) Express.
 
 1. Make sure that Docker is set up to use the container type (Linux or Windows) that you are using. Right-click on the Docker icon on the Taskbar, and choose **Switch to Linux containers** or **Switch to Windows containers** as appropriate.
 

docs/containers/includes/vs-2019/container-tools.md

@@ -69,7 +69,7 @@ Select **Docker** from the debug dropdown list in the toolbar, and start debuggi
 
 The **Container Tools** option in the **Output** window shows what actions are taking place. The first time, it might take a while to download the base image, but it's much faster on subsequent runs.
 
->[!NOTE]
+> [!NOTE]
 > If you need to change ports for debugging, you can do that in the *launchSettings.json* file. See [Container Launch Settings](../../container-launch-settings.md).
 
 ## Containers window

docs/containers/launch-profiles.md

@@ -90,7 +90,7 @@ In the example below, the `web1` Compose profile is selected, which filters the
 
 !["Screenshot of launch settings dialog box"](media/launch-settings/launch-settings-create-profile.png)
 
->[!NOTE]
+> [!NOTE]
 > The Docker Compose profiles section only appears if there are profiles defined in your *docker-compose.yml* files.
 
 The next example demonstrates selecting between individual services instead of filtering to the services in a Compose profile. Here, we show how the dialog would look if you created a new launch profile named `test2` that only starts two out of the five services, `webapplication1` with debugging and `webapplication2` without debugging. This launch profile also launches a browser when the application starts and opens it to the home page of `webapplication1`.

docs/containers/view-and-diagnose-containers.md

@@ -141,7 +141,7 @@ To open files in Visual Studio, browse to the file and double-click it, or right
 ![Screenshot of file open for viewing in Visual Studio.](media/view-and-diagnose-containers/vs-2022/container-file-open.png)
 :::moniker-end
 
-Using the **Files** tab, you can view application logs such as IIS logs, configuration files, and other content files in your container's filesystem.
+Using the **Files** tab, you can view application logs such as Internet Information Services (IIS) logs, configuration files, and other content files in your container's filesystem.
 
 :::moniker range=">=vs-2022"
 In Visual Studio 2022 version 17.7 or later, when targeting .NET 8 or later, the Dockerfile might contain the  `USER app` command, which specifies to run the app with normal user permissions. The **Files** tab uses those permissions as well, and so you might not be able to view some folders, if those folders are set to require elevated permissions to view.

docs/cross-platform/cross-platform-mobile-development-in-visual-studio.md

@@ -4,7 +4,7 @@ description: Build cross-platform mobile applications for Android, iOS, and Wind
 titleSuffix: ""
 ms.date: 08/26/2022
 ms.subservice: mobile-development
-ms.topic: "conceptual"
+ms.topic: conceptual
 author: therealjohn
 ms.author: johmil
 ---
@@ -15,7 +15,7 @@ You can build apps for Android, iOS, and Windows devices by using Visual Studio.
 
 Build your apps by using C# and the .NET Framework, HTML and JavaScript, or C++. Share code, strings, images, and in some cases even the user interface.
 
-If you want to build a game or immersive graphical app, install Visual Studio tools for Unity and enjoy all of the powerful productivity features of Visual Studio with Unity, the popular cross-platform game/graphics engine and development environment for apps that run on iOS, Android, Windows, and other platforms.
+If you want to build a game or immersive graphical app, install Visual Studio Tools for Unity (VSTU) and enjoy all of the powerful productivity features of Visual Studio with Unity, the popular cross-platform game/graphics engine and development environment for apps that run on iOS, Android, Windows, and other platforms.
 
 ## Build an app for Android, iOS, and Windows (.NET Framework)
 
@@ -110,9 +110,9 @@ As you write code in these libraries, you can use IntelliSense to explore the na
 
 <a name="Unity"></a>
 
-## Build a cross-platform game for Android, iOS, and Windows by using Visual Studio tools for Unity
+## Build a cross-platform game for Android, iOS, and Windows by using Visual Studio Tools for Unity
 
-Visual Studio Tools for Unity is a free extension for Visual Studio that integrates Visual Studio's powerful code editing, productivity, and debugging tools with *Unity*, the popular cross-platform gaming/graphics engine and development environment for immersive apps that target Windows, iOS, Android, and other platforms including the web.
+Visual Studio Tools for Unity (VSTU) is a free extension for Visual Studio that integrates Visual Studio's powerful code editing, productivity, and debugging tools with *Unity*, the popular cross-platform gaming/graphics engine and development environment for immersive apps that target Windows, iOS, Android, and other platforms including the web.
 
  :::image type="content" source="../cross-platform/media/vstu_overview.png" alt-text="Screenshot showing the overview of Visual Studio Tools for Unity and development environment.":::
 

docs/data-tools/add-custom-controls-to-the-data-sources-window.md

@@ -34,7 +34,7 @@ To add or remove controls from the list of available controls for items in the D
 
 1. Make sure that the WPF Designer or the Windows Forms Designer is open.
 
-2. In the **Data Sources** window, click an item that is part of a data source you added to the window, and then click the dropdown list menu for the item.
+2. In the **Data Sources** window, click an item that is part of a data source you added to the window, and then select the dropdown list menu for the item.
 
    > [!TIP]
    > If the Data Sources window isn't open, open it by selecting **View** > **Other Windows** > **Data Sources**.
@@ -60,7 +60,7 @@ To add or remove controls from the list of available controls for items in the D
 
 6. Click **OK**.
 
-7. In the **Data Sources** window, click an item of the data type that you just associated one or more controls, and then click the dropdown list menu for the item.
+7. In the **Data Sources** window, click an item of the data type that you just associated one or more controls, and then select the dropdown list menu for the item.
 
      The controls you selected in the **Associated controls** box now appear in the dropdown list menu for the item.
 

docs/data-tools/bind-wpf-controls-to-a-dataset.md

@@ -72,17 +72,17 @@ Before you can create data-bound controls, you must define a data model for your
 
    The **Data Source Configuration** wizard opens.
 
-3. On the **Choose a Data Source Type** page, select **Database**, and then click **Next**.
+3. On the **Choose a Data Source Type** page, select **Database**, and then select **Next**.
 
-4. On the **Choose a Database Model** page, select **Dataset**, and then click **Next**.
+4. On the **Choose a Database Model** page, select **Dataset**, and then select **Next**.
 
 5. On the **Choose Your Data Connection** page, select one of the following options:
 
-   - If a data connection to the AdventureWorksLT sample database is available in the dropdown list, select it and then click **Next**.
+   - If a data connection to the AdventureWorksLT sample database is available in the dropdown list, select it, and then select **Next**.
 
    - Click **New Connection**, and create a connection to the AdventureWorksLT database.
 
-6. On the **Save the Connection String to the Application Configure File** page, select the **Yes, save the connection as** checkbox, and then click **Next**.
+6. On the **Save the Connection String to the Application Configure File** page, select the **Yes, save the connection as** checkbox, and then select **Next**.
 
 7. On the **Choose Your Database Objects** page, expand **Tables**, and then select the **Product (SalesLT)** table.
 
@@ -236,7 +236,7 @@ Build and run the application. Verify that you can view and update product recor
 
     - You can click the **>** or **<** buttons to navigate through other product records.
 
-2. In one of the product records, change the **Size** value, and then click **Save changes**.
+2. In one of the product records, change the **Size** value, and then select **Save changes**.
 
 3. Close the application, and then restart the application by pressing **F5** in Visual Studio.
 

docs/data-tools/bind-wpf-controls-to-a-wcf-data-service.md

@@ -78,7 +78,7 @@ To expose data to an application by using a WCF Data Service, you must define a
 
     - Click **New Connection**, and create a connection to the AdventureWorksLT database.
 
-6. On the **Choose Your Data Connection** page, make sure that the **Save entity connection settings in App.Config as** option is selected, and then click **Next**.
+6. On the **Choose Your Data Connection** page, make sure that the **Save entity connection settings in App.Config as** option is selected, and then select **Next**.
 
 7. On the **Choose Your Database Objects** page, expand **Tables**, and then select the **SalesOrderHeader** table.
 
@@ -135,15 +135,15 @@ To display the data from the WCF Data Service, create a new WPF application with
 
    The **Data Source Configuration** wizard opens.
 
-7. In the **Choose a Data Source Type** page of the wizard, select **Service**, and then click **Next**.
+7. In the **Choose a Data Source Type** page of the wizard, select **Service**, and then select **Next**.
 
 8. In the **Add Service Reference** dialog box, click **Discover**.
 
    Visual Studio searches the current solution for available services, and adds `AdventureWorksService.svc` to the list of available services in the **Services** box.
 
 9. In the **Namespace** box, type **AdventureWorksService**.
 
-10. In the **Services** box, click **AdventureWorksService.svc**, and then click **OK**.
+10. In the **Services** box, click **AdventureWorksService.svc**, and then select **OK**.
 
     Visual Studio downloads the service information and then returns to the **Data Source Configuration** wizard.
 
@@ -293,7 +293,7 @@ Build and run the application to verify that you can view and update customer re
 
     - You can click the **>** or **<** buttons to navigate through other sales records.
 
-5. In one of the sales records, type some text in the **Comment** box, and then click **Save changes**.
+5. In one of the sales records, type some text in the **Comment** box, and then select **Save changes**.
 
 6. Close the application, and then start the application again from Visual Studio.
 

docs/data-tools/connect-to-data-in-an-access-database-windows-forms.md

@@ -76,7 +76,7 @@ Connect to databases created with Microsoft 365, Access 2016, Access 2013, Acces
 
 8. Choose **Browse** next to **Database file name**, and then navigate to your `.accdb` file and choose **Open**.
 
-   >[!NOTE]
+   > [!NOTE]
    > If the bitness (32-bit or 64-bit) of Microsoft Office and Visual Studio do not match, you will see an error while connecting to an Access database. In Visual Studio 2019, you will get an error that the database provider is not registered. In Visual Studio 2022, you will see an error that you can't connect to a 32-bit data provider. To resolve this error, make sure that if you are using a 32-bit version of Office, you are using Visual Studio 2019 or earlier; for a 64-bit version of Office, you need Visual Studio 2022 or later.
 
 9. Enter a user name and password (if necessary), and then choose **OK**.
@@ -140,7 +140,7 @@ Connect to databases created with Microsoft 365, Access 2016, Access 2013, Acces
 
 8. Choose **Browse** next to **Database file name**, and then navigate to your `.accdb` file and choose **Open**.
 
-   >[!NOTE]
+   > [!NOTE]
    > If the bitness (32-bit or 64-bit) of Microsoft Office and Visual Studio do not match, you will see an error while connecting to an Access database. In Visual Studio 2019, you will get an error that the database provider is not registered. In Visual Studio 2022, you will see an error that you can't connect to a 32-bit data provider. To resolve this error, make sure that if you are using a 32-bit version of Office, you are using Visual Studio 2019 or earlier; for a 64-bit version of Office, you need Visual Studio 2022 or later.
 
 9. Enter a user name and password (if necessary), and then choose **OK**.

docs/data-tools/could-not-retrieve-schema-information-for-database-object-object-name.md

@@ -9,7 +9,7 @@ manager: mijacobs
 ms.subservice: data-tools
 ---
 
-# Could not retrieve schema information for database object \<object name>
+# Could not retrieve schema information for database object
 
 This message typically appears when an object in **Server Explorer** or **Database Explorer** is copied to the clipboard, deleted from the database, and then pasted onto the designer. Because the database object no longer exists, this message appears.
 

docs/data-tools/create-a-simple-data-application-by-using-adonet.md

@@ -225,7 +225,7 @@ To complete the NewCustomer form logic, follow these steps.
 
 ### FillOrCancel form
 
-The FillOrCancel form runs a query to return an order when you enter an order ID and then click the **Find Order** button. The returned row appears in a read-only data grid. You can mark the order as canceled (X) if you select the **Cancel Order** button, or you can mark the order as filled (F) if you select the **Fill Order** button. If you select the **Find Order** button again, the updated row appears.
+The FillOrCancel form runs a query to return an order when you enter an order ID, and then select the **Find Order** button. The returned row appears in a read-only data grid. You can mark the order as canceled (X) if you select the **Cancel Order** button, or you can mark the order as filled (F) if you select the **Fill Order** button. If you select the **Find Order** button again, the updated row appears.
 
 #### Create autogenerated event handlers