fixed build validation errors

Author: HeidiSteen

articles/search/search-howto-incremental-index.md

@@ -106,7 +106,7 @@ POST https://[service name].search.windows.net/indexers?api-version=2024-05-01-p
 
 ### Step 3: Reset the indexer
 
-[Reset Indexer](rest/api/searchservice/indexers/reset) is required when setting up incremental enrichment for existing indexers to ensure all documents are in a consistent state. You can use the portal or an API client for this task.
+[Reset Indexer](/rest/api/searchservice/indexers/reset) is required when setting up incremental enrichment for existing indexers to ensure all documents are in a consistent state. You can use the portal or an API client for this task.
 
 ```https
 POST https://[YOUR-SEARCH-SERVICE].search.windows.net/indexers/[YOUR-INDEXER-NAME]/reset?api-version=2024-05-01-preview

articles/search/search-howto-run-reset-indexers.md

@@ -202,9 +202,9 @@ If the document is enriched through a skillset and has cached data, the  skillse
 
 When you're testing this API for the first time, the following APIs can help you validate and test the behaviors. You can use preview API version 2020-06-30-preview and later. We recommend using the latest preview API.
 
-1. Call [Indexers - Get Status](/rest/api/searchservice/indexers/get-status?view=rest-searchservice-2024-05-01-preview&preserve-version=true) with a preview API version to check reset status and execution status. You can find information about the reset request at the end of the status response.
+1. Call [Indexers - Get Status](/rest/api/searchservice/indexers/get-status?view=rest-searchservice-2024-05-01-preview&preserve-view=true) with a preview API version to check reset status and execution status. You can find information about the reset request at the end of the status response.
 
-1. Call [Indexers - Reset Docs](/rest/api/searchservice/indexers/reset-docs?view=rest-searchservice-2024-05-01-preview&preserve-version=true) with a preview API version to specify which documents to process.
+1. Call [Indexers - Reset Docs](/rest/api/searchservice/indexers/reset-docs?view=rest-searchservice-2024-05-01-preview&preserve-view=true) with a preview API version to specify which documents to process.
 
     ```http
     POST https://[service name].search.windows.net/indexers/[indexer name]/resetdocs?api-version=2024-05-01-preview

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

@@ -315,7 +315,7 @@ On the Azure AI Search side, you can confirm request approval by revisiting the
 
    :::image type="content" source="media/search-indexer-howto-secure-access/new-shared-private-link-resource-approved.png" alt-text="Screenshot of the Azure portal, showing an Approved shared private link resource.":::
 
-Alternatively, you can also obtain connection state by using the [GET Shared Private Link API](/rest/api/searchmanagement/2021-06-01-preview/shared-private-link-resources/get).
+Alternatively, you can also obtain connection state by using the [Shared Private Link Resources - Get](/rest/api/searchmanagement/shared-private-link-resources/get).
 
 ```dotnetcli
 az rest --method get --uri https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/contoso/providers/Microsoft.Search/searchServices/contoso-search/sharedPrivateLinkResources/blob-pe?api-version=2023-11-01

articles/search/search-security-manage-encryption-keys.md

@@ -299,9 +299,9 @@ Encryption keys are added when you create an object. To add a customer-managed k
 
    + [Create Index](/rest/api/searchservice/indexes/create)
    + [Create Synonym Map](/rest/api/searchservice/synonym-maps/create)
-   + [Create Indexer](//rest/api/searchservice/indexers/create)
+   + [Create Indexer](/rest/api/searchservice/indexers/create)
    + [Create Data Source](/rest/api/searchservice/data-sources/create)
-   + [Create Skillset](/rest/api/searchservice/skillsets/create).
+   + [Create Skillset](/rest/api/searchservice/skillsets/create)
 
 1. Insert the encryptionKey construct into the object definition. This property is a first-level property, on the same level as name and description. The following [REST examples](#rest-examples) show property placement. If you're using the same vault, key, and version, you can paste in the same "encryptionKey" construct into each object definition.
 
@@ -379,7 +379,7 @@ This section shows the JSON for several objects so that you can see where to loc
 
 ### Index encryption
 
-The details of creating a new index via the REST API could be found at [Create Index (REST API)](/rest/api/searchservice/index/create), where the only difference is specifying the encryption key details as part of the index definition:
+The details of creating a new index via the REST API could be found at [Create Index (REST API)](/rest/api/searchservice/indexes/create), where the only difference is specifying the encryption key details as part of the index definition:
 
 ```json
 {
@@ -436,7 +436,7 @@ You can now send the synonym map creation request, and then start using it norma
 
 ### Data source encryption
 
-Create an encrypted data source using the [Create Data Source (REST API)](rest/api/searchservice/data-sources/create). Use the "encryptionKey" property to specify which encryption key to use.
+Create an encrypted data source using the [Create Data Source (REST API)](/rest/api/searchservice/data-sources/create). Use the "encryptionKey" property to specify which encryption key to use.
 
 ```json
 {