Merge pull request #94298 from MicrosoftDocs/release-ignite-cogsvcs-containers-luis

Ignite

Author: SyntaxC4

articles/cognitive-services/LUIS/deploy-luis-on-container-instances.md

@@ -1,26 +1,26 @@
 ---
-title: Run Azure Container Instances
+title: Run Azure Container instances
 titleSuffix: Azure Cognitive Services
-description: Deploy the LUIS container to an Azure Container Instance, and test it in a web browser.
+description: Deploy the LUIS container to an Azure Container instance, and test it in a web browser.
 services: cognitive-services
 author: IEvangelist
 manager: nitinme
 ms.service: cognitive-services
 ms.subservice: language-understanding
 ms.topic: conceptual
-ms.date: 7/5/2019
+ms.date: 11/04/2019
 ms.author: dapine
 ---
 
-# Deploy the Language Understanding (LUIS) container to Azure Container Instances
+# Deploy the Language Understanding (LUIS) container to Azure Container instances
 
-Learn how to deploy the Cognitive Services [LUIS](luis-container-howto.md) container to Azure [Container Instances](https://docs.microsoft.com/azure/container-instances/). This procedure demonstrates the creation of an Anomaly Detector resource. Then we discuss pulling the associated container image. Finally, we highlight the ability to exercise the orchestration of the two from a browser. Using containers can shift the developers' attention away from managing infrastructure to instead focusing on application development.
+Learn how to deploy the Cognitive Services [LUIS](luis-container-howto.md) container to Azure [Container instances](https://docs.microsoft.com/azure/container-instances/). This procedure demonstrates the creation of an Anomaly Detector resource. Then we discuss pulling the associated container image. Finally, we highlight the ability to exercise the orchestration of the two from a browser. Using containers can shift the developers' attention away from managing infrastructure to instead focusing on application development.
 
 [!INCLUDE [Prerequisites](../containers/includes/container-prerequisites.md)]
 
 [!INCLUDE [Create LUIS resource](includes/create-luis-resource.md)]
 
-[!INCLUDE [Create LUIS Container Instance resource](../containers/includes/create-container-instances-resource.md)]
+[!INCLUDE [Create LUIS Container instance resource](../containers/includes/create-container-instances-resource.md)]
 
 [!INCLUDE [API documentation](../../../includes/cognitive-services-containers-api-documentation.md)]
 

articles/cognitive-services/LUIS/includes/chinese-language-support-notes.md

@@ -0,0 +1,17 @@
+---
+title: Chinese support notes
+services: cognitive-services
+author: IEvangelist
+manager: nitinme
+ms.service: cognitive-services
+ms.topic: include
+ms.date: 10/07/2019
+ms.author: dapine
+---
+
+### *Chinese support notes
+
+ - In the `zh-CN` culture, LUIS expects the simplified Chinese character set instead of the traditional character set.
+ - The names of intents, entities, features, and regular expressions may be in Chinese or Roman characters.
+ - See the [prebuilt domains reference](../luis-reference-prebuilt-domains.md) for information on which prebuilt domains are supported in the `zh-CN` culture.
+<!--- When writing regular expressions in Chinese, do not insert whitespace between Chinese characters.-->

articles/cognitive-services/LUIS/includes/create-luis-resource.md

@@ -1,5 +1,5 @@
 ---
-title: Container support
+title: Create LUIS resource
 titleSuffix: Azure Cognitive Services
 services: cognitive-services
 author: IEvangelist
@@ -24,10 +24,7 @@ ms.author: dapine
     |Pricing Tier|`F0` - the minimal pricing tier|
     |Resource Group|Select an available resource group|
 
-1. Click **Create** and wait for the resource to be created. After it is created, navigate to the resource page
-1. Collect configured `endpoint` and an API key:
+1. Click **Create** and wait for the resource to be created. After it is created, navigate to the resource page.
+1. Collect configured `endpoint` and an API key, see [gathering required parameters](#gathering-required-parameters).
 
-    |Resource Tab in Portal|Setting|Value|
-    |--|--|--|
-    |**Overview**|Endpoint|Copy the endpoint. It looks similar to `https://luis.cognitiveservices.azure.com/luis/v2.0`|
-    |**Keys**|API Key|Copy 1 of the two keys. It is a 32 alphanumeric-character string with no spaces or dashes, `xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx`.|
+[!INCLUDE [Gathering required parameters](../../containers/includes/container-gathering-required-parameters.md)]

articles/cognitive-services/LUIS/includes/text-analytics-support-notes.md

@@ -0,0 +1,13 @@
+---
+title: Chinese support notes
+services: cognitive-services
+author: IEvangelist
+manager: nitinme
+ms.service: cognitive-services
+ms.topic: include
+ms.date: 10/07/2019
+ms.author: dapine
+---
+
+### **Text analytics support notes
+Text analytics includes keyPhrase prebuilt entity and sentiment analysis. Only Portuguese is supported for subcultures: `pt-PT` and `pt-BR`. All other cultures are supported at the primary culture level. Learn more about Text Analytics [supported languages](../../text-analytics/language-support.md).

articles/cognitive-services/LUIS/luis-container-configuration.md

@@ -9,7 +9,7 @@ ms.custom: seodec18
 ms.service: cognitive-services
 ms.subservice: language-understanding
 ms.topic: conceptual
-ms.date: 09/18/2019
+ms.date: 11/04/2019
 ms.author: dapine
 ---
 
@@ -59,12 +59,9 @@ This setting can be found in the following places:
 * Azure portal: **Cognitive Services** Overview, labeled `Endpoint`
 * LUIS portal: **Keys and Endpoint settings** page, as part of the endpoint URI.
 
-Remember to include the `luis/v2.0` routing in the URL as shown in the following table:
-
-
-|Required| Name | Data type | Description |
-|--|------|-----------|-------------|
-|Yes| `Billing` | String | Billing endpoint URI<br><br>Example:<br>`Billing=https://westus.api.cognitive.microsoft.com/luis/v2.0` |
+| Required | Name | Data type | Description |
+|----------|------|-----------|-------------|
+| Yes      | `Billing` | string | Billing endpoint URI. |
 
 ## Eula setting
 
@@ -74,7 +71,7 @@ Remember to include the `luis/v2.0` routing in the URL as shown in the following
 
 [!INCLUDE [Container shared configuration fluentd settings](../../../includes/cognitive-services-containers-configuration-shared-settings-fluentd.md)]
 
-## Http proxy credentials settings
+## HTTP proxy credentials settings
 
 [!INCLUDE [Container shared configuration fluentd settings](../../../includes/cognitive-services-containers-configuration-shared-settings-http-proxy.md)]
 
@@ -105,8 +102,6 @@ The following examples use the configuration settings to illustrate how to write
 * Do not change the order of the arguments unless you are very familiar with docker containers.
 * If you are using a different operating system, use the correct console/terminal, folder syntax for mounts, and line continuation character for your system. These examples assume a Windows console with a line continuation character `^`. Because the container is a Linux operating system, the target mount uses a Linux-style folder syntax.
 
-Remember to include the `luis/v2.0` routing in the URL as shown in the following table.
-
 Replace {_argument_name_} with your own values:
 
 | Placeholder | Value | Format or example |