Merge pull request #90130 from jaydeepn/patch-4

Content rectification

Author: jborsecnik

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

@@ -30,7 +30,7 @@ When you move into the development phase of the project, you should consider:
 Typically there are three parameters you need to consider:
 
 * **The throughput you need**:
-    * Question answering is a free feature, and the throughput is currently capped at 10 transactions per second for both management APIs and prediction APIs.
+    * The throughput for question answering is currently capped at 10 transactions per second for both management APIs and prediction APIs.
     * This should also influence your Azure **Cognitive Search** SKU selection, see more details [here](../../../../search/search-sku-tier.md). Additionally, you may need to adjust Cognitive Search [capacity](../../../../search/search-capacity-planning.md) with replicas.
 
 * **Size and the number of knowledge bases**: Choose the appropriate [Azure search SKU](https://azure.microsoft.com/pricing/details/search/) for your scenario. Typically, you decide the number of knowledge bases you need based on number of different subject domains. One subject domain (for a single language) should be in one knowledge base.
@@ -42,7 +42,7 @@ Typically there are three parameters you need to consider:
 
     For example, if your tier has 15 allowed indexes, you can publish 14 knowledge bases of the same language (one index per published knowledge base). The 15th index is used for all the knowledge bases for authoring and testing. If you choose to have knowledge bases in different languages, then you can only publish seven knowledge bases.
 
-* **Number of documents as sources**: question answering is a free feature, and there are no limits to the number of documents you can add as sources. 
+* **Number of documents as sources**: There are no limits to the number of documents you can add as sources in question answering.
 
 The following table gives you some high-level guidelines.
 
@@ -54,7 +54,7 @@ The following table gives you some high-level guidelines.
 
 ## Recommended settings
 
-Custom question answering is a free feature, and the throughput is currently capped at 10 transactions per second for both management APIs and prediction APIs. To target 10 transactions per second for your service, we recommend the S1 (one instance) SKU of Azure Cognitive Search.
+The throughput for question answering is currently capped at 10 transactions per second for both management APIs and prediction APIs. To target 10 transactions per second for your service, we recommend the S1 (one instance) SKU of Azure Cognitive Search.
 
 ## Keys in question answering