Skip to content

Commit 6831ddb

Browse files
committed
fixing typos, information about importing
1 parent d9ea297 commit 6831ddb

File tree

4 files changed

+7
-10
lines changed

4 files changed

+7
-10
lines changed

articles/cognitive-services/language-service/conversational-language-understanding/includes/rest-api/get-deployment-status.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,7 @@ ms.date: 05/16/2022
99
ms.author: aahi
1010
---
1111

12-
> [!NOTE]
13-
> When you send a successful deployment request, the full request URL for checking the job's status (including your endpoint, project name, and job ID) is contained in the response's `location-location` header.
12+
When you send a successful deployment request, the full request URL for checking the job's status (including your endpoint, project name, and job ID) is contained in the response's `operation-location` header.
1413

1514
Use the following **GET** request to get the status of your deployment job. Replace the placeholder values below with your own values.
1615

articles/cognitive-services/language-service/conversational-language-understanding/includes/rest-api/get-import-status.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,12 @@ manager: nitinme
66
ms.service: cognitive-services
77
ms.subservice: language-service
88
ms.topic: include
9-
ms.date: 05/13/2022
9+
ms.date: 03/17/2023
1010
ms.author: aahi
1111
ms.custom: language-service-clu
1212
---
1313

14-
> [!NOTE]
15-
> When you send a successful project import request, the full request URL for checking the import job's status (including your endpoint, project name, and job ID) is contained in the response's `location-location` header.
14+
When you send a successful project import request, the full request URL for checking the import job's status (including your endpoint, project name, and job ID) is contained in the response's `operation-location` header.
1615

1716
Use the following **GET** request to query the status of your import job. You can use the URL you received from the previous step, or replace the placeholder values below with your own values.
1817

articles/cognitive-services/language-service/conversational-language-understanding/includes/rest-api/get-training-status.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,11 @@ manager: nitinme
55
ms.service: cognitive-services
66
ms.subservice: language-service
77
ms.topic: include
8-
ms.date: 05/12/2022
8+
ms.date: 03/17/2023
99
ms.author: aahi
1010
---
1111

12-
> [!NOTE]
13-
> When you send a successful training request, the full request URL for checking the job's status (including your endpoint, project name, and job ID) is contained in the response's `location-location` header.
12+
When you send a successful training request, the full request URL for checking the job's status (including your endpoint, project name, and job ID) is contained in the response's `operation-location` header.
1413

1514
Use the following **GET** request to get the status of your model's training progress. Replace the placeholder values below with your own values.
1615

articles/cognitive-services/language-service/conversational-language-understanding/includes/rest-api/import-project.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Use the following URL when creating your API request. Replace the placeholder va
2323
|Placeholder |Value | Example |
2424
|---------|---------|---------|
2525
|`{ENDPOINT}` | The endpoint for authenticating your API request. | `https://<your-custom-subdomain>.cognitiveservices.azure.com` |
26-
|`{PROJECT-NAME}` | The name for your project. This value is case-sensitive. | `myProject` |
26+
|`{PROJECT-NAME}` | The name for your project. This value is case-sensitive, and must match the Project name in the JSON file you're importing. | `EmailAppDemo` |
2727
|`{API-VERSION}` | The version of the API you're calling. The value referenced here is for the latest released [model version](../../../concepts/model-lifecycle.md#choose-the-model-version-used-on-your-data). | `2022-05-01` |
2828

2929
### Headers
@@ -96,7 +96,7 @@ The JSON body you send will look similar to the below. See the [reference docume
9696
|Key |Placeholder |Value | Example |
9797
|---------|---------|----------|--|
9898
| api-version | `{API-VERSION}` | The version of the API you're calling. The version used here must be the same API model version in the URL. See the [model version](../../../concepts/model-lifecycle.md#choose-the-model-version-used-on-your-data) article to learn more. | `2022-05-01` |
99-
| `projectName` | `{PROJECT-NAME}` | The name of your project. This value is case-sensitive. | `EmailApp` |
99+
| `projectName` | `{PROJECT-NAME}` | The name of your project. This value is case-sensitive. | `EmailAppDemo` |
100100
| `language` | `{LANGUAGE-CODE}` | A string specifying the language code for the utterances used in your project. If your project is a multilingual project, choose the [language code](../../language-support.md) of the majority of the utterances. |`en-us`|
101101
| `multilingual` | `true`| A boolean value that enables you to have documents in multiple languages in your dataset. When your model is deployed, you can query the model in any [supported language](../../language-support.md#multi-lingual-option). This includes languages that aren't included in your training documents. | `true`|
102102
| `dataset` | `{DATASET}` | See [how to train a model](../../how-to/tag-utterances.md) for information on splitting your data between a testing and training set. Possible values for this field are `Train` and `Test`. |`Train`|

0 commit comments

Comments
 (0)