updated with Heidi's comments

tchristiani · tchristiani · commit a0a04622f040 · 2020-05-18T15:44:09.000-07:00
diff --git a/articles/search/cognitive-search-debug-session.md b/articles/search/cognitive-search-debug-session.md
@@ -39,51 +39,53 @@ To start a debug session you must have an existing AI enrichment pipeline includ
 
 The debug session begins by executing the skillset on the selected document. The debug session will record additional metadata associated with each operation in the skillset. The metadata created by the pipeline's skill executions, informs the following set of features that are then used to help identify and fix issues with the skillset.
 
-## AI enrichments
+## AI Enrichments
 
 As skills execute a tree of enrichments, representing the document, grows. Using a tree to visualize the outputs of skills or enrichments provides a comprehensive look at all the enrichments performed. You can look across the entire document and inspect each node of the enrichment tree. This perspective makes it easier to shape objects. This format also provides visual cues to the type, path, and contents of each node in the tree.
 
-## Skill graph
+## Skill Graph
 
-The skill graph view provides a hierarchical, visual representation of the skillset. The graph is a top to bottom representation of the order in which the skills are executed. Skills that are dependent upon the output of other skills will be shown lower in the graph. Skills at the same level in the hierarchy can execute in parallel. 
+The **Skill Graph** view provides a hierarchical, visual representation of the skillset. The graph is a top to bottom representation of the order in which the skills are executed. Skills that are dependent upon the output of other skills will be shown lower in the graph. Skills at the same level in the hierarchy can execute in parallel. 
 
-Selecting a skill in the graph will highlight the skills connected to it, the node(s) that create its inputs and the node(s) that accept its outputs. Each skill node displays its type, errors or warnings, and execution counts. The skills graph is where you will select which skill to debug or enhance.
+Selecting a skill in the graph will highlight the skills connected to it, the nodes that create its inputs and the nodes that accept its outputs. Each skill node displays its type, errors or warnings, and execution counts. The **Skill Graph** is where you will select which skill to debug or enhance. When you select a skill its details will be displayed in the skill details pane to the right of the graph.
 
 > [!div class="mx-imgBorder"]
-> ![Skill graph](media/cognitive-search-debug/skills-graph.png)
+> ![Skill Graph](media/cognitive-search-debug/skills-graph.png)
 
 ## Skill details
 
-The skill details pane displays a set of areas for working with a specific skill. You can review and edit the details of the skill's settings. The skill's JSON definition is provided. The details of the skill's execution and the errors and warnings are also displayed. The Skill Settings & Skill JSON Editor allow for direct edits to the skill. The Expression Evaluator </> opens a window for viewing and editing the expressions of the skills inputs and outputs.
+The skill details pane displays a set of areas for working with a specific skill, when that skill is highlighted in the **Skill Graph**. You can review and edit the details of the skill's settings. The skill's JSON definition is provided. The details of the skill's execution and the errors and warnings are also displayed. The **Skill Settings** tab & **Skill JSON Editor** allow for direct edits to the skill. The [`</>`](##expression-evaluator) opens a window for viewing and editing the expressions of the skills inputs and outputs.
 
-Nested input controls in the skill settings window can be used to build complex shapes for projections, output field mappings for a complex type field, or an input to a skill. When used with the expression evaluator, nested inputs provide an easy test and validate expression builder.
+Nested input controls in the skill settings window can be used to build complex shapes for projections, output field mappings for a complex type field, or an input to a skill. When used with the **Expression evaluator**, nested inputs provide an easy test and validate expression builder.
 
 ## Skill execution history
 
-A skill can execute multiple times in a skillset for a single document. For example, the OCR skill will execute once for each image extracted from each document. The skill execution history provides a deeper look into each invocation of the skill. 
+A skill can execute multiple times in a skillset for a single document. For example, the OCR skill will execute once for each image extracted from each document. In the skill details pane  the **Executions** tab displays the skill's execution history providing a deeper look into each invocation of the skill. 
 
 The execution history enables tracking a specific enrichment back to the skill that generated it. Clicking on a skill input navigates to the skill that generated that input. This allows identification of the root cause of a problem that may manifest in a downstream skill. 
 
 When a potential issue is identified, the execution history displays links to the skills that generated the specific inputs, providing a stack-trace like feature. Clicking on the skill associated with an input, navigates to the skill to fix any bugs or continue to trace the specific issue.
 
 When building a custom skill or debugging an error with a custom skill, there is the option to generate a request for a skill invocation in the execution history.
 
-## Enriched data structure
+## Enriched Data Structure
 
-The enriched data structure pane shows the document's enrichments through the skillset, detailing the context for each enrichment and the originating skill. The expression evaluator `</>` can also be used to view the contents for each enrichment.
+The **Enriched Data Structure** pane shows the document's enrichments through the skillset, detailing the context for each enrichment and the originating skill. The **Expression evaluator** can also be used to view the contents for each enrichment.
 
 > [!div class="mx-imgBorder"]
