Merge pull request #76116 from v-albemi/two-search-articles

Edit pass: Two search articles

Author: ShawnJackson

articles/search/cognitive-search-attach-cognitive-services.md

@@ -1,6 +1,6 @@
 ---
 title: Attach a Cognitive Services resource with a skillset - Azure Search
-description: Instructions for attaching a Cognitive Services All-in-One subscription to a cognitive enrichment pipeline in Azure Search.
+description: Instructions for attaching a Cognitive Services all-in-one subscription to a cognitive enrichment pipeline in Azure Search.
 manager: cgronlun
 author: LuisCabrer
 services: search
@@ -13,84 +13,84 @@ ms.custom: seodec2018
 ---
 # Attach a Cognitive Services resource with a skillset in Azure Search 
 
-AI algorithms drive the [cognitive indexing pipelines](cognitive-search-concept-intro.md) used for processing unstructured data in Azure Search. These algorithms are based on [Cognitive Services resources](https://azure.microsoft.com/services/cognitive-services/), including [Computer Vision](https://azure.microsoft.com/services/cognitive-services/computer-vision/) for image analysis and optical character recognition (OCR), and [Text Analytics](https://azure.microsoft.com/services/cognitive-services/text-analytics/) for entity recognition, key phrase extraction, and other enrichments.
+AI algorithms drive the [cognitive indexing pipelines](cognitive-search-concept-intro.md) used for processing unstructured data in Azure Search. These algorithms are based on [Azure Cognitive Services resources](https://azure.microsoft.com/services/cognitive-services/), including [Computer Vision](https://azure.microsoft.com/services/cognitive-services/computer-vision/) for image analysis and optical character recognition (OCR) and [Text Analytics](https://azure.microsoft.com/services/cognitive-services/text-analytics/) for entity recognition, key phrase extraction, and other enrichments.
 
-You can enrich a limited number of documents for free, or attach a billable Cognitive Services resource for larger and more frequent workloads. In this article, learn how to associate a Cognitive Services resource with your cognitive skillset to enrich data during [Azure Search indexing](search-what-is-an-index.md).
+You can enrich a limited number of documents for free, or you can attach a billable Cognitive Services resource for larger and more frequent workloads. In this article, you'll learn how to associate a Cognitive Services resource with your cognitive skillset to enrich data during [Azure Search indexing](search-what-is-an-index.md).
 
-If your pipeline consists of skills unrelated to Cognitive Services APIs, you should still attach a Cognitive Services resource. Doing so overrides the **Free** resource that limits you to a small quantity of enrichments per day. There is no charge for skills that are not bound to Cognitive Services APIs. These skills include: [custom skills](cognitive-search-create-custom-skill-example.md), [text merger](cognitive-search-skill-textmerger.md), [text splitter](cognitive-search-skill-textsplit.md), and [shaper](cognitive-search-skill-shaper.md).
+Even if your pipeline consists of skills that aren't related to Cognitive Services APIs, you should still attach a Cognitive Services resource. Doing so overrides the Free resource that limits you to a small number of enrichments per day. You won't be charged for skills that aren't bound to Cognitive Services APIs. These skills include [custom skills](cognitive-search-create-custom-skill-example.md), [text merger](cognitive-search-skill-textmerger.md), [text splitter](cognitive-search-skill-textsplit.md), and [shaper](cognitive-search-skill-shaper.md).
 
 > [!NOTE]
-> As you expand scope by increasing the frequency of processing, adding more documents, or adding more AI algorithms, you will need to attach a billable Cognitive Services resource. Charges accrue when calling APIs in Cognitive Services, and for image extraction as part of the document-cracking stage in Azure Search. There are no charges for text extraction from documents.
+> As you expand scope by increasing the frequency of processing, adding more documents, or adding more AI algorithms, you'll need to attach a billable Cognitive Services resource. You'll be charged for calling APIs in Cognitive Services and for image extraction as part of the document-cracking stage in Azure Search. You won't be charged for text extraction from documents.
 >
-> Execution of built-in skills is charged at the existing [Cognitive Services pay-as-you go price](https://azure.microsoft.com/pricing/details/cognitive-services/). Image extraction pricing is described on the [Azure Search pricing page](https://go.microsoft.com/fwlink/?linkid=2042400).
+> Execution of built-in skills is billed at the [Cognitive Services pay-as-you go price](https://azure.microsoft.com/pricing/details/cognitive-services/). For information about image extraction pricing, see the [Azure Search pricing page](https://go.microsoft.com/fwlink/?linkid=2042400).
 
 ## Use Free resources
 
-You can use a limited, free processing option to complete the cognitive search tutorial and quickstart exercises. 
+You can use a limited, free processing option to complete the cognitive search tutorial and quickstart exercises.
 
-**Free (Limited Enrichments)** are restricted to 20 documents per day, per subscription.
+Free (Limited enrichments) resources are restricted to 20 documents per day, per subscription.
 
-1. Open the **Import data** wizard.
+1. Open the Import data wizard:
 
-   ![Import data command](media/search-get-started-portal/import-data-cmd2.png "Import data command")
+   ![Open the Import data wizard](media/search-get-started-portal/import-data-cmd2.png "Open the Import data wizard")
 
-1. Choose a data source and continue to **Add cognitive search (optional)**. For a step-by-step walkthrough of this wizard, see [Import, index, and query using portal tools](search-get-started-portal.md).
+1. Choose a data source and continue to **Add cognitive search (Optional)**. For a step-by-step walkthrough of this wizard, see [Import, index, and query by using portal tools](search-get-started-portal.md).
 
-1. Expand **Attach Cognitive Services** and select **Free (Limited Enrichments)**.
+1. Expand **Attach Cognitive Services** and then select **Free (Limited enrichments)**:
 
-   ![Expanded Attach Cognitive Services section](./media/cognitive-search-attach-cognitive-services/attach1.png "Expanded Attach Cognitive Services")
+   ![Expanded Attach Cognitive Services section](./media/cognitive-search-attach-cognitive-services/attach1.png "Expanded Attach Cognitive Services section")
 
-Continue to the next step, **Add enrichments**. For a description of skills available in the portal, see ["Step 2: Add cognitive skill"](cognitive-search-quickstart-blob.md#create-the-enrichment-pipeline) in the cognitive search quickstart.
+1. Continue to the next step, **Add Enrichments**. For a description of skills available in the portal, see [Step 2: Add cognitive skills](cognitive-search-quickstart-blob.md#create-the-enrichment-pipeline) in the cognitive search quickstart.
 
 ## Use billable resources
 
-For workloads numbering more than 20 enrichments daily, you need to attach a billable Cognitive Services resource. 
+For workloads that create more than 20 enrichments per day, you need to attach a billable Cognitive Services resource.
 
-You are only charged for skills that call the Cognitive Services APIs. Non-API-based skills like [custom skills](cognitive-search-create-custom-skill-example.md), [text merger](cognitive-search-skill-textmerger.md), [text splitter](cognitive-search-skill-textsplit.md), and [shaper](cognitive-search-skill-shaper.md) skills are not billed.
+You're charged only for skills that call the Cognitive Services APIs. You're not billed for [custom skills](cognitive-search-create-custom-skill-example.md),  or skills like [text merger](cognitive-search-skill-textmerger.md), [text splitter](cognitive-search-skill-textsplit.md), and [shaper](cognitive-search-skill-shaper.md), which aren't API-based.
 
-1. Open the **Import data** wizard, choose a data source, and continue to **Add cognitive search (optional)**. 
+1. Open the Import data wizard, choose a data source, and continue to **Add cognitive search (Optional)**.
 
-1. Expand **Attach Cognitive Services** and then select **Create new Cognitive Services resource**. A new tab opens so that you can create the resource. 
+1. Expand **Attach Cognitive Services** and then select **Create new Cognitive Services resource**. A new tab opens so that you can create the resource:
 
    ![Create a Cognitive Services resource](./media/cognitive-search-attach-cognitive-services/cog-services-create.png "Create a Cognitive Services resource")
 
-1. In Location, choose the same region as Azure Search. This is required for performance reasons, but it also voids outbound bandwidth charges across regions.
+1. In the **Location** list, select the region where your Azure Search service is located. You need to use this region for performance reasons. Using this region also voids outbound bandwidth charges across regions.
 
-1. In Pricing tier, choose **S0** to get the all-in-one collection of Cognitive Services features, including the Vision and Language features that back the predefined skills used by Azure Search. 
+1. In the **Pricing tier** list, select **S0** to get the all-in-one collection of Cognitive Services features, including the Vision and Language features that back the predefined skills used by Azure Search.
 
    For the S0 tier, you can find rates for specific workloads on the [Cognitive Services pricing page](https://azure.microsoft.com/pricing/details/cognitive-services/).
 
-   + In **Select Offer**, make sure that *Cognitive Services* is selected.
-   + Under Language features, the rates for *Text Analytics Standard* apply to AI indexing. 
-   + Under Vision features, the rates for *Computer Vision S1* are applied.
+   + In the **Select Offer** list, make sure **Cognitive Services** is selected.
+   + Under **Language** features, the rates for **Text Analytics Standard** apply to AI indexing.
+   + Under **Vision** features, the rates for **Computer Vision S1** apply.
 
-1. Click **Create** to provision the new Cognitive Services resource. 
+1. Select **Create** to provision the new Cognitive Services resource.
 
-1. Return to the previous tab containing the **Import data** wizard. Click **Refresh** to show the Cognitive Services resource, and then select the resource.
+1. Return to the previous tab, which contains the Import data wizard. Select **Refresh** to show the Cognitive Services resource, and then select the resource:
 
-   ![Selected Cognitive Services resource](./media/cognitive-search-attach-cognitive-services/attach2.png "Selected Cognitive Service Resource")
+   ![Select the Cognitive Services resource](./media/cognitive-search-attach-cognitive-services/attach2.png "Select the Cognitive Services resource")
 
-1. Expand the **Add Enrichments** section to select the specific cognitive skills that you want to run over your data, and proceed with the rest of the flow. For a description of skills available in the portal, see ["Step 2: Add cognitive skill"](cognitive-search-quickstart-blob.md#create-the-enrichment-pipeline) in the cognitive search quickstart.
+1. Expand the **Add Enrichments** section to select the specific cognitive skills that you want to run on your data. Complete the rest of the wizard. For a description of skills available in the portal, see [Step 2: Add cognitive skills](cognitive-search-quickstart-blob.md#create-the-enrichment-pipeline) in the cognitive search quickstart.
 
 ## Attach an existing skillset to a Cognitive Services resource
 
 If you have an existing skillset, you can attach it to a new or different Cognitive Services resource.
 
-1. On the **Service overview** page, click **Skillsets**.
+1. On the **Service overview** page, select **Skillsets**:
 
    ![Skillsets tab](./media/cognitive-search-attach-cognitive-services/attach-existing1.png "Skillsets tab")
 
-1. Click the name of skillset, and then select an existing resource or create a new one. Click **OK** to confirm your changes. 
+1. Select the name of the skillset, and then select an existing resource or create a new one. Select **OK** to confirm your changes.
 
    ![Skillset resource list](./media/cognitive-search-attach-cognitive-services/attach-existing2.png "Skillset resource list")
 
-Recall that **Free (Limited Enrichments)** is limited to 20 documents daily, and that **Create new Cognitive Services resource** is used to provision a new billable resource. If you create a new resource, select **Refresh** to refresh the list of Cognitive Services resources, and then select the resource.
+   Remember that the **Free (Limited enrichments)** option limits you to 20 documents daily, and that you can use **Create new Cognitive Services resource** to provision a new billable resource. If you create a new resource, select **Refresh** to refresh the list of Cognitive Services resources, and then select the resource.
 
 ## Attach Cognitive Services programmatically
 
-When you're defining the skillset programmatically, add a `cognitiveServices` section to the skillset. In the section, include the key of the Cognitive Services resource that you want to associate with the skillset. Recall that the resource must be in the same region as Azure Search. Also include `@odata.type`, and set it to `#Microsoft.Azure.Search.CognitiveServicesByKey`. 
+When you're defining the skillset programmatically, add a `cognitiveServices` section to the skillset. In that section, include the key of the Cognitive Services resource that you want to associate with the skillset. Remember that the resource must be in the same region as your Azure Search resource. Also include `@odata.type`, and set it to `#Microsoft.Azure.Search.CognitiveServicesByKey`.
 
-The following example shows this pattern. Notice the cognitiveServices section at the bottom of the definition
+The following example shows this pattern. Notice the `cognitiveServices` section at the end of the definition.
 
 ```http
 PUT https://[servicename].search.windows.net/skillsets/[skillset name]?api-version=2019-05-06
@@ -128,24 +128,24 @@ Content-Type: application/json
 
 ## Example: Estimate costs
 
-To estimate costs associated with cognitive search indexing, start with an idea of what an average document looks like so that you can run some numbers. For example, for estimation purposes, you might approximate:
+To estimate the costs associated with cognitive search indexing, start with an idea of what an average document looks like so you can run some numbers. For example, you might approximate:
 
-+ 1000 PDFs
-+ Six pages each
-+ One image per page (6000 images)
-+ 3000 characters per page
++ 1,000 PDFs.
++ Six pages each.
++ One image per page (6,000 images).
++ 3,000 characters per page.
 
-Assume a pipeline consisting of document cracking of each PDF with image and text extraction, optical character recognition (OCR) of images, and entity recognition of organizations. 
+Assume a pipeline that consists of document cracking of each PDF, image and text extraction, optical character recognition (OCR) of images, and entity recognition of organizations.
 
-In this exercise, we're using the most expensive price per transaction. Actual costs could be lower due to graduated pricing. See [Cognitive Services pricing](https://azure.microsoft.com/pricing/details/cognitive-services).
+The prices shown in this article are hypothetical. They're used to illustrate the estimation process. Your costs could be lower. For the actual prices of transactions, see See [Cognitive Services pricing](https://azure.microsoft.com/pricing/details/cognitive-services).
 
-1. For document cracking with text and image content, text extraction is currently free. For 6000 images, assume $1 for every 1,000 images extracted, costing $6.00 for this step.
+1. For document cracking with text and image content, text extraction is currently free. For 6,000 images, assume $1 for every 1,000 images extracted. That's a cost of $6.00 for this step.
 
 2. For OCR of 6,000 images in English, the OCR cognitive skill uses the best algorithm (DescribeText). Assuming a cost of $2.50 per 1,000 images to be analyzed, you would pay $15.00 for this step.
 
-3. For entity extraction, you would have a total of 3 text records per page. Each record is 1,000 characters. Three text records per page * 6,000 pages = 18,000 text records. Assuming $2.00 per 1,000 text records, this step would cost $36.00.
+3. For entity extraction, you'd have a total of three text records per page. Each record is 1,000 characters. Three text records per page multiplied by 6,000 pages equals 18,000 text records. Assuming $2.00 per 1,000 text records, this step would cost $36.00.
 
-Putting it all together, you would pay about $57.00 to ingest 1,000 PDF documents of this nature with the described skillset. 
+Putting it all together, you'd pay about $57.00 to ingest 1,000 PDF documents of this type with the described skillset.
 
 ## Next steps
 + [Azure Search pricing page](https://azure.microsoft.com/pricing/details/search/)