Merge pull request #104418 from diberry/diberry/0214-luis-meta-fix

[Cogsvcs] LUIS - subservice correction

Author: TedA-M

articles/cognitive-services/LUIS/includes/add-example-utterances-none-intent.md

@@ -1,22 +1,22 @@
 ---
 title: include file
-description: include file 
+description: include file
 services: cognitive-services
 author: diberry
 manager: nitinme
 ms.service: cognitive-services
-ms.subservice: luis
 ms.topic: include
 ms.custom: include file
-ms.date: 11/20/2019
+ms.date: 02/14/2020
+ms.subservice: language-understanding
 ms.author: diberry
 ---
 
 The client application needs to know if an utterance is not meaningful or appropriate for the application. The **None** intent is added to each application as part of the creation process to determine if an utterance shouldn't be answered by the client application.
 
-If LUIS returns the **None** intent for an utterance, your client application can ask if the user wants to end the conversation or give more directions for continuing the conversation. 
+If LUIS returns the **None** intent for an utterance, your client application can ask if the user wants to end the conversation or give more directions for continuing the conversation.
 
-If you leave the **None** intent empty, an utterance that should be predicted outside the subject domain will be predicted in one of the existing subject domain intents. The result is that the client application, such as a chat bot, will perform incorrect operations based on an incorrect prediction. 
+If you leave the **None** intent empty, an utterance that should be predicted outside the subject domain will be predicted in one of the existing subject domain intents. The result is that the client application, such as a chat bot, will perform incorrect operations based on an incorrect prediction.
 
 1. Select **Intents** from the left panel.
 

articles/cognitive-services/LUIS/includes/create-pizza-app.md

@@ -5,20 +5,20 @@ services: cognitive-services
 author: diberry
 manager: nitinme
 ms.service: cognitive-services
-ms.subservice: luis
+ms.date: 02/14/2020
+ms.subservice: language-understanding
 ms.topic: include
 ms.custom: include file
-ms.date: 11/05/2019
 ms.author: diberry
 ---
 
