Update docs/database-engine/availability-groups/windows/upgrading-always-on-availability-group-replica-instances.md

Author: MashaMSFT

docs/database-engine/availability-groups/windows/upgrading-always-on-availability-group-replica-instances.md

@@ -96,7 +96,7 @@ If necessary, you can perform an extra manual failover to return the AG to its o
 > If `REQUIRED_SYNCHRONIZED_SECONDARIES_TO_COMMIT` is set to either `1` or `2`, the Primary replica may be unavailable for read/writes when a corresponding number of sync secondary replicas are not available during the update process.
 
 > [!NOTE]  
-> When you perform an in-place upgrade of a secondary replica to a newer version of SQL Server, the database inside the availability group remains in the **Synchronized / In Recovery** state until the availability group is manually failed over, which finishes the recovery and upgrades the database.   
+> When you perform an in-place upgrade of a secondary replica to a newer version of SQL Server, the database inside the availability group remains in the **Synchronizing / In recovery** or **Synchronized / In Recovery** state until the availability group is manually failed over, which finishes the recovery and upgrades the database.  An upgraded primary replica can no longer ship logs to any lower version secondary replica and data movement stops and no automatic failover can occur for that replica, and your availability databases are vulnerable to data loss. After you upgrade the old primary, you may need to resume synchronization.