Merge pull request #191763 from MladjoA/patch-8

Update auto-failover-group-sql-mi.md

Author: PRMerger12

articles/azure-sql/managed-instance/auto-failover-group-sql-mi.md

@@ -185,7 +185,7 @@ Due to the high latency of wide area networks, geo-replication uses an asynchron
 > [!NOTE]
 > `sp_wait_for_database_copy_sync` prevents data loss after geo-failover for specific transactions, but does not guarantee full synchronization for read access. The delay caused by a `sp_wait_for_database_copy_sync` procedure call can be significant and depends on the size of the not yet transmitted transaction log on the primary at the time of the call.
 
-## Auto-failover group status
+## Failover group status
 Auto-failover group reports its status describing the current state of the data replication:
 
 - Seeding - [Initial seeding](auto-failover-group-sql-mi.md#initial-seeding) is taking place after creation of the failover group, until all user databases are initialized on the secondary instance. Failover process cannot be initiated while auto-failover group is in the Seeding status, since user databases are not copied to secondary instance yet.