Fixing monitoring doc issues

Author: SnehaGunda

articles/cosmos-db/cosmosdb-monitor-resource-logs.md

@@ -94,12 +94,12 @@ For detailed information about how to create a diagnostic setting by using the A
    | render timechart
    ```
 
-1. How to get partition Key statistics to evaluate skew across top 3 partitions for database account:
+1. How to get partition key statistics to evaluate skew across top 3 partitions for a database account:
 
    ```Kusto
    AzureDiagnostics 
    | where ResourceProvider=="MICROSOFT.DOCUMENTDB" and Category=="PartitionKeyStatistics" 
-   | project SubscriptionId, regionName_s, databaseName_s, collectionname_s, partitionkey_s, sizeKb_s, ResourceId 
+   | project SubscriptionId, regionName_s, databaseName_s, collectionName_s, partitionKey_s, sizeKb_d, ResourceId 
    ```
 
 1. How to get the request charges for expensive queries?
@@ -209,14 +209,6 @@ For detailed information about how to create a diagnostic setting by using the A
    | where todouble(sizeKb_d) > 800000
    ```
 
-1. How to get partition Key statistics to evaluate skew across top three partitions for database account?
-
-   ```Kusto
-   AzureDiagnostics 
-   | where ResourceProvider=="MICROSOFT.DOCUMENTDB" and Category=="PartitionKeyStatistics" 
-   | project SubscriptionId, regionName_s, databaseName_s, collectionName_s, partitionKey_s, sizeKb_d, ResourceId
-   ```
-
 1. How to get P99 or P50 replication latencies for operations, request charge or the length of the response?
 
    ```Kusto

articles/cosmos-db/monitor-cosmos-db.md

@@ -71,6 +71,8 @@ You can analyze metrics for Azure Cosmos DB with metrics from other Azure servic
 * Region
 * StatusCode
 
+Metrics which are available to monitor are available [here](monitor-cosmos-db.md#analyzing-metric-data)
+
 ### View operation level metrics for Azure Cosmos DB
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).

articles/cosmos-db/monitor-server-side-latency.md

@@ -12,12 +12,13 @@ ms.date: 04/07/2020
 
 Azure Monitor for Azure Cosmos DB provides a metrics view to monitor your account and create dashboards. The Azure Cosmos DB metrics are collected by default, this feature does not require you to enable or configure anything explicitly. The server-side latency metric is used to view the server-side latency of an operation. Azure Cosmos DB provides SLA of less than 10 ms for point read/write operations with direct connectivity. For point read and write operations, the SLAs are calculated as detailed in the [SLA document](https://azure.microsoft.com/support/legal/sla/cosmos-db/v1_3/).
 
-If you see unusually high latency for point operation such as A get or set operation with partition key and ID in direct mode
-Or 
+You can monitor server-side latency if you see unusually high latency for point operation such as:
+
+* A GET or a SET operation with partition key and ID in direct connectivity mode
 * A read or write operation or
 * A query
 
-You can look up the diagnostic log to see the size of data returned. If you see a sustained high latency for query operation, you should look up the diagnostic log for higher [throughput or RU/s](cosmosdb-monitor-resource-logs.md#diagnostic-queries) used. Server side latency shows as the name suggests amount of time spent on the backend infrastructure before data was returned to your calling code. It is important to look at this metric to rule out any backend latency issues. 
+You can look up the diagnostic log to see the size of the data returned. If you see a sustained high latency for query operations, you should look up the diagnostic log for higher [throughput or RU/s](cosmosdb-monitor-resource-logs.md#diagnostic-queries) used. Server side latency shows the amount of time spent on the backend infrastructure before the data was returned to the client. It is important to look at this metric to rule out any backend latency issues.
 
 ## View the server-side latency metric
 

articles/cosmos-db/online-backup-and-restore.md

@@ -85,6 +85,13 @@ When you accidentally delete or modify one or more items within a container (the
 
 If you have accidentally deleted or corrupted your data, you should contact [Azure support](https://azure.microsoft.com/support/options/) within 8 hours so that the Azure Cosmos DB team can help you restore the data from the backups. This way the Azure Cosmos DB support team will have enough time to restore your account.
 
+> [!NOTE]
+> After you restore the data, not all the source capabilities or settings are carried over to the restored account. The following settings are not carried over to the new account:
+
+> * VNET access control lists
+> * Stored procedures, triggers and user-defined functions
+> * Multi-region settings  
+
 If you provision throughput at the database level, the backup and restore process in this case happen at the entire database level, and not at the individual containers level. In such cases, you can't select a subset of containers to restore.
 
 ## Migrate data to the original account