fixed merge conflicts from private repo

windows/deployment/deploy-windows-mdt/set-up-mdt-for-bitlocker.md

@@ -11,6 +11,7 @@ ms.mktglfcycl: deploy
 ms.localizationpriority: medium
 ms.sitesec: library
 ms.pagetype: mdt
+audience: itpro
 author: greg-lindsay
 ms.topic: article
 ---
@@ -138,12 +139,12 @@ cscript.exe SetConfig.vbs SecurityChip Active
 
 When configuring a task sequence to run any BitLocker tool, either directly or using a custom script, it is helpful if you also add some logic to detect whether the BIOS is already configured on the machine. In the following task sequence, we are using a sample script (ZTICheckforTPM.wsf) from the Deployment Guys web page to check the status on the TPM chip. You can download this script from the Deployment Guys Blog post, [Check to see if the TPM is enabled](https://go.microsoft.com/fwlink/p/?LinkId=619549). 
 
-We have added these five actions to the task sequence:
+In the following task sequence, we added five actions:
 -   **Check TPM Status.** Runs the ZTICheckforTPM.wsf script to determine if TPM is enabled. Depending on the status, the script will set the TPMEnabled and TPMActivated properties to either true or false.
 -   **Configure BIOS for TPM.** Runs the vendor tools (in this case, HP, Dell, and Lenovo). To ensure this action is run only when necessary, add a condition so the action is run only when the TPM chip is not already activated. Use the properties from the ZTICheckforTPM.wsf.
-
-    > [!NOTE]
-    > It is common for organizations to wrap these tools in scripts to get additional logging and error handling.
+    **Note**  
+    It is common for organizations to wrap these tools in scripts to get additional logging and error handling.
+     
 -   **Restart computer.** Self-explanatory, reboots the computer.
 -   **Check TPM Status.** Runs the ZTICheckforTPM.wsf script one more time.
 -   **Enable BitLocker.** Runs the built-in action to activate BitLocker.