more

Author: CarlRabeler

docs/relational-databases/extended-events/targets-for-extended-events-in-sql-server.md

@@ -1,7 +1,7 @@
 ---
 title: "Targets for Extended Events in SQL Server | Microsoft Docs"
 ms.custom: ""
-ms.date: "04/17/2018"
+ms.date: "09/07/2018"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
 ms.reviewer: ""
@@ -82,7 +82,7 @@ SQL Server extended events can inter-operate with Event Tracing for Windows (ETW
 This ETW target processes *synchronously* the data it receives, whereas most targets process *asynchronously*.
 
 > [!NOTE]
-> Azure SQL Database does not support the ETW target. Nor does Azure SQL Database Managed Instance.
+> Azure SQL Database does not support the `etw_classic_sync_target target`.
 
 <!-- After OPS Versioning is live, the above !NOTE could be converted into a "3colon ZONE".  GeneMi = MightyPen. -->
 
@@ -151,7 +151,7 @@ The **event_file** target writes event session output from buffer to a disk file
 ::: moniker range="= azuresqldb-current || = azuresqldb-mi-current || = sqlallproducts-allversions"
 
 > [!NOTE]
-> Azure SQL Database supports the **event_file** target, but only by using a blob in Azure Storage for the output. SQL Database cannot store event output in a file on your local harddrive.
+> Azure SQL Database only supports storing `xel` files on Azure blob storage. 
 >
 > For an **event_file** code example particular to SQL Database (and to SQL Database Managed Instance), see [Event File target code for extended events in SQL Database](https://docs.microsoft.com/azure/sql-database/sql-database-xevent-code-event-file).