acrolinx fixes

jboback · jboback · commit c5c686894042 · 2025-02-27T17:04:22.000-08:00
diff --git a/articles/ai-services/language-service/question-answering/how-to/migrate-qnamaker-to-question-answering.md b/articles/ai-services/language-service/question-answering/how-to/migrate-qnamaker-to-question-answering.md
@@ -11,7 +11,7 @@ ms.custom: language-service-question-answering
 ---
 # Migrate from QnA Maker to custom question answering 
 
-**Purpose of this document:** This article aims to provide information that can be used to successfully migrate applications that use QnA Maker to custom question answering. Using this article, we hope customers will gain clarity on the following: 
+**Purpose of this document:** This article aims to provide information that can be used to successfully migrate applications that use QnA Maker to custom question answering. Using this article, we hope customers gain clarity on the following: 
 
   - Comparison of features across QnA Maker and custom question answering
   - Pricing
@@ -23,7 +23,7 @@ ms.custom: language-service-question-answering
 **Intended Audience:** Existing QnA Maker customers
 
 > [!IMPORTANT]
-> Custom question Answering, a feature of Azure AI Language was introduced in November 2021 with several new capabilities including enhanced relevance using a deep learning ranker, precise answers, and end-to-end region support. Each custom question answering project is equivalent to a knowledge base in QnA Maker. Resource level settings such as Role-based access control (RBAC) are not migrated to the new resource. These resource level settings would have to be reconfigured for the language resource post migration:
+> Custom question Answering, a feature of Azure AI Language was introduced in November 2021 with several new capabilities including enhanced relevance using a deep learning ranker, precise answers, and end-to-end region support. Each custom question answering project is equivalent to a knowledge base in QnA Maker. Resource level settings such as Role-based access control (RBAC) aren't migrated to the new resource. These resource level settings would have to be reconfigured for the language resource post migration:
 >
 >  - Automatic RBAC to Language project (not resource)
 >  - Automatic enabling of analytics.
@@ -37,15 +37,15 @@ In addition to a new set of features, custom question answering provides many te
 |Feature|QnA Maker|Custom question answering|Details|
 |-------|---------|------------------|-------|
 |State of the art transformer-based models|➖|✔️|Turing based models that enable search of QnA at web scale.|
-|Pre-built capability|➖|✔️|Using this capability one can leverage the power of custom question answering without having to ingest content and manage resources.|
+|Prebuilt capability|➖|✔️|Using this capability one can use the power of custom question answering without having to ingest content and manage resources.|
 |Precise answering|➖|✔️|Custom question answering supports  precise answering with the help of SOTA models.|
 |Smart URL Refresh|➖|✔️|Custom question answering provides a means to refresh ingested content from public sources with a single click.|
 |Q&A over knowledge base (hierarchical extraction)|✔️|✔️| |
 |Active learning|✔️|✔️|Custom question answering has an improved active learning model.|
 |Alternate Questions|✔️|✔️|The improved models in custom question answering reduce the need to add alternate questions.|
 |Synonyms|✔️|✔️| |
 |Metadata|✔️|✔️| |
-|Question Generation (private preview)|➖|✔️|This new feature will allow generation of questions over text.|
+|Question Generation (private preview)|➖|✔️|This new feature allows generation of questions over text.|
 |Support for unstructured documents|➖|✔️|Users can now ingest unstructured documents as input sources and query the content for responses|
 |.NET SDK|✔️|✔️| |
 |API|✔️|✔️| |
@@ -54,7 +54,7 @@ In addition to a new set of features, custom question answering provides many te
 
 ## Pricing
 
-When you're looking at migrating to custom question answering, please consider the following:
+When you're looking at migrating to custom question answering, consider the following:
 
 |Component                      |QnA Maker|Custom question answering|Details                                                                                                  |
 |-------------------------------|---------|------------------|---------------------------------------------------------------------------------------------------------|
@@ -65,7 +65,7 @@ When you're looking at migrating to custom question answering, please consider t
 
 - Users may select a higher tier with higher capacity, which will impact overall price they pay. It doesn’t impact the price on language component of custom question answering.
 