-1. Sign in to the preview LUIS portal with the URL of [https://preview.luis.ai](https://preview.luis.ai). 
+1. Sign in to the preview LUIS portal with the URL of [https://preview.luis.ai](https://preview.luis.ai).
 
-1. Select **Create new app**.  
+1. Select **Create new app**.
 
     [![Screenshot of Language Understanding (LUIS) My Apps page](../media/create-app-in-portal.png "Screenshot of Language Understanding (LUIS) My Apps page")](../media/create-app-in-portal.png#lightbox)
 
-1. In the pop-up dialog, enter the name `Pizza tutorial` and keep the default culture, **English**. The other fields are optional, do not set them. Select **Done**. 
+1. In the pop-up dialog, enter the name `Pizza tutorial` and keep the default culture, **English**. The other fields are optional, do not set them. Select **Done**.
 
     ![Enter name of new LUIS app](../media/create-pizza-tutorial-app-in-portal.png)
 

articles/cognitive-services/LUIS/includes/do-not-use-too-few-utterances.md

@@ -1,15 +1,15 @@
 ---
 title: include file
-description: include file 
+description: include file
 services: cognitive-services
 author: diberry
 manager: nitinme
 ms.custom: seodec18
 ms.service: cognitive-services
-ms.subservice: luis
+ms.date: 02/14/2020
+ms.subservice: language-understanding
 ms.topic: include
 ms.custom: include file
-ms.date: 11/05/2019
 ms.author: diberry
 ---
 

articles/cognitive-services/LUIS/includes/get-started-get-model-json-example-utterances.md

@@ -1,17 +1,17 @@
 ---
 title: include file
-description: include file 
+description: include file
 services: cognitive-services
 author: diberry
 manager: nitinme
 ms.service: cognitive-services
-ms.subservice: luis
+ms.date: 02/14/2020
+ms.subservice: language-understanding
 ms.topic: include
 ms.custom: include file
-ms.date: 10/19/2019
 ms.author: diberry
 ---
-The example utterances follow a specific format. 
+The example utterances follow a specific format.
 
 The `text` field contains the text of the example utterance. The `intentName` field must correspond to the name of an existing intent in the LUIS app. The `entityLabels` field is required. If you don't want to label any entities, provide an empty array.
 

articles/cognitive-services/LUIS/includes/howto-get-endpoint.md

@@ -1,19 +1,19 @@
 ---
 title: include file
-description: include file 
+description: include file
 services: cognitive-services
 author: diberry
 manager: nitinme
 ms.custom: seodec18
 ms.service: cognitive-services
-ms.subservice: luis
+ms.date: 02/14/2020
+ms.subservice: language-understanding
 ms.topic: include
 ms.custom: include file
-ms.date: 11/05/2019
 ms.author: diberry
 ---
 
-In the **Manage** section (top right menu), on the **Azure Resources** page (left menu), copy the **Example Query** URL then paste into a new browser tab. 
+In the **Manage** section (top right menu), on the **Azure Resources** page (left menu), copy the **Example Query** URL then paste into a new browser tab.
 
 The endpoint URL looks like the following format, with your own app ID and endpoint key replacing APP-ID and KEY-ID:
 

articles/cognitive-services/LUIS/includes/howto-publish.md

@@ -1,19 +1,19 @@
 ---
 title: include file
-description: include file 
+description: include file
 services: cognitive-services
 author: diberry
 manager: nitinme
 ms.custom: seodec18
 ms.service: cognitive-services
-ms.subservice: luis
+ms.date: 02/14/2020
+ms.subservice: language-understanding
 ms.topic: include
 ms.custom: include file
-ms.date: 11/05/2019
 ms.author: diberry
 ---
 
-In order to receive a LUIS prediction in a chat bot or other client application, you need to publish the app to the endpoint. 
+In order to receive a LUIS prediction in a chat bot or other client application, you need to publish the app to the endpoint.
 
 1. Select **Publish** in the top right navigation.
 

articles/cognitive-services/LUIS/includes/howto-train.md

@@ -1,19 +1,19 @@
 ---
 title: include file
-description: include file 
+description: include file
 services: cognitive-services
 author: diberry
 manager: nitinme
 ms.custom: seodec18
 ms.service: cognitive-services
-ms.subservice: luis
+ms.date: 02/14/2020
+ms.subservice: language-understanding
 ms.topic: include
 ms.custom: include file
-ms.date: 11/04/2019
 ms.author: diberry
 ---
 
-1. In the top right side of the LUIS website, select the **Train** button. 
+1. In the top right side of the LUIS website, select the **Train** button.
 
     ![Train button](../media/train-button-preview.png)
 

articles/cognitive-services/LUIS/includes/manage-contributor-collaborator-migration.md

@@ -1,22 +1,22 @@
 ---
 title: include file
-description: include file 
+description: include file
 services: cognitive-services
 author: diberry
 manager: nitinme
 ms.custom: seodec18
 ms.service: cognitive-services
-ms.subservice: luis
+ms.date: 02/14/2020
+ms.subservice: language-understanding
 ms.topic: include
 ms.custom: include file
-ms.date: 09/02/2019
 ms.author: diberry
 ---
 
 Management of contributions from collaborators depends on the current status of the app.
 
-**For [authoring resource migrated](../luis-migration-authoring.md) apps**: _contributors_ are managed in the Azure portal for the authoring resource, using the **Access control (IAM)** page. Add a user, using the collaborator's email address and the _contributor_ role. 
+**For [authoring resource migrated](../luis-migration-authoring.md) apps**: _contributors_ are managed in the Azure portal for the authoring resource, using the **Access control (IAM)** page. Add a user, using the collaborator's email address and the _contributor_ role.
 
-**For apps that have not migrated yet**: all _collaborators_ are managed in the LUIS portal from each app's **Manage -> Collaborators** page. On this page, [add a user's email address](../luis-how-to-collaborate.md). This provides authoring access to this app only. 
+**For apps that have not migrated yet**: all _collaborators_ are managed in the LUIS portal from each app's **Manage -> Collaborators** page. On this page, [add a user's email address](../luis-how-to-collaborate.md). This provides authoring access to this app only.
 
 

articles/cognitive-services/LUIS/includes/manage-contributors-authoring-resource.md

@@ -1,24 +1,24 @@
 ---
 title: include file
-description: include file 
+description: include file
 services: cognitive-services
 author: diberry
 manager: nitinme
 ms.custom: seodec18
 ms.service: cognitive-services
-ms.subservice: luis
+ms.date: 02/14/2020
+ms.subservice: language-understanding
 ms.topic: include
 ms.custom: include file
-ms.date: 09/02/2019
 ms.author: diberry
 ---
 If your apps need to be authored by other people, you need to add the associated email addresses in the Azure portal's authoring resource.
 
-If you are the **owner or administrator of your Azure subscription**, you can add a contributor to the resource. 
+If you are the **owner or administrator of your Azure subscription**, you can add a contributor to the resource.
 
 If you are **not the owner or administrator of your Azure subscription**, your Azure account needs to have `Microsoft.Authorization/roleAssignments/write` permissions.
 
-If you have trouble with this role assignment, review: 
+If you have trouble with this role assignment, review:
 
 * [Azure role assignments](../../../role-based-access-control/role-assignments-portal.md)
  * [Azure access control troubleshooting](../../../role-based-access-control/troubleshooting.md#problems-with-rbac-role-assignments)