-> ![Enriched data structure](media/cognitive-search-debug/enriched-data-structure-display.png)
+> ![Enriched Data Structure](media/cognitive-search-debug/enriched-data-structure-display.png)
 
 ## Expression evaluator
 
-Debug sessions have a few features that are available across the different components. The expression evaluator `</>` gives a quick peek into the value of any path. It allows for editing the path and testing the results before updating any of the inputs or context for a skill or projection.
+**Expression evaluator** gives a quick peek into the value of any path. It allows for editing the path and testing the results before updating any of the inputs or context for a skill or projection.
 
 ## Errors/Warnings
 
 This window displays all of the errors and warnings the skillset produces as it is executed against the document in the debug session.
 
 ## Next steps
 
+Now that you understand the elements of Debug sessions try the tutorial for a hands-on experience.
+
 > [!div class="nextstepaction"]
 > [Explore Debug sessions feature tutorial](https://docs.microsoft.com/azure/search/cognitive-search-tutorial-debug-sessions)
diff --git a/articles/search/cognitive-search-tutorial-debug-sessions.md b/articles/search/cognitive-search-tutorial-debug-sessions.md
@@ -26,28 +26,29 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
 
 ## Prerequisites
 
-1. An Azure subscription. Create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) or use your current subscription.
-1. An Azure Cognitive Search service instance.
-1. An Azure Storage account.
-1. [Postman desktop app](https://www.getpostman.com/).
+> [!div class="checklist"]
+> * An Azure subscription. Create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) or use your current subscription
+> * An Azure Cognitive Search service instance
+> * An Azure Storage account
+> * [Postman desktop app](https://www.getpostman.com/)
 
 ## Create services and load data
 
 This tutorial uses Azure Cognitive Search and Azure Storage services.
 
-1. [Download sample data](https://github.com/Azure-Samples/azure-search-knowledge-mining/blob/master/workshops/data/clinical-trials-small.zip) consisting of 107 files. Unzip the files.
+* [Download sample data](https://github.com/Azure-Samples/azure-search-sample-data/tree/master/clinical-trials-pdf-19) consisting of 19 files.
 
-1. [Create an Azure storage account](https://docs.microsoft.com/azure/storage/common/storage-quickstart-create-account?tabs=azure-portal) or [find an existing account](https://ms.portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Storage%2storageAccounts/). 
+* [Create an Azure storage account](https://docs.microsoft.com/azure/storage/common/storage-quickstart-create-account?tabs=azure-portal) or [find an existing account](https://ms.portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Storage%2storageAccounts/). 
 
    Choose the same region as Azure Cognitive Search to avoid bandwidth charges.
    
    Choose the StorageV2 (general purpose V2) account type.
 
-1. Open the storage services pages and create a container. Best practice is to specify the access level "private". Name your container `clinicaltrialdataset`.
+* Open the storage services pages and create a container. Best practice is to specify the access level "private". Name your container `clinicaltrialdataset`.
 
-1. In container, click **Upload** to upload the sample files you downloaded and unzipped in the first step.
+* In container, click **Upload** to upload the sample files you downloaded and unzipped in the first step.
 
-1. [Create an Azure Cognitive Search service](search-create-service-portal.md) or [find an existing service](https://ms.portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Search%2FsearchServices). You can use a free service for this quickstart.
+* [Create an Azure Cognitive Search service](search-create-service-portal.md) or [find an existing service](https://ms.portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Search%2FsearchServices). You can use a free service for this quickstart.
 
 ## Get a key and URL
 
@@ -66,7 +67,7 @@ All requests require an api-key on every request sent to your service. Having a
 In this section, Postman and a provided collection are used to create the search service's data source, skillset, index, and indexer.
 
 1. If you do not have Postman, you can [download the Postman desktop app here](https://www.getpostman.com/).
-1. [Download the Postman collection](https://github.com/Azure-Samples/azure-search-postman-samples/tree/master/Debug-sessions)
+1. [Download the Debug Sessions Postman collection](https://github.com/Azure-Samples/azure-search-postman-samples/tree/master/Debug-sessions)
 1. Start Postman
 1. Under **Files** > **New**, select the collection to import.
 1. After the collection is imported, expand the actions list (...).
diff --git a/articles/search/whats-new.md b/articles/search/whats-new.md
@@ -22,7 +22,7 @@ Azure Search is now renamed to **Azure Cognitive Search** to reflect the expande
 
 ## Feature announcements
 
-### May 2020 //build
+### May 2020 (Microsoft Build)
 
 + Debug sessions feature is now in preview. [Sign up to request access](https://aka.ms/DebugSessions). Debug sessions provides a portal-based interface to investigate and resolve issues with a skillset. Fixes created in the debug session can be saved to production skillsets or downloaded for import to your source-controlled project.
 
