Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
     "redirections": [
+    {
+      "source_path": "articles/network-watcher/network-watcher-connectivity-rest.md",
+      "redirect_url": "/previous-versions/azure/network-watcher/network-watcher-connectivity-rest",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/application-gateway/resource-manager-template-samples.md",
       "redirect_url": "/previous-versions/azure/application-gateway/resource-manager-template-samples",

articles/ai-services/computer-vision/includes/identity-sensitive-attributes.md

@@ -11,5 +11,4 @@ ms.author: pafarley
 ---
 
 > [!CAUTION]
-> Microsoft has retired facial recognition capabilities that can be used to try to infer emotional states and identity attributes which, if misused, can subject people to stereotyping, discrimination or unfair denial of services. These include capabilities that predict emotion, gender, age, smile, facial hair, hair and makeup. Read more about this decision [here](https://azure.microsoft.com/blog/responsible-ai-investments-and-safeguards-for-facial-recognition/).
-
+> Microsoft has retired or limited facial recognition capabilities that can be used to try to infer emotional states and identity attributes which, if misused, can subject people to stereotyping, discrimination or unfair denial of services. The retired capabilities are emotion and gender. The limited capabilities are age, smile, facial hair, hair and makeup. Email [Azure Face API](mailto:[email protected]) if you have a responsible use case that would benefit from the use of any of the limited capabilities. Read more about this decision [here](https://azure.microsoft.com/blog/responsible-ai-investments-and-safeguards-for-facial-recognition/).

articles/ai-services/custom-vision-service/index.yml

@@ -101,9 +101,9 @@ landingContent:
       - linkListType: reference
         links:
           - text: Training API
-            url: https://go.microsoft.com/fwlink/?linkid=865446
+            url: /rest/api/customvision/train-project
           - text: Prediction API
-            url: https://go.microsoft.com/fwlink/?linkid=865445
+            url: /rest/api/customvision/operation-groups
           - text: .NET SDK
             url: /dotnet/api/overview/azure/custom-vision
           - text: Python SDK

articles/ai-services/language-service/conversational-language-understanding/concepts/best-practices.md

@@ -1,7 +1,7 @@
 ---
 title: Multilingual projects
 titleSuffix: Azure AI services
-description: Learn about which how to make use of multilingual projects in conversational language understanding
+description: Learn about how to make use of multilingual projects in conversational language understanding.
 #services: cognitive-services
 author: jboback
 manager: nitinme
@@ -13,34 +13,34 @@ ms.author: jboback
 
 # Multilingual projects
 
-Conversational language understanding makes it easy for you to extend your project to several languages at once. When you enable multiple languages in projects, you'll be able to add language specific utterances and synonyms to your project, and get multilingual predictions for your intents and entities. 
+Conversational language understanding makes it easy for you to extend your project to several languages at once. When you enable multiple languages in projects, you can add language-specific utterances and synonyms to your project. You can get multilingual predictions for your intents and entities.
 
 ## Multilingual intent and learned entity components
 
-When you enable multiple languages in a project, you can train the project primarily in one language and immediately get predictions in others. 
+When you enable multiple languages in a project, you can train the project primarily in one language and immediately get predictions in other languages.
 
-For example, you can train your project entirely with English utterances, and query it in: French, German, Mandarin, Japanese, Korean, and others. Conversational language understanding makes it easy for you to scale your projects to multiple languages by using multilingual technology to train your models.
+For example, you can train your project entirely with English utterances and query it in French, German, Mandarin, Japanese, Korean, and others. Conversational language understanding makes it easy for you to scale your projects to multiple languages by using multilingual technology to train your models.
 
-Whenever you identify that a particular language is not performing as well as other languages, you can add utterances for that language in your project. In the [tag utterances](../how-to/tag-utterances.md) page in Language Studio, you can select the language of the utterance you're adding. When you introduce examples for that language to the model, it is introduced to more of the syntax of that language, and learns to predict it better.
+Whenever you identify that a particular language isn't performing as well as other languages, you can add utterances for that language in your project. In the [tag utterances](../how-to/tag-utterances.md) page in Language Studio, you can select the language of the utterance you're adding. When you introduce examples for that language to the model, it's introduced to more of the syntax of that language and learns to predict it better.
 
-You aren't expected to add the same amount of utterances for every language. You should build the majority of your project in one language, and only add a few utterances in languages you observe aren't performing well. If you create a project that is primarily in English, and start testing it in French, German, and Spanish, you might observe that German doesn't perform as well as the other two languages. In that case, consider adding 5% of your original English examples in German, train a new model and test in German again. You should see better results for German queries. The more utterances you add, the more likely the results are going to get better. 
+You aren't expected to add the same number of utterances for every language. You should build most of your project in one language and only add a few utterances in languages that you observe aren't performing well. If you create a project that's primarily in English and start testing it in French, German, and Spanish, you might observe that German doesn't perform as well as the other two languages. In that case, consider adding 5% of your original English examples in German, train a new model, and test in German again. You should see better results for German queries. The more utterances you add, the more likely the results are going to get better.
 
-When you add data in another language, you shouldn't expect it to negatively affect other languages. 
+When you add data in another language, you shouldn't expect it to negatively affect other languages.
 
 ## List and prebuilt components in multiple languages
 
-Projects with multiple languages enabled will allow you to specify synonyms **per language** for every list key. Depending on the language you query your project with, you will only get matches for the list component with synonyms of that language. When you query your project, you can specify the language in the request body:
+Projects with multiple languages enabled allow you to specify synonyms *per language* for every list key. Depending on the language you query your project with, you only get matches for the list component with synonyms of that language. When you query your project, you can specify the language in the request body:
 
 ```json
 "query": "{query}"
 "language": "{language code}"
 ```
 
-If you do not provide a language, it will fall back to the default language of your project. See the [language support](../language-support.md) article for a list of different language codes.
+If you don't provide a language, it falls back to the default language of your project. For a list of different language codes, see [Language support](../language-support.md).
 
-Prebuilt components are similar, where you should expect to get predictions for prebuilt components that are available in specific languages. The request's language again determines which components are attempting to be predicted. See the [prebuilt components](../prebuilt-component-reference.md) reference article for the language support of each prebuilt component.
+Prebuilt components are similar, where you should expect to get predictions for prebuilt components that are available in specific languages. The request's language again determines which components are attempting to be predicted. For information on the language support of each prebuilt component, see the [Supported prebuilt entity components](../prebuilt-component-reference.md).
 
-## Next steps
+## Related content
 
 * [Tag utterances](../how-to/tag-utterances.md) 
 * [Train a model](../how-to/train-model.md)

articles/ai-services/language-service/conversational-language-understanding/concepts/entity-components.md

@@ -10,18 +10,17 @@ ms.author: jboback
 
 ## Balance training data
 
-You should try to keep your schema well balanced when it comes to training data. Including large quantities of one intent, and very few of another will result in a model that is heavily biased towards particular intents.
+When it comes to training data, try to keep your schema well balanced. Including large quantities of one intent and very few of another results in a model that's biased toward particular intents.
 
-To address this, you can you may need to downsample your training set, or add to it. Downsampling can be done either by:
-* Getting rid of a certain percentage of the training data randomly. 
-* In a more systematic manner by analyzing the dataset, and removing overrepresented duplicate entries.
+To address this scenario, you might need to downsample your training set. Or you might need to add to it. To downsample, you can:
 
-You can also add to the training set by selecting **Suggest Utterances** in **Data labeling** tab in Language studio. Conversational Language Understanding will send a call to [Azure OpenAI](../../../openai/overview.md) to generate similar utterances. 
+* Get rid of a certain percentage of the training data randomly.
+* Analyze the dataset and remove overrepresented duplicate entries, which is a more systematic manner.
 
+To add to the training set, in Language Studio, on the **Data labeling** tab, select **Suggest utterances**. Conversational Language Understanding sends a call to [Azure OpenAI](../../../openai/overview.md) to generate similar utterances.
 
-:::image type="content" source="../media/suggest-utterances.png" alt-text="A screenshot showing utterance suggestion in Language Studio." lightbox="../media/suggest-utterances.png":::
+:::image type="content" source="../media/suggest-utterances.png" alt-text="Screenshot that shows an utterance suggestion in Language Studio." lightbox="../media/suggest-utterances.png":::
 
-You should also look for unintended "patterns" in the training set. For example, if the training set for a particular intent is all lowercase, or starts with a particular phrase. In such cases, the model you train might learn these unintended biases in the training set instead of being able to generalize.
-
-We recommend introducing casing and punctuation diversity in the training set. If your model is expected to handle variations, be sure to have a training set that also reflects that diversity. For example, include some utterances in proper casing, and some in all lowercase.
+You should also look for unintended "patterns" in the training set. For example, look to see if the training set for a particular intent is all lowercase or starts with a particular phrase. In such cases, the model you train might learn these unintended biases in the training set instead of being able to generalize.
 
+We recommend that you introduce casing and punctuation diversity in the training set. If your model is expected to handle variations, be sure to have a training set that also reflects that diversity. For example, include some utterances in proper casing and some in all lowercase.

articles/ai-services/language-service/conversational-language-understanding/concepts/multiple-languages.md

@@ -10,13 +10,10 @@ ms.author: jboback
 
 ## Clearly label utterances 
 
-* Ensure that the concepts that your entities refer to are well defined and separable. Check if you can easily determine the differences reliably. If you can't, this may be an indication that the learned component will also have difficulty. 
+* Ensure that the concepts that your entities refer to are well defined and separable. Check if you can easily determine the differences reliably. If you can't, this lack of distinction might indicate that the learned component will also have difficulty.
+* If there's a similarity between entities, ensure that there's some aspect of your data that provides a signal for the difference between them.
 
-* If there's a similarity between entities ensure that there's some aspect of your data that provides a signal for the difference between them. 
-
-    For example, if you built a model to book flights, a user might use an utterance like "*I want a flight from Boston to Seattle.*" The *origin city* and  *destination city* for such utterances would be expected to be similar. A signal to differentiate "*Origin city*" might be that it's often be preceded by the word "*from.*"
+    For example, if you built a model to book flights, a user might use an utterance like "I want a flight from Boston to Seattle." The *origin city* and *destination city* for such utterances would be expected to be similar. A signal to differentiate *origin city* might be that the word *from* often precedes it.
 
 * Ensure that you label all instances of each entity in both your training and testing data. One approach is to use the search function to find all instances of a word or phrase in your data to check if they're correctly labeled.
-
-*	Label test data for entities that have no [learned component](../concepts/entity-components.md#learned-component) and also for those that do. This will help ensure that your evaluation metrics are accurate.
-
+* Label test data for entities that have no [learned component](../concepts/entity-components.md#learned-component) and also for the entities that do. This practice helps to ensure that your evaluation metrics are accurate.