corrections and a few more

Author: KingdomOfEnds

articles/time-series-insights/how-to-connect-power-bi.md

@@ -135,7 +135,7 @@ As an overview:
 1. Modify the JSON payload as desired.
 1. Select **Done** and then **Close & Apply** within the **Power Query Editor Window**.
 
-You should read the desired changes applied.  
+The interface will now reflect the desired changes you applied.  
 
 ## Next Steps
 

articles/time-series-insights/how-to-shape-query-json.md

@@ -47,7 +47,7 @@ The following guidance helps to ensure the best possible query performance:
 
 ## Example overview
 
-The following two examples demonstrate how to send events to highlight the previous recommendations. Following each example, you can read how the recommendations were applied.
+The following two examples demonstrate how to send events to highlight the previous recommendations. Following each example, you can review how the recommendations were applied.
 
 The examples are based on a scenario where multiple devices send measurements or signals. Measurements or signals can be Flow Rate, Engine Oil Pressure, Temperature, and Humidity. In the first example, there are a few measurements across all devices. The second example has many devices, and each device sends many unique measurements.
 

articles/time-series-insights/time-series-insights-add-reference-data-set.md

@@ -69,7 +69,7 @@ Reference data is not joined retroactively. Thus, only current and future ingres
 
    [![Review reference data](media/add-reference-data-set/review-displayed-data-grid.png)](media/add-reference-data-set/review-displayed-data-grid.png#lightbox)
 
-1. Review each column to read the data type assumed, and change the data type if needed.  Select the data type symbol in the column heading: **#** for double (numerical data), **T|F** for boolean, or **Abc** for string.
+1. Review each column to understand the data type assumed, and change the data type if needed.  Select the data type symbol in the column heading: **#** for double (numerical data), **T|F** for boolean, or **Abc** for string.
 
    [![Choose data types on the column headings.](media/add-reference-data-set/select-column-types.png)](media/add-reference-data-set/select-column-types.png#lightbox)
 

articles/time-series-insights/time-series-insights-authentication-and-authorization.md

@@ -102,7 +102,7 @@ This section describes common HTTP request headers and parameters used to make q
 To perform authenticated queries against the [Time Series Insights REST APIs](https://docs.microsoft.com/rest/api/time-series-insights/), a valid OAuth 2.0 bearer token must be passed in the [Authorization header](/rest/api/apimanagement/2019-01-01/authorizationserver/createorupdate) using a REST client of your choice (Postman, JavaScript, C#). 
 
 > [!TIP]
-> Read the hosted Azure Time Series Insights [client SDK sample visualization](https://tsiclientsample.azurewebsites.net/) to read how to authenticate with the Time Series Insights APIs programmatically using the [JavaScript Client SDK](https://github.com/microsoft/tsiclient/blob/master/docs/API.md) along with charts and graphs.
+> Read the hosted Azure Time Series Insights [client SDK sample visualization](https://tsiclientsample.azurewebsites.net/) to learn how to authenticate with the Time Series Insights APIs programmatically using the [JavaScript Client SDK](https://github.com/microsoft/tsiclient/blob/master/docs/API.md) along with charts and graphs.
 
 ### HTTP headers
 

articles/time-series-insights/time-series-insights-concepts-retention.md

@@ -39,7 +39,7 @@ Both data retention policies are described in greater detail below.
 ## Purge old data
 
 - **Purge old data** is the default setting for Azure Time Series Insights environments.  
-- **Purge old data** is preferred when users want to always read their *most recent data* in their Time Series Insights environment.
+- **Purge old data** is preferred when users want to always have their *most recent data* in their Time Series Insights environment.
 - The **Purge old data** setting *purges* data once the environment’s limits (retention time, size, or count, whichever comes first) are reached. Retention is set to 30 days by default.
 - The oldest ingested data is purged first (the "First In First Out" approach).
 

articles/time-series-insights/time-series-insights-data-access.md

@@ -108,7 +108,7 @@ Follow these steps to grant guest access to a Time Series Insights environment t
 
 1. The guest can now access the shared environment using the environment URL provided by the administrator. They can enter that URL into their web browser for immediate access.
 
-1. The guest user will read the administrator's tenant by selecting their profile icon in the upper-right corner of the Time Series explorer.
+1. The administrator's tenant will be displayed to the guest user after selecting their profile icon in the upper-right corner of the Time Series explorer.
 
     [![Avatar selection on insights.azure.com](media/data-access/data-access-select-tenant-and-instance.png)](media/data-access/data-access-select-tenant-and-instance.png#lightbox)
 

articles/time-series-insights/time-series-insights-diagnose-and-solve-problems.md

@@ -64,7 +64,7 @@ If you have old events in your event source, you can approach throttling in one
 - Change your event source's retention limits to help remove old events that you don't want to show up in Time Series Insights.
 - Provision a larger environment size (number of units) to increase the throughput of old events. Using the preceding example, if you increase the same S1 environment to five units for one day, the environment should catch up within a day. If your steady-state event production is 1 million or fewer events per day, you can reduce the capacity of the event to one unit after it catches up.
 
-The throttling limit is enforced based on the environment's SKU type and capacity. All event sources in the environment share this capacity. If the event source for your IoT hub or event hub pushes data beyond the enforced limits, you will experience throttling and a lag.
+The throttling limit is enforced based on the environment's SKU type and capacity. All event sources in the environment share this capacity. If the event source for your IoT hub or event hub pushes data beyond the enforced limits, you'll experience throttling and a lag.
 
 The following figure shows a Time Series Insights environment that has an SKU of S1 and a capacity of 3. It can ingress 3 million events per day.
 

articles/time-series-insights/time-series-insights-environment-mitigate-latency.md

@@ -69,11 +69,11 @@ Alerts can help you to help diagnose and mitigate latency issues caused by your
 
 ## Throttling and ingress management
 
-* If you are being throttled, you will read a value for the *Ingress Received Message Time Lag*, informing you about how many seconds behind your TIme Series Insights environment are from the actual time the message hits the event source (excluding indexing time of appx. 30-60 seconds).  
+* If you're being throttled, a value for the *Ingress Received Message Time Lag* will be registered informing you about how many seconds behind your TIme Series Insights environment are from the actual time the message hits the event source (excluding indexing time of appx. 30-60 seconds).  
 
   *Ingress Received Message Count Lag* should also have a value, allowing you to determine how many messages behind you are.  The easiest way to get caught up is to increase your environment's capacity to a size that will enable you to overcome the difference.  
 
-  For example, if you read that your S1 environment is demonstrating lag of 5,000,000 messages, you might increase the size of your environment to six units for around a day to get caught up.  You could increase even further to catch up faster. The catch-up period is a common occurrence when initially provisioning an environment, particularly when you connect it to an event source that already has events in it or when you bulk upload lots of historical data.
+  For example, if your S1 environment is demonstrating lag of 5,000,000 messages, you might increase the size of your environment to six units for around a day to get caught up.  You could increase even further to catch up faster. The catch-up period is a common occurrence when initially provisioning an environment, particularly when you connect it to an event source that already has events in it or when you bulk upload lots of historical data.
 
 * Another technique is to set an **Ingress Stored Events** alert >= a threshold slightly below your total environment capacity for a period of 2 hours.  This alert can help you understand if you are constantly at capacity, which indicates a high likelihood of latency. 
 

articles/time-series-insights/time-series-insights-explorer.md

@@ -54,7 +54,7 @@ Within minutes of connecting your event source to your Time Series Insights envi
 
    [![Time Series Insights environment selection](media/time-series-insights-explorer/tsi-ga-explorer-environments.png)](media/time-series-insights-explorer/tsi-ga-explorer-environments.png#lightbox)
 
-1. Next, you read a chart that shows a count of all events during the selected timespan. Here you have a number of controls:
+1. Next, a chart that shows a count of all events during the selected timespan is displayed. Here you have a number of controls:
 
     - **Terms Editor panel**: The term space is where you query your environment. It’s found on the left side of the screen:
       - **MEASURE**: This drop-down list shows all numeric columns (**Doubles**).
@@ -77,11 +77,11 @@ Within minutes of connecting your event source to your Time Series Insights envi
 
          [![Example GA queries](media/time-series-insights-explorer/tsi-ga-example-queries.png)](media/time-series-insights-explorer/tsi-ga-example-queries.png#lightbox)
 
-1. You can use the **Interval Size** slider tool to zoom in and out of intervals over the same timespan. The slider provides more precise control of movement between large slices of time that show smooth trends down to slices as small as the millisecond, which allow you to read granular, high-resolution cuts of your data. The slider’s default starting point is set as the most optimal view of the data from your selection to balance resolution, query speed, and granularity.
+1. You can use the **Interval Size** slider tool to zoom in and out of intervals over the same timespan. The slider provides more precise control of movement between large slices of time that show smooth trends down to slices as small as the millisecond, which allow you to display and analyze granular, high-resolution cuts of your data. The slider’s default starting point is set as the most optimal view of the data from your selection to balance resolution, query speed, and granularity.
 
 1. The **Time brush** tool makes it easy to navigate from one timespan to another.
 
-1. Select the **Save** icon to save your current query and share it with other users of the environment. When you select the **Open** icon, you can read all of your saved queries and any shared queries of other users in environments you have access to.
+1. Select the **Save** icon to save your current query and share it with other users of the environment. When you select the **Open** icon, you can review all of your saved queries and any shared queries of other users in environments you have access to.
 
    [![Queries](media/time-series-insights-explorer/tsi-ga-explorer-saved-queries.png)](media/time-series-insights-explorer/tsi-ga-explorer-saved-queries.png#lightbox)
 

articles/time-series-insights/time-series-insights-manage-resources-using-azure-resource-manager-template.md

@@ -81,7 +81,7 @@ The following procedure describes how to use PowerShell to deploy an Azure Resou
 
    * As an example, the following parameters file would be used to create an environment and an event source that reads events from an existing event hub. It also creates two access policies that grant Contributor access to the environment.
 
-     ```json
+     ```JSON
      {
          "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
          "contentVersion": "1.0.0.0",