Update restore.md

Author: DaleKoetke

articles/azure-monitor/logs/restore.md

@@ -6,7 +6,7 @@ ms.date: 10/01/2022
 ---
 
 # Restore logs in Azure Monitor
-The restore operation makes a specific time range of data in a table available in the hot cache for high-performance queries. This article describes how to restore data, query that data, and then dismiss the data when you're done. 
+The restore operation makes a specific time range of data in a table available in the hot cache for high-performance queries. This article describes how to restore data, query that data, and then dismiss the data when you're done.  
 
 ## Permissions
 
@@ -21,7 +21,7 @@ Use the restore operation to query data in [Archived Logs](data-retention-archiv
 ## What does restore do?
 When you restore data, you specify the source table that contains the data you want to query and the name of the new destination table to be created. 
 
-The restore operation creates the restore table and allocates additional compute resources for querying the restored data using high-performance queries that support full KQL.
+The restore operation creates the restore table and allocates extra compute resources for querying the restored data using high-performance queries that support full KQL.
 
 The destination table provides a view of the underlying source data, but doesn't affect it in any way. The table has no retention setting, and you must explicitly [dismiss the restored data](#dismiss-restored-data) when you no longer need it. 
 
@@ -124,29 +124,29 @@ You can:
 
 - Restore up to 60 TB.
 - Run up to two restore processes in a workspace concurrently.
-- Run only one active restore on a specific table at a given time. Executing a second restore on a table that already has an active restore will fail. 
+- Run only one active restore on a specific table at a given time. Executing a second restore on a table that already has an active restore fails. 
 - Perform up to four restores per table per week. 
 
 ## Pricing model
 
 The charge for restored logs is based on the volume of data you restore, and the duration for which the restore is active. Thus, the units of price are *per GB per day*. Data restores are billed on each UTC-day that the restore is active. 
 
 - Charges are subject to a minimum restored data volume of 2 TB per restore. If you restore less data, you will be charged for the 2 TB minimum each day until the [restore is dismissed](#dismiss-restored-data).
-- On the first and last days that the restore is active, you are only billed for the part of the day the restore was active. 
+- On the first and last days that the restore is active, you're only billed for the part of the day the restore was active. 
 
-- The minimum charge will be for a 12-hour restore duration, even if the restore is active for less than 12-hours.
+- The minimum charge is for a 12-hour restore duration, even if the restore is active for less than 12-hours.
 
 - For more information on your data restore price, see [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/) on the Logs tab.
 
 Here are some examples to illustrate data restore cost calculations:
 
-1. If your table holds 500 GB a day and you restore 10 days data from that table, your total restore size is 5 TB and you will be charged for this 5 TB of restored data each day until you [dismiss the restored data](#dismiss-restored-data). Your daily cost will be 5000 GB multiplied by your data restore price (see [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).) 
+1. If your table holds 500 GB a day and you restore 10 days data from that table, your total restore size is 5 TB. You are charged for this 5 TB of restored data each day until you [dismiss the restored data](#dismiss-restored-data). Your daily cost is 5,000 GB multiplied by your data restore price (see [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).) 
 
-1. If instead, only 700 GB of data is restored, each day that the restore is active will be billed for the 2 TB minimum restore level.  Your daily cost will be 2000 GB multiplied by your data restore price.
+1. If instead, only 700 GB of data is restored, each day that the restore is active is billed for the 2 TB minimum restore level. Your daily cost is 2,000 GB multiplied by your data restore price.
 
-1. If a 5 TB data restore is only kept active for 1 hour, it will be billed for 12-hour minimum. The cost for this data restore will be 5000 GB multiplied by your data restore price multiplied by 0.5 days (the 12-hour minimum). 
+1. If a 5 TB data restore is only kept active for 1 hour, it is billed for 12-hour minimum. The cost for this data restore is 5,000 GB multiplied by your data restore price multiplied by 0.5 days (the 12-hour minimum). 
 
-1. If a 700 GB data restore is only kept active for 1 hour, it will be billed for 12-hour minimum. The cost for this data restore will be 2000 GB (the minimum billed restore size) multiplied by your data restore price multiplied by 0.5 days (the 12-hour minimum). 
+1. If a 700 GB data restore is only kept active for 1 hour, it is billed for 12-hour minimum. The cost for this data restore is 2,000 GB (the minimum billed restore size) multiplied by your data restore price multiplied by 0.5 days (the 12-hour minimum). 
 
 > [!NOTE]
 > There is no charge for querying restored logs since they are Analytics logs.