acrolinx pass

Author: aahill

articles/ai-services/language-service/concepts/role-based-access-control.md

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: conceptual
-ms.date: 11/21/2024
+ms.date: 06/30/2025
 ms.author: lajanuar
 ---
 
@@ -51,7 +51,7 @@ These custom roles only apply to Language resources.
 
 ### Cognitive Services Language Reader
 
-A user that should only be validating and reviewing the Language apps, typically a tester to ensure the application is performing well before deploying the project. They may want to review the application’s assets to notify the app developers of any changes that need to be made, but do not have direct access to make them. Readers will have access to view the evaluation results.
+A user that should only be validating and reviewing the Language apps, typically a tester to ensure the application is performing well before deploying the project. They might want to review the application’s assets to notify the app developers of any changes that need to be made, but do not have direct access to make them. Readers will have access to view the evaluation results.
 
 
 :::row:::
@@ -85,7 +85,7 @@ A user that should only be validating and reviewing the Language apps, typically
 
 ### Cognitive Services Language Writer
 
-A user that is responsible for building and modifying an application, as a collaborator in a larger team. The collaborator can modify the Language apps in any way, train those changes, and validate/test those changes in the portal. However, this user shouldn’t have access to deploying this application to the runtime, as they may accidentally reflect their changes in production. They also shouldn’t be able to delete the application or alter its prediction resources and endpoint settings (assigning or unassigning prediction resources, making the endpoint public). This restricts this role from altering an application currently being used in production. They may also create new applications under this resource, but with the restrictions mentioned.
+A user that is responsible for building and modifying an application, as a collaborator in a larger team. The collaborator can modify the Language apps in any way, train those changes, and validate/test those changes in the portal. However, this user shouldn’t have access to deploying this application to the runtime, as they might accidentally reflect their changes in production. They also shouldn’t be able to delete the application or alter its prediction resources and endpoint settings (assigning or unassigning prediction resources, making the endpoint public). This restricts this role from altering an application currently being used in production. They might also create new applications under this resource, but with the restrictions mentioned.
 
 :::row:::
     :::column span="":::
@@ -104,7 +104,7 @@ A user that is responsible for building and modifying an application, as a colla
     :::column-end:::
     :::column span="":::
       * All APIs under Language reader
-      * All POST, PUT and PATCH APIs under:
+      * All POST, PUT, and PATCH APIs under:
          * [Language conversational language understanding APIs](/rest/api/language/2023-04-01/conversational-analysis-authoring)
          * [Language text analysis APIs](/rest/api/language/2023-04-01/text-analysis-authoring)
          * [question answering projects](/rest/api/questionanswering/question-answering-projects)

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

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: conceptual
-ms.date: 11/21/2024
+ms.date: 06/30/2025
 ms.author: lajanuar
 ---
 

articles/ai-services/language-service/custom-text-classification/tutorials/triage-email.md

@@ -7,11 +7,11 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: tutorial
-ms.date: 11/21/2024
+ms.date: 06/30/2025
 ms.author: lajanuar
 ---
 
-# Tutorial: Triage incoming emails with power automate
+# Tutorial: Triage incoming emails with Power Automate
 
 In this tutorial you will categorize and triage incoming email using custom text classification. Using this [Power Automate](/power-automate/getting-started) flow, when a new email is received, its contents will have a classification applied, and depending on the result, a message will be sent to a designated channel on [Microsoft Teams](https://www.microsoft.com/microsoft-teams).
 
@@ -27,7 +27,7 @@ In this tutorial you will categorize and triage incoming email using custom text
 
 ## Create a Power Automate flow
 
-1. [Sign in to power automate](https://make.powerautomate.com/)
+1. [Sign in to Power Automate](https://make.powerautomate.com/)
 
 2. From the left side menu, select **My flows** and create a **Automated cloud flow**
 

articles/ai-services/language-service/language-detection/language-support.md

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: conceptual
-ms.date: 11/21/2024
+ms.date: 06/30/2025
 ms.author: lajanuar
 ms.custom: language-service-language-detection, ignite-2024
 ---

articles/ai-services/language-service/orchestration-workflow/quickstart.md

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: quickstart
-ms.date: 11/21/2024
+ms.date: 06/30/2025
 ms.author: lajanuar
 ms.custom: language-service-clu, mode-other
 zone_pivot_groups: usage-custom-language-features

articles/ai-services/language-service/question-answering/concepts/azure-resources.md

@@ -5,7 +5,7 @@ ms.service: azure-ai-language
 ms.topic: conceptual
 author: laujan
 ms.author: lajanuar
-ms.date: 11/21/2024
+ms.date: 06/30/2025
 ms.custom: language-service-question-answering
 ---
 
@@ -34,7 +34,7 @@ Typically there are three parameters you need to consider:
 
     * The throughput for custom question answering is currently capped at 10 text records per second for both management APIs and prediction APIs.
 
-    * This should also influence your **Azure AI Search** SKU selection, see more details [here](/azure/search/search-sku-tier). Additionally, you might need to adjust Azure AI Search [capacity](/azure/search/search-capacity-planning) with replicas.
+    * This should also influence your **Azure AI Search** selection, see more details [here](/azure/search/search-sku-tier). Additionally, you might need to adjust Azure AI Search [capacity](/azure/search/search-capacity-planning) with replicas.
 
 * **Size and the number of projects**: Choose the appropriate [Azure search SKU](https://azure.microsoft.com/pricing/details/search/) for your scenario. Typically, you decide the number of projects you need based on number of different subject domains. One subject domain (for a single language) should be in one project.
 
@@ -58,7 +58,7 @@ The following table gives you some high-level guidelines.
 ## Recommended settings
 
 
-The throughput for custom question answering is currently capped at 10 text records per second for both management APIs and prediction APIs. To target 10 text records per second for your service, we recommend the S1 (one instance) SKU of Azure AI Search.
+The throughput for custom question answering is currently capped at 10 text records per second for both management APIs and prediction APIs. To target 10 text records per second for your service, we recommend the S1 (one instance) tier of Azure AI Search.
 
 
 ## Keys in custom question answering

articles/ai-services/language-service/question-answering/how-to/chit-chat.md

@@ -8,7 +8,7 @@ author: laujan
 ms.author: lajanuar
 ms.service: azure-ai-language
 ms.topic: how-to
-ms.date: 11/21/2024
+ms.date: 06/30/2025
 ms.custom: language-service-question-answering
 ---
 

articles/ai-services/language-service/sentiment-opinion-mining/how-to/use-containers.md

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: how-to
-ms.date: 11/21/2024
+ms.date: 06/30/2025
 ms.author: lajanuar
 ms.custom: language-service-sentiment-opinion-mining
 keywords: on-premises, Docker, container, sentiment analysis, natural language processing
@@ -130,7 +130,7 @@ In this article, you learned concepts and workflow for downloading, installing,
 * You must specify billing information when instantiating a container.
 
 > [!IMPORTANT]
-> Azure AI containers are not licensed to run without being connected to Azure for metering. Customers need to enable the containers to communicate billing information with the metering service at all times. Azure AI containers do not send customer data (e.g. text that is being analyzed) to Microsoft.
+> Azure AI containers are not licensed to run without being connected to Azure for metering. Customers need to enable the containers to communicate billing information with the metering service at all times. Azure AI containers do not send customer data (for example, text that is being analyzed) to Microsoft.
 
 ## Next steps