-- “Text Records” in custom question answering features refers to the query submitted by the user to the runtime, and it's a concept common to all features within Language service. Sometimes a query may have more text records when the query length is higher. 
+- "Text Records" in custom question answering features refers to the query submitted by the user to the runtime, and it's a concept common to all features within Language service. Sometimes a query may have more text records when the query length is higher. 
 
 **Example price estimations**
 
@@ -84,7 +84,7 @@ The [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/)
 
 ## Simplified Provisioning and Development Experience
 
-With the Language service, QnA Maker customers now benefit from a single service that provides Text Analytics, LUIS and custom question answering as features of the language resource. The Language service provides:
+With the Language service, QnA Maker customers now benefit from a single service that provides Text Analytics, LUIS, and custom question answering as features of the language resource. The Language service provides:
 
 - One Language resource to access all above capabilities
 - A single pane of authoring experience across capabilities
@@ -93,13 +93,13 @@ With the Language service, QnA Maker customers now benefit from a single service
 
 ## Migration Phases
 
-If you or your organization have applications in development or production that use QnA Maker, you should update them to use custom question answering as soon as possible. See the following links for available APIs, SDKs, Bot SDKs and code samples.
+If you or your organization have applications in development or production that use QnA Maker, you should update them to use custom question answering as soon as possible. See the following links for available APIs, SDKs, Bot SDKs, and code samples.
 
 Following are the broad migration phases to consider:
 
 ![A chart showing the phases of a successful migration](../media/migrate-qnamaker-to-question-answering/migration-phases.png)
 
