Merge pull request #171518 from HeidiSteen/heidist-quickfix

[azure search] K-store edits to table sections

Author: PRMerger13

articles/search/knowledge-store-create-portal.md

@@ -147,16 +147,28 @@ In this wizard step, configure an indexer that will pull together the data sourc
 
 1. For **Schedule**, keep the default **Once**.
 
-1. Click **Submit** to run the indexer. Data extraction, indexing, application of cognitive skills all happen in this step.
+1. Select **Submit** to run the indexer. Data extraction, indexing, application of cognitive skills all happen in this step.
 
-## Check indexer status
+## Check status
 
 In the **Overview** page, open the **Indexers** tab in the middle of the page, and then select **hotels-reviews-ixr**. Within a minute or two, status should progress from "In progress" to "Success" with zero errors and warnings.
 
-## Check tables in Azure Storage
+## Check tables in Storage Explorer
 
 In the Azure portal, switch to your Azure Storage account and use **Storage Explorer** to view the new tables. You should see three tables, one for each projection that was offered in the "Save enrichments" section of the "Add enrichments" page.
 
++ The document table contains all of the first-level nodes of a document's enrichment tree.
+
++ A pages table (or sentences table) is created if you specify "pages" or "sentences" level of granularity. Skills that execute at the pages or sentence level will have output projected to this table.
+
++ Skills that output collections (arrays), such as key phrases and entities, will have output in a standalone table.
+
+All tables within the same projection group contain cross-reference information to support table relationships in other tools and apps.
+
+In this quickstart, your table should look similar to the following screenshot:
+
+   :::image type="content" source="media/knowledge-store-create-portal/azure-table-hotel-reviews.png" alt-text="Screenshot of the generated tables in Storage Explorer" border="true":::
+
 Each table is generated with the IDs necessary for cross-linking the tables in queries. When you open a table, scroll past these fields to view the content fields added by the pipeline.
 
 | Table | Description |
@@ -165,10 +177,6 @@ Each table is generated with the IDs necessary for cross-linking the tables in q
 | hotelReviewssPages | Contains enriched fields created by the skillset, such as sentiment label and translated text. |
 | hotelReviewssKeyPhrases | Contains a long list of just the key phrases. |
 
-Your table should look similar to the following screenshot:
-
-   :::image type="content" source="media/knowledge-store-create-portal/azure-table-hotel-reviews.png" alt-text="Screenshot of the generated tables in Storage Explorer" border="true":::
-
 ## Clean up
 
 When you're working in your own subscription, it's a good idea at the end of a project to identify whether you still need the resources you created. Resources left running can cost you money. You can delete resources individually or delete the resource group to delete the entire set of resources.

articles/search/knowledge-store-create-rest.md

@@ -104,7 +104,7 @@ The variables you set up earlier are used in the headers and URL. The following
 > All of the requests in the collection set `api-key` and `Content-type` headers, which are required. If Postman recognizes a variable, the variable appears in orange text, as with `{{admin-key}}` in the preceding screenshot. If the variable is misspelled, it appears in red text.
 >
 
-## Create an Azure Cognitive Search index
+## Create an index
 
 Use the [Create Index (REST API)](/rest/api/searchservice/create-index) to create a search index on the search service. A search index is unrelated to a knowledge store, but the indexer requires that you create one. The search index will contain the same content as the knowledge store. If you want an alternative approach for exploring your content, you can query this index by sending query requests to your search service. 
 
@@ -137,7 +137,7 @@ You should see the status `201 - Created`. If you see a different status, in the
 
 At this point, the index is created but not loaded. Importing documents occurs later when you run the indexer. 
 
-## Create the data source
+## Create a data source
 
 Next, connect Azure Cognitive Search to the hotel data you stored in Blob storage. To create the data source, send a [Create Data Source](/rest/api/searchservice/create-data-source) POST request to `https://{{search-service-name}}.search.windows.net/datasources?api-version={{api-version}}`. 
 
@@ -155,7 +155,7 @@ In Postman, go to the **Create Datasource** request, and then to the **Body** pa
 
 Select **Send** to issue the POST request. 
 
-## Create the skillset 
+## Create a skillset 
 
 The next step creates the skillset, which specifies both the enhancements to be applied and the knowledge store where the results will be stored. This request sends a [Create Skillset](/rest/api/searchservice/create-skillset) PUT request to `https://{{search-service-name}}.search.windows.net/skillsets/{{skillset-name}}?api-version={{api-version}}`.
 
@@ -320,7 +320,7 @@ To generate the skillset, select the **Send** button in Postman to PUT the reque
 }
 ```
 
-## Create the indexer
+## Create an indexer
 
 The final step is the [Create Indexer](/rest/api/searchservice/create-indexer) request. The indexer reads the data and activates the skillset. The definition of the indexer refers to several other resources that you already created: the datasource, the index, and the skillset. 
 
@@ -361,21 +361,21 @@ Select **Send** in Postman to create and run the indexer. Data import, skillset
 }
 ```
 
-## Check indexer status
+## Check status
 
 After you send each request, the search service should respond with a 201 success message. If you get errors, re-check your variables and make sure that the search service has room for the new index, indexer, data source, and skillset (the free tier is limited to three of each).
 
 In the Azure portal, go to the Azure Cognitive Search service's **Overview** page. Select the **Indexers** tab, and then select **hotels-reviews-ixr**. Within a minute or two, status should progress from "In progress" to "Success" with zero errors and warnings.
 
-## Check tables in Azure Storage
+## Check tables in Storage Explorer
 
-In the Azure portal, switch to your Azure Storage account and use **Storage Explorer** to view the new tables. You should see six tables.
+In the Azure portal, switch to your Azure Storage account and use **Storage Explorer** to view the new tables. You should see six tables, one for each projection defined in the skillset.
 
 Each table is generated with the IDs necessary for cross-linking the tables in queries. When you open a table, scroll past these fields to view the content fields added by the pipeline.
 
    :::image type="content" source="media/knowledge-store-create-rest/knowledge-store-tables.png" alt-text="Screenshot of the knowledge store tables in Storage Explorer" border="true":::
 
-In this walkthrough, the knowledge store is composed of a various tables showing different ways of shaping and structuring a table. The first three rely on a Shaper skill to provide the columns and data values.
+In this walkthrough, the knowledge store is composed of a various tables showing different ways of shaping and structuring a table. The first set of three demonstrate tables that use output from a Shaper skill to determine the columns and rows. The second set demonstrates inline shaping commands, embedded within the projection itself. You can use either approach to achieve the same outcome.
 
 | Table | Description |
 |-------|-------------|