Merge pull request #269382 from HeidiSteen/heidist-fix

Refresh pass, fixed customer-reported syntax issue

Author: prmerger-automator[bot]

articles/search/knowledge-store-projections-examples.md

@@ -10,7 +10,7 @@ ms.service: cognitive-search
 ms.custom:
   - ignite-2023
 ms.topic: conceptual
-ms.date: 01/31/2023
+ms.date: 03/18/2024
 ---
 
 # Define projections in a knowledge store
@@ -35,6 +35,7 @@ Recall that projections are defined under the "knowledgeStore" property of a ski
         "files": [ ]
       }
     ]
+}
 ```
 
 If you need more background before getting started, review [this check list](knowledge-store-projection-overview.md#checklist-for-getting-started) for tips and workflow.

articles/search/search-get-started-rest.md

@@ -51,7 +51,7 @@ If you're not familiar with the REST client for Visual Studio Code, this section
 
 1. Search for the REST client and select **Install**.
 
-   :::image type="content" source="media/search-get-started-rest/rest-client-install.png" alt-text="Screenshot of the install command.":::
+   :::image type="content" source="media/search-get-started-rest/rest-client-install.png" alt-text="Screenshot of the REST client install command.":::
 
 1. Open or create new file named with either a `.rest` or `.http` file extension.
 
@@ -257,7 +257,7 @@ Now that documents are loaded, you can issue queries against them using [Documen
 The URI is extended to include a query expression, specified using the `/docs/search` operator.
 
 1. Paste in the following example to query the search index, and then select **Send request**. A text search request always includes a `search` parameter. This example includes an optional `searchFields` parameter that constrains text search to specific fields.
-    
+
     ```http
     ### Run a query
     POST {{baseUrl}}/indexes/hotels-quickstart/docs/search?api-version=2023-11-01  HTTP/1.1
@@ -333,7 +333,7 @@ DELETE  {{baseUrl}}/indexes/hotels-quickstart?api-version=2023-11-01 HTTP/1.1
     api-key: {{apiKey}}
 ```
 
-## Next steps
+## Next step
 
 Now that you're familiar with the REST client and making REST calls to Azure AI Search, try another quickstart that demonstrates vector support.
 

articles/search/search-get-started-vector.md

@@ -138,7 +138,7 @@ The index schema is organized around hotels content. Sample data consists of vec
                 "filterable": true,
                 "retrievable": true,
                 "sortable": false,
-                "facetable": true,
+                "facetable": true
             },
             {
                 "name": "Address", 

articles/search/search-indexer-howto-access-private.md

@@ -45,8 +45,13 @@ Only your search service can use the private links that it creates, and there ca
 
 Once you set up the private link, it's used automatically whenever the search service connects to that PaaS resource. You don't need to modify the connection string or alter the client you're using to issue the requests, although the device used for the connection must connect using an authorized IP in the Azure PaaS resource's firewall.
 
-> [!NOTE]
-> There are two scenarios for using [Azure Private Link](../private-link/private-link-overview.md) and Azure AI Search together. Creating a shared private link is one scenario, relevant when an *outbound* connection to Azure PaaS requires a private connection. The second scenario is [configure search for a private *inbound* connection](service-create-private-endpoint.md) from clients that run in a virtual network. While both scenarios have a dependency on Azure Private Link, they are independent. You can create a shared private link without having to configure your own search service for a private endpoint.
+There are two scenarios for using [Azure Private Link](../private-link/private-link-overview.md) and Azure AI Search together.
+
++ Scenario one: create a shared private link when an *outbound* (indexer) connection to Azure PaaS requires a private connection.
+
++ Scenario two: [configure search for a private *inbound* connection](service-create-private-endpoint.md) from clients that run in a virtual network. 
+
+While both scenarios have a dependency on Azure Private Link, they are independent. You can create a shared private link without having to configure your own search service for a private endpoint.
 
 ### Limitations
 
@@ -353,10 +358,6 @@ This step shows you how to configure the indexer to run in the private environme
     }
     ```
 
-    Following is an example of the request in Postman.
-
-    ![Screenshot showing the creation of an indexer on the Postman user interface.](media\search-indexer-howto-secure-access\create-indexer.png)
-
 After the indexer is created successfully, it should connect to the Azure resource over the private endpoint connection. You can monitor the status of the indexer by using the [Indexer Status API](/rest/api/searchservice/get-indexer-status).
 
 > [!NOTE]
@@ -366,7 +367,7 @@ After the indexer is created successfully, it should connect to the Azure resour
 
 1. If you haven't done so already, verify that your Azure PaaS resource refuses connections from the public internet. If connections are accepted, review the DNS settings in the **Networking** page of your Azure PaaS resource.
 
-1. Choose a tool that can invoke an outbound request scenario, such as an indexer connection to a private endpoint. An easy choice is using the **Import data** wizard, but you can also try the Postman app and REST APIs for more precision. Assuming that your search service isn't also configured for a private connection, the REST client connection to Search can be over the public internet.
+1. Choose a tool that can invoke an outbound request scenario, such as an indexer connection to a private endpoint. An easy choice is using the **Import data** wizard, but you can also try a REST client and REST APIs for more precision. Assuming that your search service isn't also configured for a private connection, the REST client connection to search can be over the public internet.
 
 1. Set the connection string to the private Azure PaaS resource. The format of the connection string doesn't change for shared private link. The search service invokes the shared private link internally.