Merge pull request #268985 from HeidiSteen/heidist-fix

[azure search] Revised the semi-structured JSON tutorial

Author: American-Dipper

articles/search/cognitive-search-tutorial-blob-dotnet.md

@@ -55,7 +55,7 @@ Once content is extracted, the [skillset](cognitive-search-working-with-skillset
 
 ### Download files
 
-Download a zip file of the sample data repository and extract the contents.
+Download a zip file of the sample data repository and extract the contents. [Learn how](https://docs.github.com/get-started/start-your-journey/downloading-files-from-github).
 
 + [Sample data files (mixed media)](https://github.com/Azure-Samples/azure-search-sample-data/tree/main/ai-enrichment-mixed-media)
 

articles/search/cognitive-search-tutorial-blob.md

@@ -49,7 +49,9 @@ Once content is extracted, the [skillset](cognitive-search-working-with-skillset
 
 ### Download files
 
-+ [Sample data files (mixed media)](https://github.com/Azure-Samples/azure-search-sample-data/tree/main/ai-enrichment-mixed-media). Download a zip file of the sample data repository and extract the contents.
+Download a zip file of the sample data repository and extract the contents. [Learn how](https://docs.github.com/get-started/start-your-journey/downloading-files-from-github).
+
++ [Sample data files (mixed media)](https://github.com/Azure-Samples/azure-search-sample-data/tree/main/ai-enrichment-mixed-media). 
 
 + [Sample REST file](https://github.com/Azure-Samples/azure-search-rest-samples/tree/main/skillset-tutorial)
 
@@ -122,7 +124,7 @@ POST {{baseUrl}}/datasources?api-version=2023-11-01  HTTP/1.1
 
 ### Step 2: Create a skillset
 
-Call [Create Skillset](/rest/api/searchservice/create-skillset) to specify which enrichment steps are applied to your content.
+Call [Create Skillset](/rest/api/searchservice/create-skillset) to specify which enrichment steps are applied to your content. Skills execute in parallel unless there's a dependency.
 
 ```http
 ### Create a skillset
@@ -309,7 +311,9 @@ POST {{baseUrl}}/skillsets?api-version=2023-11-01  HTTP/1.1
 
 ### Step 3: Create an index
 
-Call [Create Index](/rest/api/searchservice/create-index) to provide the schema used to create inverted indexes and other constructs in Azure AI Search. The largest component of an index is the fields collection, where data type and attributes determine content and behavior in Azure AI Search.
+Call [Create Index](/rest/api/searchservice/create-index) to provide the schema used to create inverted indexes and other constructs in Azure AI Search. 
+
+The largest component of an index is the fields collection, where data type and attributes determine content and behavior in Azure AI Search. Make sure you have fields for your newly generated output.
 
 ```http
 ### Create an index
@@ -398,7 +402,6 @@ POST {{baseUrl}}/indexes?api-version=2023-11-01  HTTP/1.1
     }
 ```
 
-
 ### Step 4: Create and run an indexer
 
 Call [Create Indexer](/rest/api/searchservice/create-indexer) to drive the pipeline. The three components you have created thus far (data source, skillset, index) are inputs to an indexer. Creating the indexer on Azure AI Search is the event that puts the entire pipeline into motion.

articles/search/search-indexer-field-mappings.md

@@ -63,6 +63,8 @@ Field mappings are added to the `fieldMappings` array of an indexer definition.
 | targetFieldName | Optional. Represents a field in your search index. If omitted, the value of `sourceFieldName` is assumed for the target. Target fields must be top-level simple fields or collections. It can't be a complex type or collection. If you're handling a data type issue, a field's data type is specified in the index definition. The field mapping just needs to have the field's name.|
 | mappingFunction | Optional. Consists of [predefined functions](#mappingFunctions) that transform data.  |
 
+If you get an error similar to `"Field mapping specifies target field 'Address/city' that doesn't exist in the index"`, it's because target field mappings can't be a complex type. The workaround is to create an index schema that's identical to the raw content for field names and data types. See [Tutorial: Index nested JSON blobs](search-semi-structured-data.md) for an example.
+
 Azure AI Search uses case-insensitive comparison to resolve the field and function names in field mappings. This is convenient (you don't have to get all the casing right), but it means that your data source or index can't have fields that differ only by case.  
 
 > [!NOTE]
@@ -386,7 +388,7 @@ This function converts a string into a formatted JSON object. This can be used f
 
 ### Example - map text content to a complex field
 
-Assume there is a SQL row with a JSON string that needs to be mapped to a (correspondingly defined) complex field in the index, the `toJson` function can be used to achieve this. For instance, if a complex field in the index needs to be populated with the following data:
+Assume there's a SQL row with a JSON string that needs to be mapped to a (correspondingly defined) complex field in the index, the `toJson` function can be used to achieve this. For instance, if a complex field in the index needs to be populated with the following data:
 
 ```JSON
 {