Merge pull request #5005 from MicrosoftDocs/repo_sync_working_branch

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

Author: gewarren

docs/containers/edit-and-refresh.md

@@ -125,4 +125,3 @@ Learn how to [troubleshoot Visual Studio Docker development](troubleshooting-doc
 * To build and deploy a Docker container, see [Docker integration for Azure Pipelines](https://aka.ms/dockertoolsforvsts).
 * For an index of Windows Server and Nano Server articles, see [Windows container information](https://aka.ms/containers).
 * Learn about [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/) and review the [Azure Kubernetes Service documentation](/azure/aks).
-

docs/install/update-servicing-baseline.md

@@ -4,7 +4,7 @@ description: Learn how to update Visual Studio while staying on a servicing base
 ms.date: 05/22/2019
 ms.custom: "seodec18"
 ms.topic: conceptual
-ms.assetid: 
+ms.assetid:
 author: doughall
 ms.author: tglee
 manager: jillfra
@@ -15,44 +15,45 @@ ms.technology: vs-installation
 ---
 # Update Visual Studio while on a servicing baseline
 
-Visual Studio 2019 will have frequent updates during its [product lifecycle](/visualstudio/productinfo/release-rhythm#release-channel-updates). Updates will include both minor release updates (for example, from 16.0 to 16.1) that might add new features and components, and servicing updates (for example, from 16.0.4 to 16.0.5) that contain only targeted fixes for critical issues. 
+Visual Studio 2019 will have frequent updates during its [product lifecycle](/visualstudio/productinfo/release-rhythm#release-channel-updates). Updates will include both minor release updates (for example, from 16.0 to 16.1) that might add new features and components, and servicing updates (for example, from 16.0.4 to 16.0.5) that contain only targeted fixes for critical issues.
 
 Enterprise administrators can choose to keep their clients on a servicing baseline. A servicing baseline is supported with servicing updates for a year past the release of the next servicing baseline.
 
 The servicing baseline option gives developers and administrators more flexibility to adopt the new features, bug fixes, or components included in new minor updates. The first servicing baseline is 16.0.x. For more information, see [Support options for enterprise and professional customers](https://docs.microsoft.com/visualstudio/releases/2019/servicing#support-options-for-enterprise-and-professional-customers).
 
 ## How to get onto a servicing baseline
 
-To start using a servicing baseline, download a fixed-version Visual Studio installer bootstrapper from [My.VisualStudio.com](https://my.visualstudio.com/Downloads?q=visual%20studio%202019%20version%2016.0). The bootstrappers have links to the product configurations, workloads, and components for that specific version. 
+To start using a servicing baseline, download a fixed-version Visual Studio installer bootstrapper from [My.VisualStudio.com](https://my.visualstudio.com/Downloads?q=visual%20studio%202019%20version%2016.0). The bootstrappers have links to the product configurations, workloads, and components for that specific version.
 
 > [!NOTE]
 > Be careful to distinguish between the fixed-version bootstrapper and the standard bootstrappers. The standard bootstrappers are configured to use the latest available release of Visual Studio. The standard boostrappers have a number in the file name (for example, vs_enterprise__123456789-123456789.exe) when they're downloaded from My.VisualStudio.com.
 
 During installation, enterprise administrators must configure their clients to prevent the clients from updating to the latest release. You can configure the clients in multiple ways:
 - [Change the `channelUri` setting in the response configuration file](update-servicing-baseline.md#install-a-servicing-baseline-on-a-network) to use a channel manifest in the layout or local folder.
 - [Modify the channelUri through command-line execution](update-servicing-baseline.md#install-a-servicing-baseline-via-the-internet) to use a nonexistent file.
-- [Set policies on the client system to disable updates](update-servicing-baseline.md#use-policy-settings-to-disable-clients-from-updating), to prevent clients from self-updating. 
+- [Set policies on the client system to disable updates](update-servicing-baseline.md#use-policy-settings-to-disable-clients-from-updating), to prevent clients from self-updating.
 
 ### Install a servicing baseline on a network
 
-Administrators who use a network layout installation should modify the `channelUri` value in the *response.json* file in the layout to use the *channelmanifest.json* file that's in the same folder. For the steps to take, see [Control updates to network-based Visual Studio deployments](controlling-updates-to-visual-studio-deployments.md). Changing the `channelUri` value enables clients to look for updates in the layout location. 
+Administrators who use a network layout installation should modify the `channelUri` value in the *response.json* file in the layout to use the *channelmanifest.json* file that's in the same folder. For the steps to take, see [Control updates to network-based Visual Studio deployments](controlling-updates-to-visual-studio-deployments.md). Changing the `channelUri` value enables clients to look for updates in the layout location.
 
 ### Install a servicing baseline via the internet
 
 For an internet-based installation, add `--channelUri` with a non-existent channel manifest to the command-line used to launch setup. This disables Visual Studio from using the latest available release for an update. Here's an example:
-  ```cmd
-   vs_enterprise.exe --channelUri c:\doesnotexist.chman 
-  ```
+
+```cmd
+vs_enterprise.exe --channelUri c:\doesnotexist.chman
+```
 
 ### Use policy settings to disable clients from updating
 
 Another option to control updates on a client is to [turn off update notifications](controlling-updates-to-visual-studio-deployments.md). Use this option if the channelUri value was not changed on installation. It will disable the client from receiving links to the latest available release. A fixed-version bootstrapper is still necessary to update to a specific version on the client.
 
 ## How to stay on a servicing baseline
 
-When an update for a servicing baseline is available, fixed-version bootstrapper files are made available for the servicing update at [My.VisualStudio.com](https://my.visualstudio.com/Downloads?q=visual%20studio%202019%20version%2016.0). 
+When an update for a servicing baseline is available, fixed-version bootstrapper files are made available for the servicing update at [My.VisualStudio.com](https://my.visualstudio.com/Downloads?q=visual%20studio%202019%20version%2016.0).
 
-For administrators deploying via network layout install, the administrator will want to update the [layout location](update-a-network-installation-of-visual-studio.md). Clients that installed from the location will receive update notifications. If the update needs to be deployed to clients, follow [these instructions](update-a-network-installation-of-visual-studio.md#how-to-deploy-an-update-to-client-machines). When modifying the 'response.json' for an update, do not add additional workloads, components, or languages. Managing these settings must be done as a 'modify' deployment after the product has been updated. 
+For administrators deploying via network layout install, the administrator will want to update the [layout location](update-a-network-installation-of-visual-studio.md). Clients that installed from the location will receive update notifications. If the update needs to be deployed to clients, follow [these instructions](update-a-network-installation-of-visual-studio.md#how-to-deploy-an-update-to-client-machines). When modifying the 'response.json' for an update, do not add additional workloads, components, or languages. Managing these settings must be done as a 'modify' deployment after the product has been updated.
 
 For an internet-based installation, run the new fixed version bootstrapper with the `--channelUri` parameter pointing to a non-existent channel manifest on the client. If the update is deployed in quiet or passive mode, use two separate commands:
 
@@ -63,7 +64,7 @@ For an internet-based installation, run the new fixed version bootstrapper with
     ```
 
 2. Update the Visual Studio application itself:
-    
+
     ```cmd
     vs_enterprise.exe update --installPath "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise" --quiet --wait --norestart --channelUri c:\doesnotexist.chman
     ```