Merge pull request #111349 from Virginia001/work01

Work01

Author: PRMerger9

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

@@ -9,7 +9,7 @@ manager: cshankar
 ms.reviewer: jasonh, kfile
 ms.workload: big-data
 ms.topic: conceptual
-ms.date: 01/10/2020
+ms.date: 04/14/2020
 ms.custom: seodec18
 ---
 
@@ -40,7 +40,7 @@ Both data retention policies are described in greater detail below.
 
 - **Purge old data** is the default setting for Azure Time Series Insights environments.  
 - **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 **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).
 
 ### Example one
@@ -55,16 +55,16 @@ On the 61st day, the environment shows the freshest data, but purges the oldest
 
 Consider an environment also configured retention behavior **Continue ingress and purge old data**. In this example, **Data retention time** is set to a lower value of 180 days. **Capacity** is set to S1 unit, which contains 30 GB of total capacity. In order to store data for the full 180 days, the daily ingress cannot exceed 0.166 GB (166 MB) per day.  
 
-Whenever this environment’s daily ingress rate exceeds of 0.166 GB per day, data cannot be stored for 180 days, since some data gets purged. Consider this same environment during a busy time frame. Assume the environment’s ingress rate may increase to an average 0.189 GB per day. In that busy time frame, about 158 days of data are retained (30GB/0.189 = 158.73 days of retention). This time is less than the desired data retention time frame.
+Whenever this environment's daily ingress rate exceeds of 0.166 GB per day, data cannot be stored for 180 days, since some data gets purged. Consider this same environment during a busy time frame. Assume the environment's ingress rate may increase to an average 0.189 GB per day. In that busy time frame, about 158 days of data are retained (30GB/0.189 = 158.73 days of retention). This time is less than the desired data retention time frame.
 
 ## Pause ingress
 
 - The **Pause ingress** setting is designed to ensure data is not purged if the size and count limits are reached prior to their retention period.  
 - **Pause ingress** provides additional time for the users to increase the capacity of their environment before data is purged due to breaching of retention period.
 - It helps protect you from data loss but can create an opportunity for the loss of your most recent data if ingress is paused beyond the retention period of your event source.
-- However, once an environment’s maximum capacity is reached, the environment pauses data ingress until the following additional actions occur:
+- However, once an environment's maximum capacity is reached, the environment pauses data ingress until the following additional actions occur:
 
-   - You increase the environment’s maximum capacity to add more scale units as described in [How to scale your Time Series Insights environment](time-series-insights-how-to-scale-your-environment.md).
+   - You increase the environment's maximum capacity to add more scale units as described in [How to scale your Time Series Insights environment](time-series-insights-how-to-scale-your-environment.md).
    - The data retention period is reached and data is purged, bringing the environment below its maximum capacity.
 
 ### Example three

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

@@ -1,5 +1,5 @@
 ---
-title: 'Explore data using the explorer - Azure Time Series Insights  | Microsoft Docs'
+title: 'Explore data using the explorer - Azure Time Series Insights | Microsoft Docs'
 description: Learn how to use the Azure Time Series Insights explorer to view your IoT data.
 ms.service: time-series-insights
 services: time-series-insights
@@ -10,7 +10,7 @@ ms.reviewer: v-mamcge, jasonh, kfile
 ms.devlang: csharp
 ms.workload: big-data
 ms.topic: conceptual
-ms.date: 01/15/2020
+ms.date: 04/14/2020
 ms.custom: seodec18
 ---
 
@@ -56,7 +56,7 @@ Within minutes of connecting your event source to your Time Series Insights envi
 
 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:
+    - **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**).
       - **SPLIT BY**: This drop-down list shows categorical columns (**Strings**).
       - You can enable step interpolation, show minimum and maximum, and adjust the y-axis from the control panel next to **MEASURE**. You also can adjust whether data shown is a count, average, or sum of the data.
@@ -77,7 +77,7 @@ 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 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. 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.