Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into patricka-archive1.1

Author: PatAltimore

articles/aks/tutorial-kubernetes-deploy-application.md

@@ -1,36 +1,36 @@
 ---
-title: Kubernetes on Azure tutorial  - Deploy an application
+title: Kubernetes on Azure tutorial - Deploy an application
 description: In this Azure Kubernetes Service (AKS) tutorial, you deploy a multi-container application to your cluster using a custom image stored in Azure Container Registry.
 services: container-service
 ms.topic: tutorial
-ms.date: 05/24/2021
-
+ms.date: 01/04/2023
 ms.custom: mvc, devx-track-azurepowershell
 
 #Customer intent: As a developer, I want to learn how to deploy apps to an Azure Kubernetes Service (AKS) cluster so that I can deploy and run my own applications.
 ---
 
 # Tutorial: Run applications in Azure Kubernetes Service (AKS)
 
-Kubernetes provides a distributed platform for containerized applications. You build and deploy your own applications and services into a Kubernetes cluster, and let the cluster manage the availability and connectivity. In this tutorial, part four of seven, a sample application is deployed into a Kubernetes cluster. You learn how to:
+Kubernetes provides a distributed platform for containerized applications. You build and deploy your own applications and services into a Kubernetes cluster and let the cluster manage the availability and connectivity. In this tutorial, part four of seven, you deploy a sample application into a Kubernetes cluster. You learn how to:
 
 > [!div class="checklist"]
-> * Update a Kubernetes manifest file
-> * Run an application in Kubernetes
-> * Test the application
+>
+> * Update a Kubernetes manifest file.
+> * Run an application in Kubernetes.
+> * Test the application.
 
-In later tutorials, this application is scaled out and updated.
+In later tutorials, you'll scale out and update your application.
 
-This quickstart assumes a basic understanding of Kubernetes concepts. For more information, see [Kubernetes core concepts for Azure Kubernetes Service (AKS)][kubernetes-concepts].
+This quickstart assumes you have a basic understanding of Kubernetes concepts. For more information, see [Kubernetes core concepts for Azure Kubernetes Service (AKS)][kubernetes-concepts].
 
 > [!TIP]
-> AKS clusters can use GitOps for configuration management. This enables declarations of your cluster's state, which are pushed to source control, to be applied to the cluster automatically. To learn how to use GitOps to deploy an application with an AKS cluster, see the tutorial [Use GitOps with Flux v2][gitops-flux-tutorial] and follow the [prerequisites for Azure Kubernetes Service clusters][gitops-flux-tutorial-aks].
+> AKS clusters can use GitOps for configuration management. GitOp enables declarations of your cluster's state, which are pushed to source control, to be applied to the cluster automatically. To learn how to use GitOps to deploy an application with an AKS cluster, see the [prerequisites for Azure Kubernetes Service clusters][gitops-flux-tutorial-aks] in the [GitOps with Flux v2][gitops-flux-tutorial] tutorial.
 
 ## Before you begin
 
-In previous tutorials, an application was packaged into a container image, this image was uploaded to Azure Container Registry, and a Kubernetes cluster was created.
+In previous tutorials, you packaged an application into a container image, uploaded the image to Azure Container Registry, and created a Kubernetes cluster.
 
-To complete this tutorial, you need the pre-created `azure-vote-all-in-one-redis.yaml` Kubernetes manifest file. This file was downloaded with the application source code in a previous tutorial. Verify that you've cloned the repo, and that you have changed directories into the cloned repo. If you haven't done these steps, and would like to follow along, start with [Tutorial 1 – Create container images][aks-tutorial-prepare-app].
+To complete this tutorial, you need the pre-created `azure-vote-all-in-one-redis.yaml` Kubernetes manifest file. This file download was included with the application source code in a previous tutorial. Verify that you've cloned the repo and that you've changed directories into the cloned repo. If you haven't done these steps and would like to follow along, start with [Tutorial 1: Prepare an application for AKS][aks-tutorial-prepare-app].
 
 ### [Azure CLI](#tab/azure-cli)
 
@@ -48,37 +48,37 @@ In these tutorials, an Azure Container Registry (ACR) instance stores the contai
 
 ### [Azure CLI](#tab/azure-cli)
 
-Get the ACR login server name using the [az acr list][az-acr-list] command as follows:
+Get the ACR login server name using the [az acr list][az-acr-list] command.
 
 ```azurecli
 az acr list --resource-group myResourceGroup --query "[].{acrLoginServer:loginServer}" --output table
 ```
 
 ### [Azure PowerShell](#tab/azure-powershell)
 
