Merge pull request #90465 from orspod/2019-10-PR-fixes

PR review non-blocking issues

Author: PRMerger6

articles/data-explorer/create-cluster-database-resource-manager.md

@@ -105,7 +105,7 @@ You can deploy the Azure Resource Manager template by [using the Azure portal](#
 
     ![Deploy to Azure](media/create-cluster-database-resource-manager/deploy-2-azure.png)
 
-You can [edit and deploy the template in the Azure portal](/azure/azure-resource-manager/resource-manager-quickstart-create-templates-use-the-portal#edit-and-deploy-the-template) by using the form.
+    You can [edit and deploy the template in the Azure portal](/azure/azure-resource-manager/resource-manager-quickstart-create-templates-use-the-portal#edit-and-deploy-the-template) by using the form.
 
 1. Complete **BASICS** and **SETTINGS** sections. Select unique cluster and database names.
 It takes a few minutes to create an Azure Data Explorer cluster and database.
@@ -135,9 +135,9 @@ It takes a few minutes to create an Azure Data Explorer cluster and database.
 1. Right-click the shell console, and then select **Paste**.
 It takes a few minutes to create an Azure Data Explorer cluster and database.
 
-#### Verify the deployment using powershell
+#### Verify the deployment using PowerShell
 
-To verify the deployment, use the following Azure PowerShell script.  If the Cloud shell is still open, you don't need to copy/run the first line (Read-Host). For more information regarding managing Azure Data Explorer resources in PowerShell, read [Az.Kusto](/powershell/module/az.kusto/?view=azps-2.7.0). Make relevant changes
+To verify the deployment, use the following Azure PowerShell script.  If the Cloud Shell is still open, you don't need to copy/run the first line (Read-Host). For more information regarding managing Azure Data Explorer resources in PowerShell, read [Az.Kusto](/powershell/module/az.kusto/?view=azps-2.7.0). 
 
 ```azurepowershell-interactive
 $projectName = Read-Host -Prompt "Enter the same project name that you used in the last procedure"
@@ -158,9 +158,9 @@ When the Azure resources are no longer needed, clean up the resources you deploy
 
 Delete the resources in the Azure portal by following the steps in [clean up resources](create-cluster-database-portal.md#clean-up-resources).
 
-### Clean up resources using powershell
+### Clean up resources using PowerShell
 
-If the Cloud shell is still open, you don't need to copy/run the first line (Read-Host).
+If the Cloud Shell is still open, you don't need to copy/run the first line (Read-Host).
 
 ```azurepowershell-interactive
 $projectName = Read-Host -Prompt "Enter the same project name that you used in the last procedure"

articles/data-explorer/power-bi-best-practices.md

@@ -25,13 +25,13 @@ When working with terabytes of fresh raw data, follow these guidelines to keep P
 
 * **Import mode versus DirectQuery mode** - Use **Import** mode for interaction of smaller data sets. Use **DirectQuery** mode for large, frequently updated data sets. For example, create dimension tables using **Import** mode since they're small and don't change often. Set the refresh interval according to the expected rate of data updates. Create fact tables using **DirectQuery** mode since these tables are large and contain raw data. Use these tables to present filtered data using Power BI [drillthrough](https://docs.microsoft.com/power-bi/desktop-drillthrough).
 
-* **Parallelism** – Azure Data explorer is a linearly scalable data platform, therefore, you can improve the performance of dashboard rendering by increasing the parallelism of the end-to-end flow as follows:
+* **Parallelism** – Azure Data Explorer is a linearly scalable data platform, therefore, you can improve the performance of dashboard rendering by increasing the parallelism of the end-to-end flow as follows:
 
    * Increase the number of [concurrent connections in DirectQuery in Power BI](https://docs.microsoft.com/power-bi/desktop-directquery-about#maximum-number-of-connections-option-for-directquery).
 
    * Use [weak consistency to improve parallelism](/azure/kusto/concepts/queryconsistency). This may have an impact on the freshness of the data.
 
-* **Effective slicers** – you can use [sync slicers](https://docs.microsoft.com/power-bi/visuals/power-bi-visualization-slicers#sync-and-use-slicers-on-other-pages) to prevent reports from loading data before you're ready. After you structure the data set, place all visuals, and mark all the slicers, you can select the sync slicer to load only the data needed.
+* **Effective slicers** – Use [sync slicers](https://docs.microsoft.com/power-bi/visuals/power-bi-visualization-slicers#sync-and-use-slicers-on-other-pages) to prevent reports from loading data before you're ready. After you structure the data set, place all visuals, and mark all the slicers, you can select the sync slicer to load only the data needed.
 
 * **Use filters** - Use as many Power BI filters as possible to focus the Azure Data Explorer search on the relevant data shards.
 
@@ -43,7 +43,7 @@ The following section includes tips and tricks for using Kusto query language wi
 
 ### Complex queries in Power BI
 
-Complex queries are more easily expressed in Kusto than in Power Query. They should be implemented as [Kusto functions](/azure/kusto/query/functions), and invoked in Power BI. This method is required when using **DirectQuery** with `let` statements in your Kusto query. Since Power BI joins two queries, and `let` statements can't be used with the `join` operator, syntax errors may occur. Therefore, save each portion of the join as a Kusto function and allow Power BI to join these two functions together.
+Complex queries are more easily expressed in Kusto than in Power Query. They should be implemented as [Kusto functions](/azure/kusto/query/functions), and invoked in Power BI. This method is required when using **DirectQuery** with `let` statements in your Kusto query. Because Power BI joins two queries, and `let` statements can't be used with the `join` operator, syntax errors may occur. Therefore, save each portion of the join as a Kusto function and allow Power BI to join these two functions together.
 
 ### How to simulate a relative data-time operator
 
@@ -101,7 +101,7 @@ In **Edit Queries** window, **Home** > **Advanced Editor**
     Source = Kusto.Contents("Help", "Samples", "StormEvents | where State == 'ALABAMA' | take 100", [])
     ```
 
-1. Replace the relevant part of the query with your parameter. Splitting the query into multiple parts, and concatenate them back using the & sign, along with the parameter.
+1. Replace the relevant part of the query with your parameter. Split the query into multiple parts, and concatenate them back using an ampersand (&), along with the parameter.
 
    For example, in the query above, we'll take the `State == 'ALABAMA'` part, and split it to: `State == '` and `'` and we'll place the `State` parameter between them:
    
@@ -136,7 +136,7 @@ You can use a query parameter in any query step that supports it. For example, f
 ### Don't use Power BI data refresh scheduler to issue control commands to Kusto
 
 Power BI includes a data refresh scheduler that can periodically issue
-queries against a data source. This mechanism shouldn't be used to schedule control commands to Kusto, since Power BI assumes all queries are read-only.
+queries against a data source. This mechanism shouldn't be used to schedule control commands to Kusto because Power BI assumes all queries are read-only.
 
 ### Power BI can send only short (<2000 characters) queries to Kusto