Merge pull request #10639 from MicrosoftDocs/main638761901036615150sync_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/ide/create-csharp-winform-visual-studio.md

@@ -2,7 +2,7 @@
 title: "Create a Windows Forms app with C#"
 description: Create a Windows Forms app in Visual Studio with C#, add button controls to the form, and run the code to test your application.
 ms.custom: vs-acquisition
-ms.date: 01/24/2025
+ms.date: 02/26/2025
 ms.topic: tutorial
 ms.devlang: csharp
 author: anandmeg
@@ -114,8 +114,8 @@ After you select your C# project template and name your project, Visual Studio o
 
    :::image type="content" source="../ide/media/vb-button-control-function.png" alt-text="Screenshot showing the new name for the button.":::
 
-   > [!NOTE]
-   > If you alphabetized the list in the **Properties** window, **Button1** appears in the **(DataBindings)** section, instead.
+   If you alphabetized the list in the **Properties** window, **Button1** appears in the **(DataBindings)** section, instead.
+   You can [dock or anchor](/dotnet/desktop/winforms/controls/how-to-dock-and-anchor) the controls on your form to help with automatic placement and sizing, when the form changes size.
 
 ### Add a label to the form
 
@@ -167,8 +167,8 @@ After you select your C# project template and name your project, Visual Studio o
 
      :::image type="content" source="media/vs-2022/csharp-winform-button-properties-design-name.png" alt-text="Screenshot that shows the new name for the button.":::
 
-   > [!NOTE]
-   > If you alphabetized the list in the **Properties** window, **button1** appears in the **(DataBindings)** section, instead.
+   If you alphabetized the list in the **Properties** window, **Button1** appears in the **(DataBindings)** section, instead.
+   You can [dock or anchor](/dotnet/desktop/winforms/controls/how-to-dock-and-anchor) the controls on your form to help with automatic placement and sizing, when the form changes size.
 
 ### Add a label to the form
 

docs/ide/how-to-change-fonts-and-colors-in-visual-studio.md

@@ -2,7 +2,7 @@
 title: Change themes, fonts, text, & accessibility options in Visual Studio
 description: Learn how to change Visual Studio color themes, font colors, text sizes, extra-contrast colors, and more for ease of use and accessibility concerns.
 titleSuffix: ''
-ms.date: 1/7/2025
+ms.date: 2/26/2025
 ms.topic: how-to
 helpviewer_keywords:
 - Visual Studio, color themes
@@ -45,8 +45,8 @@ Here's how to change the color theme of the IDE frame and the tool windows in Vi
 
    :::image type="content" source="media/vs-2022/fonts-colors-theme.png" alt-text="Screenshot of the Options dialog box where you can change the color theme.":::
 
-   > [!NOTE]
-   > When you change a color theme, text in the IDE reverts to the default or previously customized fonts and sizes for that theme.
+Visual Studio remembers the color theme and other UI settings, and synchronizes them across all Visual Studio environments depending on your [account setup](signing-in-to-visual-studio.md#sign-in-to-your-account-1).
+With Visual Studio 2022 version 17.12, your [font settings are preserved across theme changes](#preserve-font-settings-across-theme-changes).
 
    > [!TIP]
    > Want even more themes to choose from? Check out the wide range of custom themes on the [**Visual Studio Marketplace**](https://marketplace.visualstudio.com/search?target=VS&category=Tools&vsVersion=&subCategory=Themes&sortBy=Installs). And to see examples of new Visual Studio 2022 custom themes based on VS Code, take a look at the [**Introducing a collection of new Visual Studio themes**](https://devblogs.microsoft.com/visualstudio/custom-themes/) blog post. 

docs/install/command-line-parameter-examples.md

@@ -50,24 +50,26 @@ For lists of the workloads and components that you can install by using the comm
    \\layoutserver\share\path\vs_enterprise.exe update --wait --passive --norestart --installPath "C:\installPathVS"
    ```
 
-Alternatively, you can also update your Visual Studio instance in one step by using the installer on the client. [Standard users, if they've been granted appropriate permissions](https://aka.ms/vs/setup/policies), can programmatically execute the update command using the installer, but they aren't allowed to use the `--passive` or `--quiet` switch. Note that you can't initiate the installer programmatically from the same directory that the installer resides in.
+  Alternatively, you can also update your Visual Studio instance in one step by using the installer on the client. Note that you can't initiate the installer programmatically from the same directory that the installer resides in.
 
    ```shell
    "C:\Program Files (x86)\Microsoft Visual Studio\Installer\setup.exe" update --passive --norestart --installPath "C:\installPathVS"
    ```
 
+  [Standard users, if they've been granted appropriate permissions](https://aka.ms/vs/setup/policies), can programmatically execute the update command using the installer, but they aren't allowed to use the `--passive` or `--quiet` switch. 
+
 ## Using --wait
 
 * Use `--wait` in batch files or scripts to wait for the initial command to complete before the next command is executed. For batch files, an `%ERRORLEVEL%` environment variable contains the return value of the command, as documented in the [Use command-line parameters to install Visual Studio](use-command-line-parameters-to-install-visual-studio.md) page. Some command utilities require other parameters to wait for completion and to get the installer's return value. 
 
-The `--wait` parameter is only supported by the bootstrapper. 
+  The `--wait` parameter is only supported by the bootstrapper. 
 
    ```shell
    start /wait vs_professional.exe --installPath "C:\VS" --passive --wait > nul
    echo %errorlevel%
    ```
 
-The following command is an example of using `--wait` with the PowerShell script command `Start-Process`:
+  The following command is an example of using `--wait` with the PowerShell script command `Start-Process`:
 
    ```powershell
    $process = Start-Process -FilePath vs_enterprise.exe -ArgumentList "--installPath", "C:\VS", "--passive", "--wait" -Wait -PassThru