Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr

Author: v-sonan

articles/azure-monitor/toc.yml

@@ -595,36 +595,48 @@
     - name: Resource logs
       items: 
       - name: Overview
+        displayname: Resource logs
         href: platform/resource-logs-overview.md 
       - name: Collect in Azure Monitor Logs
+        displayname: Resource logs
         href: platform/resource-logs-collect-workspace.md
       - name: Archive to storage
+        displayname: Resource logs
         href: platform/resource-logs-collect-storage.md
       - name: Stream to Event Hubs
+        displayname: Resource logs
         href: platform/resource-logs-stream-event-hubs.md
     - name: Activity log
       items:
       - name: Overview
+        displayname: Activity log
         href: platform/activity-logs-overview.md
+      - name: Collect with diagnostic setting
+        displayname: Activity log
+        href: platform/diagnostic-settings-subscription.md
       - name: View and retrieve
+        displayname: Activity log
         href: platform/activity-log-view.md
       - name: Collect and analyze
+        displayname: Activity log
         href: platform/activity-log-collect.md
       - name: Collect across tenants
+        displayname: Activity log
         href: platform/activity-log-collect-tenants.md
       - name: Export 
+        displayname: Activity log
         href: platform/activity-log-export.md
       - name: Schema
+        displayname: Activity log
         href: platform/activity-log-schema.md
     - name: Diagnostic settings
       items: 
       - name: Create diagnostic setting
         href: platform/diagnostic-settings.md
-      - name: Collect with diagnostic setting
-        href: platform/diagnostic-settings-subscription.md
       - name: Create diagnostic setting with Resource Manager
         href: platform/diagnostic-settings-template.md
       - name: Change to blob storage format
+        displayname: Diagnostic settings
         href: platform/resource-logs-blob-format.md
     - name: Stream data to Event Hubs
       href: platform/stream-monitoring-data-event-hubs.md 

articles/cognitive-services/QnAMaker/How-To/chit-chat-knowledge-base.md

@@ -8,7 +8,7 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: qna-maker
 ms.topic: conceptual
-ms.date: 10/09/2019
+ms.date: 11/04/2019
 ms.author: diberry
 ms.custom: seodec18
 ---
@@ -40,15 +40,15 @@ Chit-chat data sets are supported in the following languages:
 
 |Language|
 |--|
-|Chinese, `zh-cn`|
-|English, `en-us`|
-|French, `fr-fr`|
-|Germany, `de-de`|
-|Italian, `it-it`|
-|Japanese, `ja-jp`|
-|Korean, `ko-kr`|
-|Portuguese, `pr-br`|
-|Spanish, `es-es`|
+|Chinese|
+|English|
+|French|
+|Germany|
+|Italian|
+|Japanese|
+|Korean|
+|Portuguese|
+|Spanish|
 
 
 ## Add chit-chat during KB creation

articles/cognitive-services/personalizer/index.yml

@@ -95,7 +95,7 @@ landingContent:
             url: concepts-exploration.md
           - text: Features, action, and context
             url: concepts-features.md
-          - text: Active learning
+          - text: Active and inactive events
             url: concept-active-learning.md
           - text: Rewards
             url: concept-rewards.md
@@ -105,7 +105,7 @@ landingContent:
         links:
           - text: Improve loop with offline evaluations
             url: concepts-offline-evaluation.md
-          - text: Active learning
+          - text: Active and inactive events
             url: concept-active-learning.md
           - text: Scalability and performance
             url: concepts-scalability-performance.md 

articles/cognitive-services/personalizer/toc.yml

@@ -41,7 +41,7 @@
     - name: "Features Action and Context"
       href: concepts-features.md
       displayName: action, context, feature, namespace, JSON, best practice, set, ID, guid, event id, 
-    - name: Active learning
+    - name: Active and inactive events
       href: concept-active-learning.md
       displayName: active, inactive
     - name: Rewards

articles/cosmos-db/media/provision-throughput-autopilot/enable-autopilot-azure-portal.png

@@ -63,6 +63,16 @@ Solutions to the previous problems not only require an enormous amount of time i
 | **Pricing** | Manually provisioned RU/s per hour. | For single write region accounts, you pay for the throughput used on an hourly basis, by using the autopilot RU/s per hour rate. <br/><br/>For accounts with multiple write regions, there is no extra charge for autopilot. You pay for the throughput used on hourly basis using the same multi-master RU/s per hour rate. |
 | **Best suited for workload types** |  Predictable and stable workloads|   Unpredictable and variable workloads  |
 
