Merge pull request #105786 from yossi-karp/streaming-fix-conflicts

Fix conflicts and English and stylistic changes

Author: PMEds28

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

@@ -11,9 +11,9 @@ ms.date: 08/30/2019
 
 # Streaming ingestion (Preview)
 
-Streaming ingestion is targeted for scenarios that require low latency with an ingestion time of less than 10 seconds for varied volume data. It's used to optimize operational processing of many tables, in one or more databases, where the stream of data into each table is relatively small (few records per second) but overall data ingestion volume is high (thousands of records per second).
+Use streaming ingestion when you require low latency with an ingestion time of less than 10 seconds for varied volume data. It's used to optimize operational processing of many tables, in one or more databases, where the stream of data into each table is relatively small (few records per second) but overall data ingestion volume is high (thousands of records per second). 
 
-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.
+Use 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.
 
 ## Prerequisites
 
@@ -43,22 +43,22 @@ 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
+* [**Event Hub**](/azure/data-explorer/ingest-data-event-hub), which is 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
 
 |   |Event Hub  |Custom Ingestion  |
 |---------|---------|---------|
-|Data delay between ingestion initiation and the data available for query   |    longer delay     |   shorter delay      |
-|Development overhead    |   fast and easy setup, no development overhead    |   high development overhead for application to handle errors and ensure data consistency     |
+|Data delay between ingestion initiation and the data available for query   |    Longer delay     |   Shorter delay      |
+|Development overhead    |   Fast and easy setup, no development overhead    |   High development overhead for application to handle errors and ensure data consistency     |
 
 ## Disable streaming ingestion on your cluster
 
 > [!WARNING]
-> Disabling streaming ingestion may take a few hours.
+> Disabling streaming ingestion could take a few hours.
 
-1. Drop [streaming ingestion policy](/azure/kusto/management/streamingingestionpolicy) from all relevant tables and databases. The streaming ingestion policy removal triggers streaming ingestion data movement from the initial storage to the permanent storage in the column store (extents or shards). The data movement can last between a few seconds to a few hours, depending on the amount of data in the initial storage and how the CPU and memory is used by the cluster.
+1. Drop [streaming ingestion policy](/azure/kusto/management/streamingingestionpolicy) from all relevant tables and databases. The streaming ingestion policy removal triggers streaming ingestion data movement from the initial storage to the permanent storage in the column store (extents or shards). The data movement can last between a few seconds to a few hours, depending on the amount of data in the initial storage, and how the CPU and memory is used by the cluster.
 1. In the Azure portal, go to your Azure Data Explorer cluster. In **Settings**, select **Configurations**. 
 1. In the **Configurations** pane, select **Off** to disable **Streaming ingestion**.
 1. Select **Save**.
@@ -67,16 +67,13 @@ There are two supported streaming ingestion types:
 
 ## Limitations
 
+* Streaming ingestion doesn't support [Database cursors](/azure/kusto/management/databasecursor) or [Data mapping](/azure/kusto/management/mappings). Only [pre-created](/azure/kusto/management/tables#create-ingestion-mapping) data mapping is supported. 
 * Streaming ingestion performance and capacity scales with increased VM and cluster sizes. Concurrent ingestions are limited to six ingestions per core. For example, for 16 core SKUs, such as D14 and L16, the maximal supported load is 96 concurrent ingestions. For two core SKUs, such as D11, the maximal supported load is 12 concurrent ingestions.
 * The data size limitation per ingestion request is 4 MB.
-* Schema updates, such as creation and modification of tables and ingestion mappings, may take up to 5 minutes for the streaming ingestion service.
+* Schema updates, such as creation and modification of tables and ingestion mappings, may take up to five minutes for the streaming ingestion service.
 * 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#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/create-ingestion-mapping-command) data mapping is supported. 
-
 ## Next steps
 
 * [Query data in Azure Data Explorer](web-query-data.md)