diff --git a/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index a34a6aa5a7..543b74e677 100644
--- a/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/configuration/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -1430,11 +1430,14 @@ To change the level of diagnostic and usage data sent when you **Send your devic
 
    -or-
 
--   Apply the Group Policy: **Computer Configuration\\Administrative Templates\\Windows Components\\Data Collection And Preview Builds\\Allow Telemetry**
+-   Apply the Group Policy: **Computer Configuration\\Administrative Templates\\Windows Components\\Data Collection And Preview Builds\\Allow Telemetry** and select the appropriate option for your deployment. 
 
    -or-
 
--   Create a REG\_DWORD registry setting in **HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DataCollection\\AllowTelemetry**, with a value of 0 (zero).
+-   Create a REG\_DWORD registry setting in **HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows\\DataCollection\\AllowTelemetry**, with a value of 0-3, as appropriate for your deployment (see below for the values for each level). 
+
+> [!NOTE] 
+> If the **Security** option is configured by using Group Policy or the Registry, the value will not be reflected in the UI.
 
    -or-
 
diff --git a/windows/device-security/bitlocker/bitlocker-basic-deployment.md b/windows/device-security/bitlocker/bitlocker-basic-deployment.md
index 9a2d09f6a4..529ff6e574 100644
--- a/windows/device-security/bitlocker/bitlocker-basic-deployment.md
+++ b/windows/device-security/bitlocker/bitlocker-basic-deployment.md
@@ -17,14 +17,7 @@ ms.date: 04/19/2017
 
 This topic for the IT professional explains how BitLocker features can be used to protect your data through drive encryption.
 
-The following sections provide information that will help you put together your basic deployment plan for implementing BitLocker in your organization:
-
--   [Using BitLocker to encrypt volumes](#bkmk-dep1)
--   [Down-level compatibility](#bkmk-dep2)
--   [Using manage-bde to encrypt volumes with BitLocker](#bkmk-dep3)
--   [Using PowerShell to encrypt volumes with BitLocker](#bkmk-dep4)
-
-## <a href="" id="bkmk-dep1"></a>Using BitLocker to encrypt volumes
+## Using BitLocker to encrypt volumes
 
 BitLocker provides full volume encryption (FVE) for operating system volumes, as well as fixed and removable data volumes. To support fully encrypted operating system volumes, BitLocker uses an unencrypted system volume for the files required to boot, decrypt, and load the operating system. This volume is automatically created during a new installation of both client and server operating systems.