Update secondary-replica-connection-redirection-always-on-availability-groups.md

Removing a paragraph that doesn't make sense in context, since read-write connections aren't supported for FAILOVER PARTNER connections

Author: kfarlee

docs/database-engine/availability-groups/windows/secondary-replica-connection-redirection-always-on-availability-groups.md

@@ -147,14 +147,10 @@ In the following diagram, the primary replica has been manually failed over to C
 ![Original Availability Group](media/replica-connection-redirection-always-on-availability-groups/03_redirectionAG.png)
 
 
-## SQL Server instance offline
-
-If the instance of SQL Server specified in the connection string is not available (has an outage), the connection will fail regardless of the role that the replica on the target server plays. To avoid prolonged application downtime, configure an alternative `FailoverPartner` in the connection string. The application has to implement retry logic to accommodate primary and secondary replicas not being online during the actual failover. For information about connection strings, see [SqlConnection.ConnectionString Property](/dotnet/api/system.data.sqlclient.sqlconnection.connectionstring).
-
 ## See Also
 
 [Overview of Always On Availability Groups (SQL Server)](../../../database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server.md)   
 
 [About Client Connection Access to Availability Replicas (SQL Server)](../../../database-engine/availability-groups/windows/about-client-connection-access-to-availability-replicas-sql-server.md)   
 
-[Availability Group Listeners, Client Connectivity, and Application Failover (SQL Server)](../../../database-engine/availability-groups/windows/listeners-client-connectivity-application-failover.md)
+[Availability Group Listeners, Client Connectivity, and Application Failover (SQL Server)](../../../database-engine/availability-groups/windows/listeners-client-connectivity-application-failover.md)