-Get the ACR login server name using the [Get-AzContainerRegistry][get-azcontainerregistry] cmdlet as follows:
+Get the ACR login server name using the [Get-AzContainerRegistry][get-azcontainerregistry] cmdlet.
 
 ```azurepowershell
 (Get-AzContainerRegistry -ResourceGroupName myResourceGroup -Name <acrName>).LoginServer
 ```
 
 ---
 
-The sample manifest file from the git repo cloned in the first tutorial uses the images from Microsoft Container Registry (*mcr.microsoft.com*). Make sure that you're in the cloned *azure-voting-app-redis* directory, then open the manifest file with a text editor, such as `vi`:
+The sample manifest file from the git repo you cloned in the first tutorial uses the images from Microsoft Container Registry (*mcr.microsoft.com*). Make sure you're in the cloned *azure-voting-app-redis* directory, and then open the manifest file with a text editor, such as `vi`:
 
 ```console
 vi azure-vote-all-in-one-redis.yaml
 ```
 
-Replace *mcr.microsoft.com* with your ACR login server name. The image name is found on line 60 of the manifest file. The following example shows the default image name:
+Replace *mcr.microsoft.com* with your ACR login server name. You can find the image name on line 60 of the manifest file. The following example shows the default image name:
 
 ```yaml
 containers:
 - name: azure-vote-front
   image: mcr.microsoft.com/azuredocs/azure-vote-front:v1
 ```
 
-Provide your own ACR login server name so that your manifest file looks like the following example:
+Provide your own ACR login server name so your manifest file looks similar to the following example:
 
 ```yaml
 containers:
@@ -90,7 +90,7 @@ Save and close the file. In `vi`, use `:wq`.
 
 ## Deploy the application
 
-To deploy your application, use the [kubectl apply][kubectl-apply] command. This command parses the manifest file and creates the defined Kubernetes objects. Specify the sample manifest file, as shown in the following example:
+To deploy your application, use the [`kubectl apply`][kubectl-apply] command, specifying the sample manifest file. This command parses the manifest file and creates the defined Kubernetes objects.
 
 ```console
 kubectl apply -f azure-vote-all-in-one-redis.yaml
@@ -111,13 +111,13 @@ service "azure-vote-front" created
 
 When the application runs, a Kubernetes service exposes the application front end to the internet. This process can take a few minutes to complete.
 
-To monitor progress, use the [kubectl get service][kubectl-get] command with the `--watch` argument.
+To monitor progress, use the [`kubectl get service`][kubectl-get] command with the `--watch` argument.
 
 ```console
 kubectl get service azure-vote-front --watch
 ```
 
-Initially the *EXTERNAL-IP* for the *azure-vote-front* service is shown as *pending*:
+Initially the *EXTERNAL-IP* for the *azure-vote-front* service shows as *pending*.
 
 ```output
 azure-vote-front   LoadBalancer   10.0.34.242   <pending>     80:30676/TCP   5s
@@ -129,22 +129,23 @@ When the *EXTERNAL-IP* address changes from *pending* to an actual public IP add
 azure-vote-front   LoadBalancer   10.0.34.242   52.179.23.131   80:30676/TCP   67s
 ```
 
-To see the application in action, open a web browser to the external IP address of your service:
+To see the application in action, open a web browser to the external IP address of your service.
 
 :::image type="content" source="./media/container-service-kubernetes-tutorials/azure-vote.png" alt-text="Screenshot showing the container image Azure Voting App running in an AKS cluster opened in a local web browser" lightbox="./media/container-service-kubernetes-tutorials/azure-vote.png":::
 
-If the application didn't load, it might be due to an authorization problem with your image registry. To view the status of your containers, use the `kubectl get pods` command. If the container images can't be pulled, see [Authenticate with Azure Container Registry from Azure Kubernetes Service](cluster-container-registry-integration.md).
+If the application doesn't load, it might be an authorization problem with your image registry. To view the status of your containers, use the `kubectl get pods` command. If you can't pull the container images, see [Authenticate with Azure Container Registry from Azure Kubernetes Service](cluster-container-registry-integration.md).
 
 ## Next steps
 
-In this tutorial, a sample Azure vote application was deployed to a Kubernetes cluster in AKS. You learned how to:
+In this tutorial, you deployed a sample Azure vote application to a Kubernetes cluster in AKS. You learned how to:
 
 > [!div class="checklist"]
-> * Update a Kubernetes manifest files
-> * Run an application in Kubernetes
-> * Test the application
+>
+> * Update a Kubernetes manifest file.
+> * Run an application in Kubernetes.
+> * Test the application.
 
