container data residency

Author: laujan

articles/ai-services/translator/containers/translate-text-parameters.md

@@ -130,7 +130,7 @@ If an error occurs, the request returns a JSON error response. The error code is
 > * Each sample runs on the `localhost` that you specified with the `docker run` command.
 > * While your container is running, `localhost` points to the container itself.
 > * You don't have to use `localhost:5000`. You can use any port that is not already in use in your host environment.
-> To specify a port, use the `-p` option.
+
 
 ### Translate a single input
 
@@ -279,7 +279,7 @@ namespace TranslateContainer
 Translating multiple strings at once is simply a matter of specifying an array of strings in the request body.
 
 ```bash
-curl -X POST "http://localhost:{port}/translate?api-version=3.0&from=en&to=zh-Hans" -H "Ocp-Apim-Subscription-Key: <client-secret>" -H "Content-Type: application/json; charset=UTF-8" -d "[{'Text':'Hello, what is your name?'}, {'Text':'I am fine, thank you.'}]"
+curl -X POST "http://localhost:5000/translate?api-version=3.0&from=en&to=zh-Hans" -H "Ocp-Apim-Subscription-Key: <client-secret>" -H "Content-Type: application/json; charset=UTF-8" -d "[{'Text':'Hello, what is your name?'}, {'Text':'I am fine, thank you.'}]"
 ```
 
 The response contains the translation of all pieces of text in the exact same order as in the request.
@@ -305,7 +305,7 @@ The response body is:
 This example shows how to translate the same input to several languages in one request.
 
 ```bash
-curl -X POST "http://localhost:{port}/translate?api-version=3.0&from=en&to=zh-Hans&to=de" -H "Ocp-Apim-Subscription-Key: <client-secret>" -H "Content-Type: application/json; charset=UTF-8" -d "[{'Text':'Hello, what is your name?'}]"
+curl -X POST "http://localhost:5000/translate?api-version=3.0&from=en&to=zh-Hans&to=de" -H "Ocp-Apim-Subscription-Key: <client-secret>" -H "Content-Type: application/json; charset=UTF-8" -d "[{'Text':'Hello, what is your name?'}]"
 ```
 
 The response body is:
@@ -333,7 +333,7 @@ It's common to translate content that includes markup such as content from an HT
 Here's a sample request to illustrate.
 
 ```bash
-curl -X POST "http://localhost:{port}/translate?api-version=3.0&from=en&to=zh-Hans&textType=html" -H "Ocp-Apim-Subscription-Key: <client-secret>" -H "Content-Type: application/json; charset=UTF-8" -d "[{'Text':'<div class=\"notranslate\">This will not be translated.</div><div>This will be translated.</div>'}]"
+curl -X POST "http://localhost:5000/translate?api-version=3.0&from=en&to=zh-Hans&textType=html" -H "Ocp-Apim-Subscription-Key: <client-secret>" -H "Content-Type: application/json; charset=UTF-8" -d "[{'Text':'<div class=\"notranslate\">This will not be translated.</div><div>This will be translated.</div>'}]"
 ```
 
 The response is:
@@ -361,7 +361,7 @@ The markup to supply uses the following syntax.
 For example, consider the English sentence "The word wordomatic is a dictionary entry." To preserve the word _wordomatic_ in the translation, send the request:
 
 ```bash
-curl -X POST "http://localhost:{port}/translate?api-version=3.0&from=en&to=de" -H "Ocp-Apim-Subscription-Key: <client-secret>" -H "Content-Type: application/json; charset=UTF-8" -d "[{'Text':'The word <mstrans:dictionary translation=\"wordomatic\">word or phrase</mstrans:dictionary> is a dictionary entry.'}]"
+curl -X POST "http://localhost:5000/translate?api-version=3.0&from=en&to=de" -H "Ocp-Apim-Subscription-Key: <client-secret>" -H "Content-Type: application/json; charset=UTF-8" -d "[{'Text':'The word <mstrans:dictionary translation=\"wordomatic\">word or phrase</mstrans:dictionary> is a dictionary entry.'}]"
 ```
 
 The result is:

articles/ai-services/translator/containers/transliterate-text-parameters.md

@@ -21,7 +21,7 @@ Convert characters or letters of a source language to the corresponding characte
 `POST` request:
 
 ```HTTP
- POST http://localhost:5000/transliterate?api-version=3.0&language={language}&fromScript={fromScript}&toScript={toScript}
+ POST http://localhost:{port}/transliterate?api-version=3.0&language={language}&fromScript={fromScript}&toScript={toScript}
 
 ```
 
@@ -107,7 +107,6 @@ The following limitations apply:
 > * Each sample runs on the `localhost` that you specified with the `docker run` command.
 > * While your container is running, `localhost` points to the container itself.
 > * You don't have to use `localhost:5000`. You can use any port that is not already in use in your host environment.
-> To specify a port, use the `-p` option.
 
 ### Transliterate with REST API
 

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

@@ -146,11 +146,6 @@ Document Translation data residency depends on the Azure region where your Trans
 ✔️ Feature: **Document Translation**</br>
 ✔️ Service endpoint:  **Custom:** &#8198;&#8198;&#8198; **`<name-of-your-resource.cognitiveservices.azure.com/translator/text/batch/v1.1`**
 
-* Translator resources **created** in any region in Europe (except Switzerland) are **processed** at data center in France Central and West Europe.
-* Translator resources **created** in any region in Switzerland are **processed** at data center in Switzerland North and Switzerland West.
-* Translator resources **created** in any region in Asia Pacific or Australia are **processed** at data center in Japan East and Southeast Asia.
-* Translator resource **created** in all other regions including Global, North America, and South America are **processed** at data center in East US 2 and West US 2.
-
 |Resource region| Request processing data center |
 |----------------------------------|-----------------------|
 |**Any region within Europe (except Switzerland)**| Europe: France Central &bull; West Europe|

articles/ai-services/translator/reference/v3-0-reference.md

@@ -29,6 +29,8 @@ Requests to Translator are, in most cases, handled by the datacenter that is clo
 
 To force the request to be handled within a specific geography, use the desired geographical endpoint. All requests are processed among the datacenters within the geography.
 
+✔️ Feature: **Translator Text** </br>
+
 | Service endpoint | Request processing data center |
 |------------------|--------------------------|
 |**Global (recommended):**</br>**`api.cognitive.microsofttranslator.com`**|Closest available data center.|

articles/ai-services/translator/text-translation-overview.md

@@ -62,14 +62,9 @@ Add Text Translation to your projects and applications using the following resou
 
 Text Translation data residency depends on the Azure region where your Translator resource was created:
 
-* Translator resources **created** in any region in Europe are **processed** at data center in West Europe and North Europe.
-* Translator resources **created** in any region in Asia or Australia are **processed** at data center in Southeast Asia and Australia East.
-* Translator resource **created** in all other regions including Global, North America and South America are **processed** at data center in East US and West US 2.
-
 ### Text Translation data residency
 
 ✔️ Feature: **Translator Text** </br>
-✔️ Region where resource created: **Any**
 
 | Service endpoint | Request processing data center |
 |------------------|--------------------------|