edit pass: search-get-started-articles

Author: paulth1

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

@@ -72,7 +72,7 @@ All requests require an API key on every request sent to your service. Having a
     }
     ```
 
-## 1 - Create an index
+## Create an index
 
 Unless you're using the portal, an index must exist on the service before you can load data. This step defines the index and pushes it to the service. The [Create Index REST API](/rest/api/searchservice/create-index) is used for this step.
 
@@ -168,7 +168,7 @@ This index is named `hotels-quickstart` and has the field definitions you see in
 
 <a name="load-documents"></a>
 
-## 2 - Load documents
+## Load documents
 
 To push documents, use an HTTP POST request to your index's URL endpoint. The REST API for this task is [Add, Update, or Delete Documents](/rest/api/searchservice/addupdate-or-delete-documents).
 
@@ -306,7 +306,7 @@ To push documents, use an HTTP POST request to your index's URL endpoint. The RE
     }
     ```
 
-## 3 - Search an index
+## Search an index
 
 This step shows you how to query an index by using the [Search Documents API](/rest/api/searchservice/search-documents).
 

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

@@ -70,7 +70,7 @@ If you're not familiar with the REST client for Visual Studio Code, this section
 
    :::image type="content" source="media/search-get-started-rest/rest-client-request-setup.png" lightbox="media/search-get-started-rest/rest-client-request-setup.png" alt-text="Screenshot that shows a REST client configured for a search service request.":::
 
-    **Key points:**
+    Key points:
   
     - Parameters are specified by using an `@` prefix.
     - `###` designates a REST call. The next line contains the request, which must include `HTTP/1.1`.

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

@@ -223,7 +223,7 @@ The index schema is organized around hotel content. Sample data consists of vect
 
 1. Select **Send request**. Recall that you need the REST client to send requests. You should have an `HTTP/1.1 201 Created` response. The response body should include the JSON representation of the index schema.
 
-    **Key points:**
+    Key points:
 
     - The `fields` collection includes a required key field and text and vector fields (such as `Description` and `DescriptionVector`) for text and vector search. Colocating vector and nonvector fields in the same index enables hybrid queries. For instance, you can combine filters, text search with semantic ranking, and vectors into a single query operation.
     - Vector fields must be `type: Collection(Edm.Single)` with `dimensions` and `vectorSearchProfile` properties.
@@ -371,7 +371,7 @@ api-key: {{apiKey}}
 }
 ```
 
-**Key points:**
+Key points:
 
 - Documents in the payload consist of fields defined in the index schema.
 - Vector fields contain floating point values. The dimensions attribute has a minimum of 2 and a maximum of 3,072 floating point values each. This quickstart sets the dimensions attribute to 1,536 because that's the size of embeddings generated by the Open AI's **text-embedding-ada-002** model.
@@ -385,7 +385,7 @@ There are several queries to demonstrate various patterns:
 - [Single vector search](#single-vector-search)
 - [Single vector search with filter](#single-vector-search-with-filter)
 - [Hybrid search](#hybrid-search)
-- [Semantic hybrid search with filter](#semantic-hybrid-search-with-filter)
+- [Semantic hybrid search with filter](#semantic-hybrid-search-with-a-filter)
 
 The vector queries in this section are based on two strings:
 
@@ -791,7 +791,7 @@ Here's the last query in the collection. This hybrid query with semantic ranking
     }
     ```
 
-    **Key points:**
+    Key points:
 
     - Vector search is specified through the `vectors.value` property. Keyword search is specified through the `search` property.
     - In a hybrid search, you can integrate vector search with full-text search over keywords. Filters, spell check, and semantic ranking apply to textual content only, and not vectors. In this final query, there's no semantic `answer` because the system didn't produce one that was sufficiently strong.