+## Enable autopilot from Azure portal
+
+You can try out autopilot in your Azure Cosmos accounts by enabling in from Azure portal. Use the following steps to enable the autopilot option:
+
+1. Sign in to the [Azure portal.](https://portal.azure.com)
+
+2. Navigate to your Azure Cosmos account and open the **New Features** tab. Select **Auto Pilot** and **Register** as shown in the following screenshot:
+
+![Create a container in autopilot mode](./media/provision-throughput-autopilot/enable-autopilot-azure-portal.png)
+
 ## Create a database or a container with autopilot mode
 
 You can configure autopilot for databases or containers while creating them. Use the following steps to a new database or container, enable autopilot, and specify the maximum throughput.
@@ -83,4 +93,4 @@ With similar steps, you can also create a database with provisioned throughput i
 
 * Learn more about [logical partitions](partition-data.md).
 * Learn how to [provision throughput on an Azure Cosmos container](how-to-provision-container-throughput.md).
-* Learn how to [provision throughput on an Azure Cosmos database](how-to-provision-database-throughput.md).
+* Learn how to [provision throughput on an Azure Cosmos database](how-to-provision-database-throughput.md).

articles/cosmos-db/provision-throughput-autopilot.md

@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 06/12/2019
+ms.date: 11/04/2019
 ---
 # Monitoring in Azure Database for MariaDB
 Monitoring data about your servers helps you troubleshoot and optimize for your workload. Azure Database for MariaDB provides various metrics that give insight into the behavior of your server.
@@ -40,15 +40,15 @@ You can enable slow query logging on your server. These logs are also available
 
 ## Query Store
 
-[Query Store](concepts-query-store.md) is a public preview feature that keeps track of query performance over time including query runtime statistics and wait events. The feature persists query runtime performance information in the **mysql** schema. You can control the collection and storage of data via various configuration knobs.
+[Query Store](concepts-query-store.md) keeps track of query performance over time including query runtime statistics and wait events. The feature persists query runtime performance information in the **mysql** schema. You can control the collection and storage of data via various configuration knobs.
 
 ## Query Performance Insight
 
-[Query Performance Insight](concepts-query-performance-insight.md) works in conjunction with Query Store to provide visualizations accessible from the Azure portal. These charts enable you to identify key queries that impact performance. Query Performance Insight is in public preview and is accessible in the **Intelligent Performance** section of your Azure Database for MariaDB server's portal page.
+[Query Performance Insight](concepts-query-performance-insight.md) works in conjunction with Query Store to provide visualizations accessible from the Azure portal. These charts enable you to identify key queries that impact performance. Query Performance Insight is accessible in the **Intelligent Performance** section of your Azure Database for MariaDB server's portal page.
 
 ## Performance Recommendations
 
-The [Performance Recommendations](concepts-performance-recommendations.md) feature identifies opportunities to improve workload performance. The public preview release of Performance Recommendations provides you with recommendations for creating new indexes that have the potential to improve the performance of your workloads. To produce index recommendations, the feature takes into consideration various database characteristics, including its schema and the workload as reported by Query Store. After implementing any performance recommendation, customers should test performance to evaluate the impact of those changes.
+The [Performance Recommendations](concepts-performance-recommendations.md) feature identifies opportunities to improve workload performance. Performance Recommendations provides you with recommendations for creating new indexes that have the potential to improve the performance of your workloads. To produce index recommendations, the feature takes into consideration various database characteristics, including its schema and the workload as reported by Query Store. After implementing any performance recommendation, customers should test performance to evaluate the impact of those changes.
 
 ## Next steps
 

articles/mariadb/concepts-monitoring.md

@@ -5,15 +5,12 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 06/27/2019
+ms.date: 11/04/2019
 ---
 # Performance Recommendations in Azure Database for MariaDB
 
 **Applies to:** Azure Database for MariaDB 10.2
 
-> [!IMPORTANT]
-> Performance Recommendations is in preview.
-
 The Performance Recommendations feature analyzes your databases to create customized suggestions for improved performance. To produce the recommendations, the analysis looks at various database characteristics including schema. Enable [Query Store](concepts-query-store.md) on your server to fully utilize the Performance Recommendations feature. If performance schema is OFF, turning on Query Store enables performance_schema and a subset of performance schema instruments required for the feature. After implementing any performance recommendation, you should test performance to evaluate the impact of those changes.
 
 ## Permissions

articles/mariadb/concepts-performance-recommendations.md

@@ -5,15 +5,12 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 06/27/2019
+ms.date: 11/04/2019
 ---
 # Query Performance Insight in Azure Database for MariaDB
 
 **Applies to:** Azure Database for MariaDB 10.2
 
-> [!IMPORTANT]
-> Query Performance Insight is in preview.
-
 Query Performance Insight helps you to quickly identify what your longest running queries are, how they change over time, and what waits are affecting them.
 
 ## Common scenarios

articles/mariadb/concepts-query-performance-insight.md

@@ -5,15 +5,12 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 10/17/2019
+ms.date: 11/04/2019
 ---
 # Monitor Azure Database for MariaDB performance with Query Store
 
 **Applies to:** Azure Database for MariaDB 10.2
 
-> [!IMPORTANT]
-> Query Store is in preview.
-
 The Query Store feature in Azure Database for Mariadb provides a way to track query performance over time. Query Store simplifies performance troubleshooting by helping you quickly find the longest running and most resource-intensive queries. Query Store automatically captures a history of queries and runtime statistics, and it retains them for your review. It separates data by time windows so that you can see database usage patterns. Data for all users, databases, and queries is stored in the **mysql** schema database in the Azure Database for MariaDB instance.
 
 ## Common scenarios for using Query Store