feedback

Author: laujan

articles/ai-services/translator/containers/install-run.md

@@ -7,7 +7,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-translator
 ms.topic: how-to
-ms.date: 04/19/2024
+ms.date: 06/20/2024
 ms.author: lajanuar
 recommendations: false
 keywords: on-premises, Docker, container, identify
@@ -312,7 +312,7 @@ The following example shows the formatting for the `docker run` command with pla
 |:-------------|:-------|:---:|
 | `[image]` | The container image you want to use. | `mcr.microsoft.com/azure-cognitive-services/translator/text-translation` |
 | `{LICENSE_MOUNT}` | The path where the license is downloaded, and mounted.  | `/host/license:/path/to/license/directory` |
- | `{MODEL_MOUNT_PATH}`| The path where the machine translation models are downloaded, and mounted. Your directory structure must be formatted as **/usr/local/models** | `/host/translator/models:/usr/local/models`|
+| `{MODEL_MOUNT_PATH}`| The path where the machine translation models are downloaded, and mounted. Your directory structure must be formatted as **/usr/local/models** | `/host/translator/models:/usr/local/models`|
 | `{ENDPOINT_URI}` | The endpoint for authenticating your service request. You can find it on your resource's **Key and endpoint** page, in the Azure portal. | `https://<your-custom-subdomain>.cognitiveservices.azure.com` |
 | `{API_KEY}` | The key for your Text Translation resource. You can find it on your resource's **Key and endpoint** page, in the Azure portal. |`{string}`|
 | `{LANGUAGES_LIST}` | List of language codes separated by commas. It's mandatory to have English (en) language as part of the list.| `en`, `fr`, `it`, `zu`, `uk` |
@@ -477,15 +477,15 @@ If you installed Docker Desktop CLI, it includes Docker compose and its prerequi
           image:  mcr.microsoft.com/azure-cognitive-services/textanalytics/language:latest
           environment:
               - EULA=accept
-              - billing={TRANSLATOR_ENDPOINT_URI}
-              - apiKey={TRANSLATOR_KEY}
+              - billing={LANGUAGE_RESOURCE_ENDPOINT_URI}
+              - apiKey={LANGUAGE_RESOURCE_KEY}
         azure-ai-read:
           container_name: azure-ai-read
           image:  mcr.microsoft.com/azure-cognitive-services/vision/read:latest
           environment:
               - EULA=accept