-Advance to the next tutorial to learn how to scale a Kubernetes application and the underlying Kubernetes infrastructure.
+In  the next tutorial, you'll learn how to scale a Kubernetes application and the underlying Kubernetes infrastructure.
 
 > [!div class="nextstepaction"]
 > [Scale Kubernetes application and infrastructure][aks-tutorial-scale]

articles/azure-monitor/app/codeless-overview.md

@@ -8,7 +8,7 @@ ms.reviewer: abinetabate
 
 # What is auto-instrumentation for Azure Monitor Application Insights?
 
-Auto-instrumentation collects [Application Insights](app-insights-overview.md) [telemetry](data-model.md).
+Auto-instrumentation quickly and easily enables [Application Insights](app-insights-overview.md) to make [telemetry](data-model.md) (metrics, requests and dependencies) available in your [Application Insights resource](create-workspace-resource.md).
 
 > [!div class="checklist"]
 > - No code changes required

articles/cognitive-services/language-service/text-analytics-for-health/concepts/assertion-detection.md

@@ -8,25 +8,25 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: language-service
 ms.topic: conceptual
-ms.date: 11/02/2021
+ms.date: 01/04/2023
 ms.author: jboback
 ms.custom: language-service-health, ignite-fall-2021
 ---
 
 # Assertion detection
 
-The meaning of medical content is highly affected by modifiers, such as negative or conditional assertions which can have critical implications if misrepresented. Text Analytics for health supports three categories of assertion detection for entities in the text: 
+The meaning of medical content is highly affected by modifiers, such as negative or conditional assertions, which can have critical implications if misrepresented. Text Analytics for health supports three categories of assertion detection for entities in the text: 
 
 * Certainty
 * Conditional
 * Association
 
 ## Assertion output
 
-Text Analytics for health returns assertion modifiers, which are informative attributes assigned to medical concepts that provide deeper understanding of the concepts’ context within the text. These modifiers are divided into three categories, each focusing on a different aspect, and containing a set of mutually exclusive values. Only one value per category is assigned to each entity. The most common value for each category is the Default value. The service’s output response contains only assertion modifiers that are different from the default value.
+Text Analytics for health returns assertion modifiers, which are informative attributes assigned to medical concepts that provide a deeper understanding of the concepts’ context within the text. These modifiers are divided into three categories, each focusing on a different aspect and containing a set of mutually exclusive values. Only one value per category is assigned to each entity. The most common value for each category is the Default value. The service’s output response contains only assertion modifiers that are different from the default value. In other words, if no assertion is returned, the implied assertion is the default value.
 
 **CERTAINTY**  – provides information regarding the presence (present vs. absent) of the concept and how certain the text is regarding its presence (definite vs. possible).
-*	**Positive** [Default]: the concept exists or happened.
+* **Positive** [Default]: the concept exists or has happened.
 * **Negative**: the concept does not exist now or never happened.
 * **Positive_Possible**: the concept likely exists but there is some uncertainty.
 * **Negative_Possible**: the concept’s existence is unlikely but there is some uncertainty.

articles/cognitive-services/language-service/text-analytics-for-health/concepts/health-entity-categories.md

@@ -8,7 +8,7 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: language-service
 ms.topic: conceptual
-ms.date: 11/02/2021
+ms.date: 01/04/2023
 ms.author: jboback
 ms.custom: language-service-health, ignite-fall-2021
 ---
@@ -17,7 +17,7 @@ ms.custom: language-service-health, ignite-fall-2021
 
 Text Analytics for health processes and extracts insights from unstructured medical data. The service detects and surfaces medical concepts, assigns assertions to concepts, infers semantic relations between concepts and links them to common medical ontologies.
 
-Text Analytics for health detects medical concepts in the following categories.
+Text Analytics for health detects medical concepts that fall under the following categories.
 
 ## Anatomy
 
@@ -58,7 +58,7 @@ Text Analytics for health detects medical concepts in the following categories.
 
 ### Entities
 
-**COURSE** - Description of a change in another entity over time, such as condition progression (e.g., improvement, worsening, resolution, remission), a course of treatment or medication (e.g., increase in medication dosage). 
+**COURSE** - Description of a change in another entity over time, such as condition progression (for example: improvement, worsening, resolution, remission), a course of treatment or medication (for example: increase in medication dosage). 
 
 :::image type="content" source="../media/entities/course-entity.png" alt-text="An example of a course entity." lightbox="../media/entities/course-entity.png":::
 
@@ -178,59 +178,7 @@ Text Analytics for health detects medical concepts in the following categories.
 :::image type="content" source="../media/entities/treatment-entities-name.png" alt-text="An example of a treatment name entity." lightbox="../media/entities/treatment-entities-name.png":::
 
 
