more formatting fixes

HeidiSteen · HeidiSteen · commit 2dca0f01f22e · 2025-07-02T18:50:31.000-07:00
diff --git a/articles/search/includes/quickstarts/semantic-ranker-csharp.md b/articles/search/includes/quickstarts/semantic-ranker-csharp.md
@@ -10,15 +10,15 @@ ms.date: 07/03/2025
 
 [!INCLUDE [Semantic ranker introduction](semantic-ranker-intro.md)]
 
-> [!TIP]
-> You can [download the source code](https://github.com/Azure-Samples/azure-search-dotnet-samples/tree/main/quickstart-semantic-search/SemanticSearchQuickstart) to start with a finished project or follow these steps to create your own. 
-
 ## Set up the client
 
 In this quickstart, you use an IDE and the [**Azure.Search.Documents**](/dotnet/api/overview/azure/search.documents-readme) client library to add semantic ranking to an existing search index.
 
 We recommend [Visual Studio](https://visualstudio.microsoft.com/vs/community/) for this quickstart.
 
+> [!TIP]
+> You can [download the source code](https://github.com/Azure-Samples/azure-search-dotnet-samples/tree/main/quickstart-semantic-search/SemanticSearchQuickstart) to start with a finished project or follow these steps to create your own. 
+
 ### Install libraries
 
 1. Start Visual Studio and open the [quickstart-semantic-search.sln](https://github.com/Azure-Samples/azure-search-dotnet-samples/tree/main/quickstart-semantic-search) or create a new project using a console application template.
diff --git a/articles/search/includes/quickstarts/semantic-ranker-python.md b/articles/search/includes/quickstarts/semantic-ranker-python.md
@@ -10,15 +10,15 @@ ms.date: 07/03/2025
 
 [!INCLUDE [Semantic ranker introduction](semantic-ranker-intro.md)]
 
-> [!TIP]
-> You can [download a finished notebook](https://github.com/Azure-Samples/azure-search-python-samples/tree/main/Quickstart-Semantic-Search) to start with a finished project or follow these steps to create your own. 
-
 ## Set up the client
 
 In this quickstart, use a Jupyter notebook and the [**azure-search-documents**](/python/api/overview/azure/search-documents-readme) library in the Azure SDK for Python to learn about semantic ranking.
 
 We recommend [Visual Studio Code](https://code.visualstudio.com/download) with Python 3.10 or later and the [Python extension](https://code.visualstudio.com/docs/languages/python) for this quickstart.
 
+> [!TIP]
+> You can [download a finished notebook](https://github.com/Azure-Samples/azure-search-python-samples/tree/main/Quickstart-Semantic-Search) to start with a finished project or follow these steps to create your own. 
+
 We recommend a virtual environment for this quickstart:
 
 1. Start Visual Studio Code.
@@ -122,73 +122,72 @@ In this section, you update a search index to include a semantic configuration.
 
 1. Add a semantic configuration to an existing hotels-sample-index on your search service. No search documents are deleted by this operation and your index is still operational after the configuration is added.
 
-```python
-# Add semantic configuration to hotels-sample-index and display updated index details
-from azure.search.documents.indexes.models import (
-    SemanticConfiguration,
-    SemanticField,
-    SemanticPrioritizedFields,
-    SemanticSearch
-)
-
-try:
-    # Get the existing index
-    existing_index = index_client.get_index(index_name)
-    
-    # Create a new semantic configuration
-    new_semantic_config = SemanticConfiguration(
-        name="semantic-config",
-        prioritized_fields=SemanticPrioritizedFields(
-            title_field=SemanticField(field_name="HotelName"),
-            keywords_fields=[SemanticField(field_name="Tags")],
-            content_fields=[SemanticField(field_name="Description")]
-        )
+    ```python
+    # Add semantic configuration to hotels-sample-index and display updated index details
+    from azure.search.documents.indexes.models import (
+        SemanticConfiguration,
+        SemanticField,
+        SemanticPrioritizedFields,
+        SemanticSearch
     )
     
-    # Add semantic configuration to the index
-    if existing_index.semantic_search is None:
-        existing_index.semantic_search = SemanticSearch(configurations=[new_semantic_config])
-    else:
-        # Check if configuration already exists
-        config_exists = any(config.name == "semantic-config" 
-                          for config in existing_index.semantic_search.configurations)
-        if not config_exists:
-            existing_index.semantic_search.configurations.append(new_semantic_config)
-    
-    # Update the index
-    result = index_client.create_or_update_index(existing_index)
-    
-    # Get the updated index and display detailed information
-    updated_index = index_client.get_index(index_name)
-    
-    print("Semantic configurations:")
-    print("-" * 40)
-    if updated_index.semantic_search and updated_index.semantic_search.configurations:
-        for config in updated_index.semantic_search.configurations:
-            print(f"  Configuration: {config.name}")
-            if config.prioritized_fields.title_field:
-                print(f"    Title field: {config.prioritized_fields.title_field.field_name}")
-            if config.prioritized_fields.keywords_fields:
-                keywords = [kf.field_name for kf in config.prioritized_fields.keywords_fields]
-                print(f"    Keywords fields: {', '.join(keywords)}")
-            if config.prioritized_fields.content_fields:
-                content = [cf.field_name for cf in config.prioritized_fields.content_fields]
-                print(f"    Content fields: {', '.join(content)}")
-            print()
-    else:
-        print("  No semantic configurations found")
-    
-    print("✅ Semantic configuration successfully added!")
+    try:
+        # Get the existing index
+        existing_index = index_client.get_index(index_name)
+        
+        # Create a new semantic configuration
+        new_semantic_config = SemanticConfiguration(
+            name="semantic-config",
+            prioritized_fields=SemanticPrioritizedFields(
+                title_field=SemanticField(field_name="HotelName"),
+                keywords_fields=[SemanticField(field_name="Tags")],
+                content_fields=[SemanticField(field_name="Description")]
+            )
+        )
+        
+        # Add semantic configuration to the index
+        if existing_index.semantic_search is None:
+            existing_index.semantic_search = SemanticSearch(configurations=[new_semantic_config])
+        else:
+            # Check if configuration already exists
+            config_exists = any(config.name == "semantic-config" 
+                              for config in existing_index.semantic_search.configurations)
+            if not config_exists:
+                existing_index.semantic_search.configurations.append(new_semantic_config)
+        
+        # Update the index
+        result = index_client.create_or_update_index(existing_index)
+        
+        # Get the updated index and display detailed information
+        updated_index = index_client.get_index(index_name)
+        
+        print("Semantic configurations:")
+        print("-" * 40)
+        if updated_index.semantic_search and updated_index.semantic_search.configurations:
+            for config in updated_index.semantic_search.configurations:
+                print(f"  Configuration: {config.name}")
+                if config.prioritized_fields.title_field:
+                    print(f"    Title field: {config.prioritized_fields.title_field.field_name}")
+                if config.prioritized_fields.keywords_fields:
+                    keywords = [kf.field_name for kf in config.prioritized_fields.keywords_fields]
+                    print(f"    Keywords fields: {', '.join(keywords)}")
+                if config.prioritized_fields.content_fields:
+                    content = [cf.field_name for cf in config.prioritized_fields.content_fields]
+                    print(f"    Content fields: {', '.join(content)}")
+                print()
+        else:
+            print("  No semantic configurations found")
+        
+        print("✅ Semantic configuration successfully added!")
+        
+    except Exception as ex:
+        print(f"❌ Error adding semantic configuration: {ex}")
+    ```
     
-except Exception as ex:
-    print(f"❌ Error adding semantic configuration: {ex}")
-```
-
 1. Run the code.
 
 1. Output is the semantic configuration you just added.
 
-
 ## Run semantic queries
 
 Once the index has a semantic configuration, you can run queries that include semantic parameters.
diff --git a/articles/search/includes/quickstarts/semantic-ranker-rest.md b/articles/search/includes/quickstarts/semantic-ranker-rest.md
@@ -9,15 +9,15 @@ ms.date: 07/03/2025
 
 [!INCLUDE [Semantic ranker introduction](semantic-ranker-intro.md)]
 
-> [!TIP]
-> You can [download the source code](https://github.com/Azure-Samples/azure-search-rest-samples/tree/main/Quickstart-semantic-search) to start with a finished project or follow these steps to create your own. 
-
 ## Set up the client
 
 In this quickstart, you use a REST client and the [Azure AI Search REST APIs](/rest/api/searchservice) to configure and use a semantic ranker.
 
 We recommend [Visual Studio Code](https://code.visualstudio.com/download) with a [REST client extension](https://marketplace.visualstudio.com/items?itemName=humao.rest-client) for this quickstart.
 
+> [!TIP]
+> You can [download the source code](https://github.com/Azure-Samples/azure-search-rest-samples/tree/main/Quickstart-semantic-search) to start with a finished project or follow these steps to create your own. 
+
 1. Start Visual Studio Code and open the [semantic-search-index-update.rest](https://github.com/Azure-Samples/azure-search-rest-samples/blob/main/Quickstart-semantic-search/semantic-search-index-update.rest) file or create a new file.
 
 1. At the top, set environment variables for your search service, authorization, and index name.
@@ -26,18 +26,20 @@ We recommend [Visual Studio Code](https://code.visualstudio.com/download) with a
 
    + For @personalAccessToken, follow the instructions in [Connect without keys](../../search-get-started-rbac.md) to get your personal access token.
 
-1. To test the connection, send your first request. 
-
-   :::image type="content" source="../../media/search-get-started-semantic/visual-studio-code-send-request.png" alt-text="Screenshot of the REST client send request link.":::
-
-  This GET request returns a list of existing indexes. You should get an HTTP 200 Success status code and a list of indexes, including hotels-sample-index used in this quickstart.
+1. To test the connection, send your first request.
 
    ```http
    ### List existing indexes by name (verify the connection)
     GET  {{searchUrl}}/indexes?api-version=2025-05-01-preview&$select=name  HTTP/1.1
     Authorization: Bearer {{personalAccessToken}}
    ```
 
+1. Select **Sent request**.
+
+   :::image type="content" source="../../media/search-get-started-semantic/visual-studio-code-send-request.png" alt-text="Screenshot of the REST client send request link.":::
+
+1. Output for this GET request returns a list of existing indexes. You should get an HTTP 200 Success status code and a list of indexes, including hotels-sample-index used in this quickstart.
+
 ## Update the index
 
 To update an index using the REST API, you must provide the entire schema, plus the modifications you want to make. This request provides hotels-sample-index schema, plus the semantic configuration. The modification consists of the following JSON.
@@ -59,8 +61,7 @@ To update an index using the REST API, you must provide the entire schema, plus
 }
 ```
 
-The full POST request specifies the index name, operation, and full JSON schema. All required elements of the schema must be present. For this task, we recommend a GET to return the schema, and then adding your modifications.
-
+The full POST request specifies the index name, operation, and full JSON schema. All required elements of the schema must be present. This request includes the full schema for hotels-sample-index plus the semantic configuration.
 ```http
 POST  {{searchUrl}}/indexes?api-version=2025-05-01-preview  HTTP/1.1
 Content-Type: application/json
