From 8ea1ba60d3293aeeffb6e9fd87f1509869ea7a04 Mon Sep 17 00:00:00 2001
From: Joey Caparas <macapara@microsoft.com>
Date: Fri, 19 May 2017 15:33:16 -0700
Subject: [PATCH] fix warning and note

---
 ...gration-windows-defender-advanced-threat-protection.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/windows/threat-protection/windows-defender-atp/enable-siem-integration-windows-defender-advanced-threat-protection.md b/windows/threat-protection/windows-defender-atp/enable-siem-integration-windows-defender-advanced-threat-protection.md
index e995968888..53cc303fdd 100644
--- a/windows/threat-protection/windows-defender-atp/enable-siem-integration-windows-defender-advanced-threat-protection.md
+++ b/windows/threat-protection/windows-defender-atp/enable-siem-integration-windows-defender-advanced-threat-protection.md
@@ -29,14 +29,14 @@ Enable security information and event management (SIEM) integration so you can p
 
 2. Select **Enable SIEM integration**. This activates the **SIEM connector access details** section with pre-populated values and an application is created under you Azure Active Directory (AAD) tenant.
 
-  WARNING:<br>
-  The client secret is only displayed once. Make sure you keep a copy of it in a safe place.<br>
+  > [!WARNING]
+  >The client secret is only displayed once. Make sure you keep a copy of it in a safe place.<br>
   For more information about getting a new secret see, [Learn how to get a new secret](troubleshoot-custom-ti-windows-defender-advanced-threat-protection.md#learn-how-to-get-a-new-client-secret).
 
 3. Choose the SIEM type you use in your organization.
 
-  NOTE:<br>
-  If you select HP ArcSight, you'll need to save these two configuration files:<br>
+  > [!NOTE]
+  > If you select HP ArcSight, you'll need to save these two configuration files:<br>
   - WDATP-connector.jsonparser.properties
   - WDATP-connector.properties <br>