-## Supported Assertions
-
-Assertion modifiers are divided into three categories, each one focuses on a different aspect.
-Each category contains a set of mutually exclusive values. Only one value per category is assigned to each entity. The most common value for each category is the Default value. The service’s output response contains only assertion modifiers that are different from the default value.
-
-### Certainty  
-
-provides information regarding the presence (present vs. absent) of the concept and how certain the text is regarding its presence (definite vs. possible).
-
-**Positive** (Default): the concept exists or happened.
-
-**Negative**: the concept does not exist now or never happened.
-
-:::image type="content" source="../media/entities/negative-entity.png" alt-text="An example of a negative entity." lightbox="../media/entities/negative-entity.png":::
-
-**Positive_Possible**: the concept likely exists but there is some uncertainty.
-
-:::image type="content" source="../media/entities/positive-possible-entity.png" alt-text="An example of a positive possible entity." lightbox="../media/entities/positive-possible-entity.png" :::
-
-**Negative_Possible**: the concept’s existence is unlikely but there is some uncertainty.
-
-:::image type="content" source="../media/entities/negative-possible-entity.png" alt-text="An example of a negative possible entity." lightbox="../media/entities/negative-possible-entity.png" :::
-
-**Neutral_Possible**: the concept may or may not exist without a tendency to either side.
-
-:::image type="content" source="../media/entities/neutral-possible-entity.png" alt-text="An example of a neutral possible entity." lightbox="../media/entities/neutral-possible-entity.png":::
-
-### Conditionality
-
-provides information regarding whether the existence of a concept depends on certain conditions. 
-
-**None** (Default): the concept is a fact and not hypothetical and does not depend on certain conditions.
-
-**Hypothetical**: the concept may develop or occur in the future.
-
-:::image type="content" source="../media/entities/hypothetical-entity.png" alt-text="An example of a hypothetical entity." lightbox="../media/entities/hypothetical-entity.png":::
-
-**Conditional**: the concept exists or occurs only under certain conditions.
-
-:::image type="content" source="../media/entities/conditional-entity.png" alt-text="An example of a conditional entity." lightbox="../media/entities/conditional-entity.png":::
-
-### Association
-
-describes whether the concept is associated with the subject of the text or someone else.
-
-**Subject** (Default): the concept is associated with the subject of the text, usually the patient.
-
-**Someone_Else**: the concept is associated with someone who is not the subject of the text.
-
-:::image type="content" source="../media/entities/association-entity.png" alt-text="An example of an association entity." lightbox="../media/entities/association-entity.png":::
-
-
 
 ## Next steps
 
-* [NER overview](../../named-entity-recognition/overview.md)
+* [How to call the Text Analytics for health](../how-to/call-api.md)

articles/cognitive-services/language-service/text-analytics-for-health/concepts/relation-extraction.md

@@ -8,19 +8,14 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: language-service
 ms.topic: how-to
-ms.date: 11/02/2021
+ms.date: 01/04/2023
 ms.author: jboback
 ms.custom: language-service-health, ignite-fall-2021
 ---
 
 # Relation extraction
 
-Relation extraction identifies meaningful connections between concepts mentioned in text. For example, a "time of condition" relation is found by associating a condition name with a time or between an abbreviation and the full description.  
-
-
-## Relation extraction output
-
-Text Analytics for health recognizes relations between different concepts, including relations between attribute and entity (for example, direction of body structure, dosage of medication) and between entities (for example, abbreviation detection).
+Text Analytics for health features relation extraction, which is used to  identify meaningful connections between concepts, or entities, mentioned in the text. For example, a "time of condition" relation is found by associating a condition name with a time. Another example is a "dosage of medication" relation, which is found by relating an extracted medication to its extracted dosage. The following example shows how relations are expressed in the JSON output.
 
 > [!NOTE]
 > * Relations referring to CONDITION may refer to either the DIAGNOSIS entity type or the SYMPTOM_OR_SIGN entity type.
@@ -62,7 +57,7 @@ Relation extraction output contains URI references and assigned roles of the ent
 
 ## Recognized relations
 
-The following relations can be returned by the API. 
+The following list presents all the recognized relations by the Text Analytics for health API. 
 
 **ABBREVIATION**
 
@@ -133,3 +128,7 @@ The following relations can be returned by the API.
 **VALUE_OF_EXAMINATION**
 
 **VARIANT_OF_GENE**
+
+## Next steps
+
+* [How to call the Text Analytics for health](../how-to/call-api.md)