Merge pull request #14022 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/visualstudio-docs (branch main)

Author: Albertyang0

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

@@ -18,7 +18,7 @@ All commands require administrative elevation, and a User Account Control prompt
 
 You can use the `^` character at the end of a command line to concatenate multiple lines into a single command. Alternatively, you can place these lines together onto a single row. In PowerShell, the equivalent is the backtick (`` ` ``) character.
 
-To execute commands in a non-interactive manner, you can use`--passive` or `--quiet`. For more information on these parameters, see the [commands and command-line paremeters](use-command-line-parameters-to-install-visual-studio.md#install-update-modify-repair-uninstall-and-export-commands-and-command-line-parameters) page.
+To execute commands in a non-interactive manner, you can use`--passive` or `--quiet`. For more information on these parameters, see the [commands and command-line parameters](use-command-line-parameters-to-install-visual-studio.md#install-update-modify-repair-uninstall-and-export-commands-and-command-line-parameters) page.
 
 For lists of the workloads and components that you can install by using the command line, see the [Visual Studio workload and component IDs](workload-and-component-ids.md) page.
 

docs/install/update-a-network-installation-of-visual-studio.md

@@ -48,7 +48,7 @@ When Visual Studio is initially installed on the client machine, it records the
 
 ::: moniker range="vs-2019"
 
-With default Visual Studio 2019 functionality, once the client has installed the product, the client's update location configuration is locked and unchangable. The only way to *reliably* change the source location for updates is to uninstall and reinstall the product using the correct configuration.
+With default Visual Studio 2019 functionality, once the client has installed the product, the client's update location configuration is locked and unchangeable. The only way to *reliably* change the source location for updates is to uninstall and reinstall the product using the correct configuration.
 
 However, if the Visual Studio client uses the latest Visual Studio 2022 Installer, then the client's source location for updates can be changed. This is useful if you want to install from one layout but have updates come from another layout. There are several ways to get the Visual Studio 2022 Installer onto a client machine. The easiest way is to use any version of Visual Studio that was shipped after June 2023, because these versions automatically contain the latest installer. Another way is to install and use the Visual Studio 2022 product. Lastly, you can [distribute the Visual Studio 2022 Installer via your Visual Studio 2019 layouts](create-a-network-installation-of-visual-studio.md#configure-the-layout-to-always-include-and-provide-the-latest-installer).
 

docs/test/intellitest-manual/static-helper-classes.md

@@ -152,7 +152,7 @@ public static void AreElementsNotNull<T>(T[] value)
     where T : class
 {
     PexAssume.NotNull(value);
-    // the followings prevents the exploration of all array lengths
+    // the following prevents the exploration of all array lengths
     int len = PexSymbolicValue.Ignore<int>(value.Length);
 
     // building up a boolean value as follows prevents exploration

docs/test/intellitest-manual/warnings-and-errors.md

@@ -136,7 +136,7 @@ You can use
 void ParameterizedTest(int n) {
     int nshadow = PexSymbolicValue.Ignore(n); // IntelliTest looses track of 'n'
 
-    // irrevelant for MaxConditions, since nshadow is not related to input
+    // irrelevant for MaxConditions, since nshadow is not related to input
     for (int i=0; i<nshadow; i++)
     {...}
 }