Update storage-table-cosmos-comparison.md

Phasing out all occurrences of "automatic failover" with "service-managed failover"

Author: abinav2307

includes/storage-table-cosmos-comparison.md

@@ -15,7 +15,7 @@ If you currently use Azure Table Storage, you gain the following benefits by mov
 | --- | --- | --- |
 | Latency | Fast, but no upper bounds on latency. | Single-digit millisecond latency for reads and writes, backed with <10-ms latency reads and <15-ms latency writes at the 99th percentile, at any scale, anywhere in the world. |
 | Throughput | Variable throughput model. Tables have a scalability limit of 20,000 operations/s. | Highly scalable with [dedicated reserved throughput per table](../articles/cosmos-db/request-units.md) that's backed by SLAs. Accounts have no upper limit on throughput and support >10 million operations/s per table (in provisioned throughput mode). |
-| Global distribution | Single region with one optional readable secondary read region for high availability which supports automatic and manual account failover. | [Turnkey global distribution](../articles/cosmos-db/distribute-data-globally.md) from one to 30+ regions. Support for [automatic and manual failovers](../articles/cosmos-db/high-availability.md) at any time, anywhere in the world. |
+| Global distribution | Single region with one optional readable secondary read region for high availability which supports automatic and manual account failover. | [Turnkey global distribution](../articles/cosmos-db/distribute-data-globally.md) from one to 30+ regions. Support for [service-managed and manual failovers](../articles/cosmos-db/high-availability.md) at any time, anywhere in the world. |
 | Indexing | Only primary index on PartitionKey and RowKey. No secondary indexes. | Automatic and complete indexing on all properties, no index management. |
 | Query | Query execution uses index for primary key, and scans otherwise. | Queries can take advantage of automatic indexing on properties for fast query times. |
 | Consistency | Strong within primary region. Eventual within secondary region. | [Five well-defined consistency levels](../articles/cosmos-db/consistency-levels.md) to trade off availability, latency, throughput, and consistency based on your application needs. |