-Additional links which can help you're given below:
+More links that can help:
 - [Authoring portal](https://language.cognitive.azure.com/home)
 - [API](authoring.md)
 - [SDK](/dotnet/api/microsoft.azure.cognitiveservices.knowledge.qnamaker)
@@ -110,10 +110,10 @@ Additional links which can help you're given below:
 This topic compares two hypothetical scenarios when migrating from QnA Maker to custom question answering. These scenarios can help you to determine the right set of migration steps to execute for the given scenario.
 
 > [!NOTE]
-> An attempt has been made to ensure these scenarios are representative of real customer migrations, however, individual customer scenarios will of course differ. Also, this article doesn't include pricing details. Visit the [pricing](https://azure.microsoft.com/pricing/details/cognitive-services/language-service/) page for more information.
+> An attempt has been made to ensure these scenarios are representative of real customer migrations, however, individual customer scenarios differ. Also, this article doesn't include pricing details. Visit the [pricing](https://azure.microsoft.com/pricing/details/cognitive-services/language-service/) page for more information.
 
 > [!IMPORTANT] 
-> Each custom question answering project is equivalent to a knowledge base in QnA Maker. Resource level settings such as Role-based access control (RBAC) are not migrated to the new resource. These resource level settings would have to be reconfigured for the language resource post migration. You'll also need to [re-enable analytics](analytics.md) for the language resource.
+> Each custom question answering project is equivalent to a knowledge base in QnA Maker. Resource level settings such as Role-based access control (RBAC) aren't migrated to the new resource. These resource level settings would have to be reconfigured for the language resource post migration. You'll also need to [re-enable analytics](analytics.md) for the language resource.
 
 ### Migration scenario 1: No custom authoring portal
 
@@ -139,11 +139,11 @@ Here are some [detailed steps](migrate-qnamaker.md) on migration scenario 1.
 
 ### Migration scenario 2
 
-In this migration scenario, the customer may have created their own authoring frontend leveraging the QnA Maker authoring APIs or QnA Maker SDKs.
+In this migration scenario, the customer may have created their own authoring frontend using the QnA Maker authoring APIs or QnA Maker SDKs.
 
 They should perform these steps required for migration of SDKs:
 
-This [SDK Migration Guide](https://github.com/Azure/azure-sdk-for-net/blob/Azure.AI.Language.QuestionAnswering_1.1.0-beta.1/sdk/cognitivelanguage/Azure.AI.Language.QuestionAnswering/MigrationGuide.md) is intended to assist in the migration to the new custom question answering client library, [Azure.AI.Language.QuestionAnswering](https://www.nuget.org/packages/Azure.AI.Language.QuestionAnswering), from the old one, [Microsoft.Azure.CognitiveServices.Knowledge.QnAMaker](https://www.nuget.org/packages/Microsoft.Azure.CognitiveServices.Knowledge.QnAMaker). It will focus on side-by-side comparisons for similar operations between the two packages.
+This [SDK Migration Guide](https://github.com/Azure/azure-sdk-for-net/blob/Azure.AI.Language.QuestionAnswering_1.1.0-beta.1/sdk/cognitivelanguage/Azure.AI.Language.QuestionAnswering/MigrationGuide.md) is intended to help the migration to the new custom question answering client library, [Azure.AI.Language.QuestionAnswering](https://www.nuget.org/packages/Azure.AI.Language.QuestionAnswering), from the old one, [Microsoft.Azure.CognitiveServices.Knowledge.QnAMaker](https://www.nuget.org/packages/Microsoft.Azure.CognitiveServices.Knowledge.QnAMaker). It will focus on side-by-side comparisons for similar operations between the two packages.
 
 They should perform the steps required for migration of Knowledge bases to the new Project within Language resource.
 
@@ -165,12 +165,12 @@ Here you can find some code samples: [Sample 1](https://github.com/microsoft/Bot
 
 Here are [detailed steps on migration scenario 2](https://github.com/Azure/azure-sdk-for-net/blob/Azure.AI.Language.QuestionAnswering_1.1.0-beta.1/sdk/cognitivelanguage/Azure.AI.Language.QuestionAnswering/MigrationGuide.md)
 
-Learn more about the [pre-built API](../../../QnAMaker/How-To/using-prebuilt-api.md)
+Learn more about the [prebuilt API](../../../QnAMaker/How-To/using-prebuilt-api.md)
 
 Learn more about the [custom question answering Get Answers REST API](/rest/api/questionanswering/question-answering/get-answers)
 
 ## Migration steps
 
-Please note that some of these steps are needed depending on the customers existing architecture. Kindly look at migration phases given above for getting more clarity on which steps are needed by you for migration.
+Note that some of these steps are needed depending on the customers existing architecture. Kindly look at migration phases given above for getting more clarity on which steps are needed by you for migration.
 
 ![A chart showing the steps of a successful migration](../media/migrate-qnamaker-to-question-answering/migration-steps.png)
diff --git a/articles/ai-services/language-service/text-analytics-for-health/how-to/call-api.md b/articles/ai-services/language-service/text-analytics-for-health/how-to/call-api.md
@@ -36,12 +36,12 @@ The Text Analytics for health supports English in addition to multiple languages
 
 ## Submitting data
 
-To send an API request, you will need your Language resource endpoint and key.
+To send an API request, you need your Language resource endpoint and key.
 
 > [!NOTE]
-> You can find the key and endpoint for your Language resource on the Azure portal. They will be located on the resource's **Key and endpoint** page, under **resource management**. 
+> You can find the key and endpoint for your Language resource on the Azure portal. They are located on the resource's **Key and endpoint** page, under **resource management**. 
 
-Analysis is performed upon receipt of the request. If you send a request using the REST API or client library, the results will be returned asynchronously. If you're using the Docker container, they will be returned synchronously.  
+Analysis is performed upon receipt of the request. If you send a request using the REST API or client library, the results are returned asynchronously. If you're using the Docker container, they are returned synchronously.  
 
 [!INCLUDE [asynchronous-result-availability](../../includes/async-result-availability.md)]
 
@@ -58,7 +58,7 @@ Fast Healthcare Interoperability Resources (FHIR) is the health industry communi
 
 ## Getting results from the feature
 
-Depending on your API request, and the data you submit to the Text Analytics for health, you will get:
+Depending on your API request, and the data you submit to the Text Analytics for health, you get:
 
 [!INCLUDE [Text Analytics for health features](../includes/features.md)]
 
