making updates based on feedback

Author: dereklegenzoff

articles/search/TOC.yml

@@ -280,7 +280,7 @@
     - name: Drop and rebuild an index
       href: search-howto-reindex.md
     - name: Create an index alias
-      href: search-howto-alias.md
+      href: search-how-to-alias.md
     - name: Create a multi-language index
       href: search-language-support.md
     - name: Index large data sets

articles/search/search-howto-alias.md renamed to articles/search/search-how-to-alias.md

@@ -19,7 +19,7 @@ In Azure Cognitive Search, an alias is a secondary name that can be used to refe
 
 The main goal of index aliases is to make it easier to manage your production indexes. For example, if you need to make a change to your index definition, such as editing a field or adding a new analyzer, you'll have to create a new search index because all search indexes are immutable. This means you either need to [drop and rebuild your index](search-howto-reindex.md) or create a new index and then migrate your application over to that index.
 
-Index aliases make this easier because you can create a new index alongside your current index and then whenever you're ready to migrate over to the new index, all you need to is update the mapping in your alias and requests will automatically start going to the new index.
+Index aliases make this easier because you can create a new index alongside your current index and then whenever you're ready to migrate over to the new index, all you need to do is update the mapping in your alias and requests will automatically start going to the new index.
 
 A typical workflow for using index aliases would be to: 
 
@@ -60,12 +60,12 @@ To create an alias in Visual Studio Code:
 
 ## Send requests
 
-Once you've created your alias, you're ready to start using it. Aliases can be used for all [document operations](rest/api/searchservice/document-operations) including querying, indexing, suggestions, and autocomplete. 
+Once you've created your alias, you're ready to start using it. Aliases can be used for all [document operations](/rest/api/searchservice/document-operations) including querying, indexing, suggestions, and autocomplete. 
 
-In the query below, instead of sending the request to `hotel-samples-index` you can instead send the request to `my-alias` and it will be routed accordingly. 
+In the query below, instead of sending the request to `hotel-samples-index`, you can instead send the request to `my-alias` and it will be routed accordingly. 
 
 ```http
-POST /indexes/my-alias/docs/search?api-version=2020-06-30
+POST /indexes/my-alias/docs/search?api-version=2021-04-30-preview
 {
     "search": "pool spa +airport",
     "searchMode": any,
@@ -75,14 +75,14 @@ POST /indexes/my-alias/docs/search?api-version=2020-06-30
 }
 ```
 
-In your client-side application, you can use the alias name rather than the index name to route all requests to the proper index. The alias gives you an easy mechanism to update where your application's requests are being routed to.
+If you expect that you may need to make updates to your index definition for your production indexes, you should use an alias rather than the index name for requests in your client-side application. Scenarios that require you to create a new index are outlined under these [rebuild conditions](search-howto-reindex.md#rebuild-conditions).
 
 > [!NOTE]
-> One area where aliases can't be used is with indexers: indexers don't support aliases so you can't include an alias as the `targetIndexName` on your indexer.
+> You can only use an alias with [document operations](/rest/api/searchservice/document-operations). Aliases can't be used to get or update an index definition, can't be used with the Analyze Text API, and can't be used as the `targetIndexName` on an indexer.
 
 ## Swap indexes
 
-Now, whenever you need to update your application to point to a new index, all you need to do is update the mapping in your alias. PUT is required for updates as described in [Create or Update Alias (REST preview)](rest/api/searchservice/preview-api/create-or-update-alias).
+Now, whenever you need to update your application to point to a new index, all you need to do is update the mapping in your alias. PUT is required for updates as described in [Create or Update Alias (REST preview)](/rest/api/searchservice/preview-api/create-or-update-alias).
 
 ```http
 PUT /aliases/my-alias?api-version=2021-04-30-preview

articles/search/search-howto-reindex.md

@@ -13,7 +13,7 @@ ms.date: 01/10/2022
 
 # Drop and rebuild an index in Azure Cognitive Search
 
-This article explains how to drop and rebuild an Azure Cognitive Search index, the circumstances under which rebuilds are required, and recommendations for mitigating the impact of rebuilds on ongoing query requests. If you frequently have to rebuild your search index, we recommend using [index aliases](search-howto-alias.md) to make it easier to swap which index your application is pointing to. 
+This article explains how to drop and rebuild an Azure Cognitive Search index, the circumstances under which rebuilds are required, and recommendations for mitigating the impact of rebuilds on ongoing query requests. If you frequently have to rebuild your search index, we recommend using [index aliases](search-how-to-alias.md) to make it easier to swap which index your application is pointing to. 
 
 A search index is a collection of physical folders and field-based inverted indexes of your content, distributed in shards across the number of partitions allocated to your search index. In Azure Cognitive Search, you cannot drop and recreate individual fields. If you want to fully rebuild a field, all field storage must be deleted, recreated based on an existing or revised index schema, and then repopulated with data pushed to the index or pulled from external sources. 
 

articles/search/search-limits-quotas-capacity.md

@@ -121,9 +121,9 @@ Maximum number of synonym maps varies by tier. Each rule can have up to 20 expan
 | Maximum synonym maps |3 |3|5 |10 |20 |20 | 10 | 10 |
 | Maximum number of rules per map |5000 |20000|20000 |20000 |20000 |20000 | 20000 | 20000  |
 
-## Alias limits
+## Index alias limits
 
-Maximum number of aliases varies by tier. In all tiers, the maximum number of aliases is the same as the maximum number of indexes.
+Maximum number of [index aliases](search-how-to-alias.md) varies by tier. In all tiers, the maximum number of aliases is the same as the maximum number of indexes.
 
 | Resource | Free | Basic | S1 | S2 | S3 | S3-HD |L1 | L2 |
 | -------- | -----|------ |----|----|----|-------|---|----|

articles/search/whats-new.md

@@ -18,7 +18,7 @@ Learn what's new in the service. Bookmark this page to keep up to date with serv
 
 |Feature                          |  Description | Availability  |
 |------------------------------------|--------------|---------------|
-| [Aliases](search-howto-alias.md) | An alias is a secondary name that can be used to refer to an index for querying, indexing, and other operations. You can create an alias that maps to a search index and substitute the alias name in places where you would otherwise reference an index name. This gives you added flexibility if you ever need to change which index your application is pointing to. Instead of updating the references to the index name in your application, you can just update the mapping for your alias. | Public preview REST APIs (no portal support at this time).|
+| [Index aliases](search-how-to-alias.md) | An index alias is a secondary name that can be used to refer to an index for querying, indexing, and other operations. You can create an alias that maps to a search index and substitute the alias name in places where you would otherwise reference an index name. This gives you added flexibility if you ever need to change which index your application is pointing to. Instead of updating the references to the index name in your application, you can just update the mapping for your alias. | Public preview REST APIs (no portal support at this time).|
 
 ## December 2021