Update availability-modes-always-on-availability-groups.md

Author: AttinderPalSingh

docs/database-engine/availability-groups/windows/availability-modes-always-on-availability-groups.md

@@ -22,10 +22,9 @@ ms.custom:
 
   In [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)], the *availability mode* is a replica property that determines whether a given availability replica can run in synchronous-commit mode. For each availability replica, the availability mode must be configured for either synchronous-commit mode, asynchronous-commit, or configuration only mode.
 If the primary replica is configured for *asynchronous-commit mode*, it doesn't wait for any secondary replica to write incoming transaction log records to disk (to *harden the log*). If a given secondary replica is configured for asynchronous-commit mode, the primary replica doesn't wait for that secondary replica to harden the log. If both the primary replica and a given secondary replica are both configured for *synchronous-commit mode*, the primary replica waits for the secondary replica to confirm that it has hardened the log (unless the secondary replica fails to ping the primary replica within the primary's *session-timeout period*). 
-  
 
 > [!NOTE]  
->  If primary's session-timeout period is exceeded by a secondary replica, the primary replica temporarily shifts into asynchronous-commit mode for that secondary replica. When the secondary replica reconnects with the primary replica, they resume synchronous-commit mode.
+> If a synchronous-commit secondary replica exceeds the primary replica's session-timeout period (default is [10 seconds](#HowSyncWorks)), the primary replica temporarily marks the synchronization state of every database on this secondary replica as `NOT SYNCHRONIZING` and the replica state as `NOT_HEALTHY`. When the secondary replica reconnects with the primary replica, they resume synchronous-commit mode.
 
 
 ##  <a name="SupportedAvModes"></a> Supported availability modes