Incorporated content from the internal file

Author: yossi-karp

articles/data-explorer/ingest-data-streaming.md

@@ -15,11 +15,6 @@ Streaming ingestion is targeted for scenarios that require low latency with an i
 
 Use the classic (bulk) ingestion instead of streaming ingestion when the amount of data grows to more than 1 MB per second per table. Read [Data ingestion overview](/azure/data-explorer/ingest-data-overview) to learn more about the various methods of ingestion.
 
-> [!NOTE]
-> Streaming ingestion doesn't support the following features:
-> * [Database cursors](/azure/kusto/management/databasecursor).
-> * [Data mapping](/azure/kusto/management/mappings). Only [pre-created](/azure/kusto/management/tables#create-ingestion-mapping) data mapping is supported. 
-
 ## Prerequisites
 
 * If you don't have an Azure subscription, create a [free Azure account](https://azure.microsoft.com/free/) before you begin.
@@ -28,6 +23,9 @@ Use the classic (bulk) ingestion instead of streaming ingestion when the amount
 
 ## Enable streaming ingestion on your cluster
 
+> [!WARNING]
+> Please review the [limitations](#limitations) prior to enabling steaming ingestion.
+
 1. In the Azure portal, go to your Azure Data Explorer cluster. In **Settings**, select **Configurations**. 
 1. In the **Configurations** pane, select **On** to enable **Streaming ingestion**.
 1. Select **Save**.
@@ -44,8 +42,9 @@ Use the classic (bulk) ingestion instead of streaming ingestion when the amount
 
 There are two supported streaming ingestion types:
 
-* [Event Hub](/azure/data-explorer/ingest-data-event-hub) used as a data source
-* Custom ingestion requires you to write an application that uses one of Azure Data Explorer client libraries. See [streaming ingestion sample](https://github.com/Azure/azure-kusto-samples-dotnet/tree/master/client/StreamingIngestionSample) for a sample application.
+
+* [**Event Hub**](/azure/data-explorer/ingest-data-event-hub) used as a data source
+* **Custom ingestion** requires you to write an application that uses one of the Azure Data Explorer client libraries. See [streaming ingestion sample](https://github.com/Azure/azure-kusto-samples-dotnet/tree/master/client/StreamingIngestionSample) for a sample application.
 
 ### Choose the appropriate streaming ingestion type
 
@@ -74,6 +73,10 @@ There are two supported streaming ingestion types:
 * Enabling streaming ingestion on a cluster, even when data isn't ingested via streaming, uses part of the local SSD disk of the cluster machines for streaming ingestion data and reduces the storage available for hot cache.
 * [Extent tags](/azure/kusto/management/extents-overview.md#extent-tagging) can't be set on the streaming ingestion data.
 
+Streaming ingestion doesn't support the following features:
+* [Database cursors](/azure/kusto/management/databasecursor).
+* [Data mapping](/azure/kusto/management/mappings). Only [pre-created](/azure/kusto/management/tables#create-ingestion-mapping) data mapping is supported. 
+
 ## Next steps
 
 * [Query data in Azure Data Explorer](web-query-data.md)