Incorporated Heidi's feedback

Author: haileytap

articles/search/search-multi-region.md

@@ -27,7 +27,7 @@ If you need two or more search services, creating them in different regions can
 
 In a multi-region setup, two or more search services are located in different regions and have synchronized indexes. Users are automatically routed to the service with the lowest latency.
 
-Azure AI Search doesn't provide an automated method of index replication across regions. However, you can [synchronize data](#data-synchronization) using indexers or REST APIs, both of which are described in the following section. You can also add Azure Traffic Manager for [request redirection](#request-failover-and-redirection).
+Azure AI Search doesn't provide an automated method of index replication across regions. However, you can synchronize data using [push or pull model indexing](search-what-is-data-import.md), both of which are described in the following section. You can also add Azure Traffic Manager for [request redirection](#request-failover-and-redirection).
 
 The following diagram illustrates a geo-distributed set of search services:
 
@@ -40,21 +40,21 @@ The following diagram illustrates a geo-distributed set of search services:
 
 To synchronize two or more distinct search services, you can either:
 
++ Push content into an index using [Documents - Index (REST API)](/rest/api/searchservice/documents/) or an equivalent API in the Azure SDKs.
 + Pull content into an index using an [indexer](search-indexer-overview.md).
-+ Push content into an index using the [Documents - Index REST API](/rest/api/searchservice/documents/) or an equivalent API in the Azure SDKs.
 
-### [Indexers](#tab/indexers)
+### [Push APIs](#tab/push-apis)
+
+If you use the REST APIs to [push content into your index](search-what-is-data-import.md#pushing-data-to-an-index), you can synchronize multiple search services by sending updates to each service whenever changes occur. Ensure that your code handles cases in which an update fails for one service but succeeds for other services.
+
+### [Pull APIs (Indexers)](#tab/pull-apis)
 
 If you have an indexer on one search service, you can create a second indexer on a second service to reference the same data source. Each service in each region has its own indexer and target index. Although the indexes are independent and store their own copies of the data, they remain synchronized because the indexers pull from the same source.
 
 The following diagram illustrates this architecture:
 
 :::image type="content" source="media/search-reliability/scale-indexers.png" alt-text="Diagram of a single data source with distributed indexer and service combinations." border="true" lightbox="media/search-reliability/scale-indexers.png":::
 
-### [REST APIs](#tab/rest-apis)
-
-If you use the REST APIs to [push content to your index](search-what-is-data-import.md#pushing-data-to-an-index), you can synchronize multiple search services by sending updates to each service whenever changes occur. Ensure that your code handles cases in which an update fails for one service but succeeds for other services.
-
 ---
 
 ## Data residency

articles/search/search-reliability.md

@@ -6,7 +6,7 @@ author: haileytap
 ms.author: haileytapia
 ms.service: azure-ai-search
 ms.topic: reliability-article
-ms.date: 06/23/2025
+ms.date: 06/26/2025
 ms.custom:
   - subject-reliability
   - ignite-2023
@@ -106,9 +106,9 @@ When you follow this approach, you must synchronize indexes across regions to re
 
 ## Backups
 
-A business continuity strategy for the data layer usually involves restoring from a backup. Azure AI Search isn't a primary data storage solution, so Microsoft doesn't formally offer self-service backup and restore. However, you can use the `index-backup-restore` sample for [.NET](https://github.com/Azure-Samples/azure-search-dotnet-utilities/tree/main/index-backup-restore) or [Python](https://github.com/Azure/azure-search-vector-samples/tree/main/demo-python/code/utilities/index-backup-restore) to back up your index definition and its documents to a series of JSON files, which are then used to restore the index. You can also use the sample to move indexes between pricing tiers.
+A business continuity strategy for the data layer usually involves restoring from a backup. Azure AI Search isn't a primary data storage solution, so Microsoft doesn't formally offer self-service backup and restore. However, you can use the `index-backup-restore` sample for [.NET](https://github.com/Azure-Samples/azure-search-dotnet-utilities/tree/main/index-backup-restore) or [Python](https://github.com/Azure/azure-search-vector-samples/tree/main/demo-python/code/utilities/index-backup-restore) to back up your index definition and its documents to a series of JSON files, which are then used to restore the index.
 
-Otherwise, if you accidentally delete an index, the application code used to create and populate the index is the de facto restore option. To rebuild an index, you must:
+Otherwise, if you accidentally delete an index, the application code used to create and populate the index is the de facto restore option. To [rebuild an index](search-howto-reindex.md), you must:
 
 1. Delete the index, assuming it exists.
 1. Recreate the index in your search service.