Merge pull request #15059 from WilliamAntonRohm/issue-4806

sql-docs/issues/4806 -- clarify behavior

Author: PRMerger7

docs/database-engine/availability-groups/windows/suspend-an-availability-database-sql-server.md

@@ -26,7 +26,7 @@ ms.author: mathoma
 
 |Suspended Database|Effect of Suspend Command|  
 |------------------------|-------------------------------|  
-|Secondary database|Only the local secondary database is suspended and its synchronization state becomes NOT SYNCHRONIZING. Other secondary databases are not affected. The suspended database stops receiving and applying data (log records) and begins to fall behind the primary database. Existing connections on the readable secondary remain usable. New connections to the suspended database on the readable secondary are not allowed until data movement is resumed.<br /><br /> The primary database remains available. If you suspend each of the corresponding secondary databases, the primary database runs exposed.<br /><br /> **\*\* Important \*\*** While a secondary database is suspended, the send queue of the corresponding primary database will accumulate unsent transaction log records. Connections to the secondary replica return data that was available at the time the data movement was suspended.|  
+|Secondary database|Only the local secondary database is suspended and its synchronization state becomes NOT SYNCHRONIZING. Other secondary databases are not affected. The suspended database stops receiving and applying data (log records) and begins to fall behind the primary database. Existing connections on the readable secondary remain usable. New connections to the suspended database on the readable secondary are not allowed until data movement is resumed. This behavior only applies when connections are opened using listener and read-only routing.<br /><br /> The primary database remains available. If you suspend each of the corresponding secondary databases, the primary database runs exposed.<br /><br /> **\*\* Important \*\*** While a secondary database is suspended, the send queue of the corresponding primary database will accumulate unsent transaction log records. Connections to the secondary replica return data that was available at the time the data movement was suspended.|  
 |Primary database|The primary database stops data movement to every connected secondary database. The primary database continues running, in an exposed mode. The primary database remains available to clients, and existing connections on a readable secondary remain usable and new connections can be made.|  
 
 > [!NOTE]