-              - billing={TRANSLATOR_ENDPOINT_URI}
-              - apiKey={TRANSLATOR_KEY}
+              - billing={COMPUTER_VISION_ENDPOINT_URI}
+              - apiKey={COMPUTER_VISION_KEY}
     ```
 
 1. Open a terminal navigate to the `container-environment` folder, and start the containers with the following `docker-compose` command:

articles/ai-services/translator/document-translation/document-sdk-overview.md

@@ -176,7 +176,7 @@ DocumentTranslationInput input = new DocumentTranslationInput(sourceUri, targetU
 
 ***Synchronous single document translation***
 
-[Single document translation](/dotnet/api/overview/azure/ai.translation.document-readme?view=azure-dotnet-preview#single-document-translation&preserve-view=true)
+[Single document translation](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/translation/Azure.AI.Translation.Document/samples/Sample5_SynchronousTranslation.md)
 
 ### [Python](#tab/python)
 

articles/ai-services/translator/document-translation/quickstarts/rest-api.md

@@ -92,13 +92,13 @@ Before you run the **POST** request, replace `{your-document-translator-endpoint
 ***PowerShell***
 
 ```powershell
-cmd /c curl "{your-document-translator-endpoint}/translator/text/batch/v1.1/batches" -i -X POST --header "Content-Type: application/json" --header "Ocp-Apim-Subscription-Key: {your-key}" --data "@document-translation.json"
+cmd /c curl "{document-translation-endpoint}/translator/document/batches?api-version={date}" -i -X POST --header "Content-Type: application/json" --header "Ocp-Apim-Subscription-Key: {your-key}" --data "@document-translation.json"
 ```
 
 ***command prompt / terminal***
 
-```curl
-curl "{your-document-translator-endpoint}/translator/text/batch/v1.1/batches" -i -X POST --header "Content-Type: application/json" --header "Ocp-Apim-Subscription-Key: {your-key}" --data "@document-translation.json"
+```bash
+curl "{document-translation-endpoint}/translator/document/batches?api-version={date}" -i -X POST --header "Content-Type: application/json" --header "Ocp-Apim-Subscription-Key: {your-key}" --data "@document-translation.json"
 ```
 
 Upon successful completion:
@@ -142,13 +142,13 @@ To call the synchronous translation feature via the [REST API](../reference/sync
 
     ```bash
 
-    curl -i -X POST "{your-document-translation-endpoint}/translator/document:translate?sourceLanguage=en&targetLanguage=hi&api-version=2023-11-01-preview" -H "Ocp-Apim-Subscription-Key:{your-key}"  -F "document={path-to-your-document-with-file-extension};type={ContentType}/{file-extension}" -F "glossary={path-to-your-glossary-with-file-extension};type={ContentType}/{file-extension}" -o "{path-to-output-file}"
+    curl -i -X POST "{document-translation-endpoint}/translator/document:translate?targetLanguage={target_language}&api-version={date}" -H "Ocp-Apim-Subscription-Key:{your-key}"  -F "document={path-to-your-document-with-file-extension};type={ContentType}/{file-extension}" -F "glossary={path-to-your-glossary-with-file-extension};type={ContentType}/{file-extension}" -o "{path-to-output-file}"
     ```
 
     ***PowerShell***
 
     ```powershell
-    cmd /c curl "{your-document-translation-endpoint}/translator/document:translate?sourceLanguage=en&targetLanguage=es&api-version=2023-11-01-preview" -i -X POST  -H "Ocp-Apim-Subscription-Key: {your-key}" -F "{path-to-your-document-with-file-extension};type=text/{file-extension}" -o "{path-to-output-file}
+    cmd /c curl "{document-translation-endpoint}/translator/document:translate?targetLanguage={target_language}&api-version={date}" -i -X POST  -H "Ocp-Apim-Subscription-Key: {your-key}" -F "{path-to-your-document-with-file-extension};type=text/{file-extension}" -o "{path-to-output-file}
 
     ```
 
@@ -164,4 +164,4 @@ That's it, congratulations! You just learned to translate documents using the Az
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Document Translation REST API guide](../reference/rest-api-guide.md "Learn more about Document Translation REST API operations).
+> [Document Translation REST API guide](../reference/rest-api-guide.md "Learn more about Document Translation REST API operations)

articles/ai-services/translator/document-translation/reference/start-batch-translation.md

@@ -23,17 +23,6 @@ HTTP method: **POST**
 * Use the `Start Translation` method to execute an asynchronous batch translation request.
 * The method requires an Azure Blob storage account with storage containers for your source and translated documents.
 
-> [!TIP]
-> This method returns the job `id` parameter for the [get-translation-status](get-translation-status.md), [get-documents-status](get-documents-status.md), [get-document-status](get-document-status.md), and [cancel-translation](cancel-translation.md) request query strings.
-
-* You can find the job `id`  in the POST `start-batch-translation` method response Header `Operation-Location`  URL value. The alphanumeric string following the `/document/` parameter is the operation's job **`id`**:
-
-|**Response header**|**Response URL**|
-|-----------------------|----------------|
-|Operation-Location   | {document-translation-endpoint}/translator/document/`9dce0aa9-78dc-41ba-8cae-2e2f3c2ff8ec`?api-version=2024-05-01|
-
-* You can also use a [get-translations-status](../reference/get-translations-status.md) request to retrieve a list of translation jobs and their `id`s.
-
 ## Request URL
 
 > [!IMPORTANT]
@@ -63,7 +52,7 @@ Request headers are:
 
 * Glossaries can be included in the request. If the glossary is invalid or unreachable during translation, an error is indicated in the document status.
 
-* If a file with the same name already exists in the target destination, the job fails. 
+* If a file with the same name already exists in the target destination, the job fails.
 
 * The targetUrl for each target language must be unique.
 
@@ -274,6 +263,17 @@ This sample request shows a single document translated into two target languages
 }
 ```
 
+> [!TIP]
+> This method returns the job `id` parameter for the [get-translation-status](get-translation-status.md), [get-documents-status](get-documents-status.md), [get-document-status](get-document-status.md), and [cancel-translation](cancel-translation.md) request query strings.
+
+* You can find the job `id`  in the POST `start-batch-translation` method response Header `Operation-Location`  URL value. The alphanumeric string following the `/document/` parameter is the operation's job **`id`**:
+
+    |**Response header**|**Response URL**|
+    |-----------------------|----------------|
+    |Operation-Location   | {document-translation-endpoint}/translator/document/`9dce0aa9-78dc-41ba-8cae-2e2f3c2ff8ec`?api-version=2024-05-01|
+
+* You can also use a [get-translations-status](../reference/get-translations-status.md) request to retrieve a list of translation jobs and their `id`s.
+
 ## Response status codes
 
 The following are the possible HTTP status codes that a request returns.

articles/ai-services/translator/toc.yml

@@ -125,15 +125,15 @@ items:
     href: document-translation/reference/rest-api-guide.md
   - name: Quickstarts
     items:
-    - name: "🆕 Quickstart: Document Translation client libraries"
+    - name: "Quickstart: Document Translation client libraries"
       displayName: batch,c#,dotnet,.net,python,blob,set up,install,cli,storage,domain,custom domain
       href: document-translation/quickstarts/client-library-sdks.md
-    - name: "🆕 Quickstart: Document Translation REST APIs"
+    - name: "Quickstart: Document Translation REST APIs"
       displayName: get,post,cancel,delete
       href: document-translation/quickstarts/rest-api.md
   - name: How-to guides
     items:
-    - name: 🆕 Use Document Translation APIs programmatically
+    - name: Use Document Translation APIs programmatically
       displayName: get started,batch,sdk,c#,.net,dotnet,python,javascript,java,go,source,target,blob,set up,storage
       href: document-translation/how-to-guides/use-rest-api-programmatically.md
   - name: Authentication and authorization
@@ -146,7 +146,7 @@ items:
       href: document-translation/how-to-guides/create-sas-tokens.md
   - name: Reference
     items:
-      - name: 🆕 Document Translation operations
+      - name: Document Translation operations
         href: document-translation/reference/rest-api-guide.md
       - name: Translate a single document
         href: document-translation/reference/translate-document.md