Merge pull request #185651 from bleroy/beleroy/debug-session-tweaks

Some tweaks to the debug session documentation

Author: PRMerger18

articles/search/cognitive-search-debug-session.md

@@ -13,14 +13,14 @@ ms.date: 12/30/2021
 
 # Debug Sessions in Azure Cognitive Search
 
-Debug Sessions is a visual editor that works with an existing skillset in the Azure portal, exposing the structure and content of a single enriched document, as its produced by an indexer and skillset, for the duration of the session. Because you are working with a live document, the session is interactive - you can identify errors, modify and invoke skill execution, and validate the results in real time. If your changes resolve the problem, you can commit them to a published skillset to apply the fixes globally.
+Debug Sessions is a visual editor that works with an existing skillset in the Azure portal, exposing the structure and content of a single enriched document, as it's produced by an indexer and skillset, for the duration of the session. Because you are working with a live document, the session is interactive - you can identify errors, modify and invoke skill execution, and validate the results in real time. If your changes resolve the problem, you can commit them to a published skillset to apply the fixes globally.
 
 > [!Important]
 > Debug Sessions is a preview feature provided under [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
 ## How a debug session works
 
-When you start a session, the search service creates a copy of the skillset, indexer, and a search index containing a single document that will be used to test the skillset. All session state will be saved to a container in an Azure Storage account that you provide. 
+When you start a session, the search service creates a copy of the skillset, indexer, and a data source containing a single document that will be used to test the skillset. All session state will be saved to a container in an Azure Storage account that you provide. 
 
 A cached copy of the enriched document and skillset is loaded into the visual editor so that you can inspect the content and metadata of the enriched document, with the ability to check each document node and edit any aspect of the skillset definition. Any changes made within the session are cached. Those changes will not affect the published skillset unless you commit them. Committing changes will overwrite the production skillset.
 
@@ -44,7 +44,7 @@ Skill details includes the following areas:
 
 + **Skill Settings** shows a formatted version of the skill definition.
 + **Skill JSON Editor** shows the raw JSON document of the definition.
-+ **Executions** shows the number of times a skill was executed.
++ **Executions** shows the data corresponding to each time a skill was executed.
 + **Errors and warnings** shows the messages generated upon session start or refresh.
 
 On Executions or Skill Settings, select the **`</>`** symbol to open the [**Expression Evaluator**](#expression-evaluator) used for viewing and editing the expressions of the skills inputs and outputs.

articles/search/cognitive-search-how-to-debug-skillset.md

@@ -15,7 +15,7 @@ ms.date: 12/31/2021
 
 Start a debug session to identify and resolve errors, validate changes, and push changes to a published skillset in your Azure Cognitive Search service.
 
-A debug session is a cached indexer and skillset execution, scoped to a single document, that you can edit and test your changes interactively. If you are unfamiliar with how a debug session works, see [Debug sessions in Azure Cognitive Search](cognitive-search-debug-session.md). To practice a debug workflow with a sample document, see [Tutorial: Debug sessions](cognitive-search-tutorial-debug-sessions.md).
+A debug session is a cached indexer and skillset execution, scoped to a single document, that you can use to edit and test your changes interactively. If you are unfamiliar with how a debug session works, see [Debug sessions in Azure Cognitive Search](cognitive-search-debug-session.md). To practice a debug workflow with a sample document, see [Tutorial: Debug sessions](cognitive-search-tutorial-debug-sessions.md).
 
 > [!Important]
 > Debug sessions is a preview portal feature, provided under [Supplemental Terms of Use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
@@ -64,7 +64,7 @@ As a best practice, resolve problems with inputs before moving on to outputs.
 
 To prove whether a modification resolves an error, follow these steps:
 
-1. Select **Save** in Skill Details to preserve your changes.
+1. Select **Save** in the skill details pane to preserve your changes.
 
 1. Select **Run** in the session window to invoke skillset execution using the modified definition.
 
@@ -103,7 +103,7 @@ The following steps show you how to get information about a skill.
    + **Skill Settings** if you prefer a visual editor
    + **Skill JSON Editor** to edit the JSON document directly
 
-1. Check the [path syntax for referencing nodes](cognitive-search-concept-annotations-syntax.md) in an enrichment tree. Inputs are usually one of the following:
+1. Check the [path syntax for referencing nodes](cognitive-search-concept-annotations-syntax.md) in an enrichment tree. Following are some of the most common input paths:
 
    + `/document/content` for chunks of text. This node is populated from the blob's content property.
    + `/document/merged_content` for chunks of text in skillets that include Text Merge skill.

articles/search/cognitive-search-tutorial-debug-sessions.md

@@ -103,7 +103,7 @@ You will need the [Postman collection](https://github.com/Azure-Samples/azure-se
 
 ## Check results in the portal
 
-The sample code intentionally creates a buggy index as a consequence of problems that occurred during skillset execution. The problem in the index is missing data. 
+The sample code intentionally creates a buggy index as a consequence of problems that occurred during skillset execution. The problem is that the index is missing data. 
 
 1. In Azure portal, on the search service **Overview** page, select the **Indexes** tab. 
 
@@ -113,7 +113,7 @@ The sample code intentionally creates a buggy index as a consequence of problems
 
 1. Select **Search** to run the query. You should see empty values for "organizations" and "locations".
 
-These fields should have been populated through the skillset's [Entity Recognition skill](cognitive-search-skill-entity-recognition-v3.md), used to detect organizations and locations anywhere within the blob's content. In the next exercise, you'll use debug the skillset to determine what went wrong.
+These fields should have been populated through the skillset's [Entity Recognition skill](cognitive-search-skill-entity-recognition-v3.md), used to detect organizations and locations anywhere within the blob's content. In the next exercise, you'll debug the skillset to determine what went wrong.
 
 Another way to investigate errors and warnings is through the Azure portal.