edits

Author: TheovanKraay

articles/cosmos-db/nosql/conceptual-resilient-sdk-applications.md

@@ -112,9 +112,11 @@ Azure Cosmos DB SDKs provide detailed information in their logs and diagnostics
 
 ## How can I mitigate retry latency?
 
-Retry policies in Azure Cosmos DB are influenced by the [preferred regions](tutorial-global-distribution.md#preferred-locations) specified in your configuration. By default, the SDK will always attempt to connect to the first region in the list of preferred regions, or to the primary [hub region](../multi-region-writes.md#hub-region) if no list is supplied. This prioritization can help minimize latency by primarily connecting to the nearest or most optimal data center.
+Retry policies in Azure Cosmos DB are influenced by the [preferred regions](tutorial-global-distribution.md#preferred-locations) specified in your configuration. 
 
-However, this prioritization also means that requests which are going to result in failure will also be tried in the preferred region first. If a failover is preferred in that scenario, this is typically handled at the infrastructure (traffic manager) layer rather than at the SDK level. Proper setup and configuration of your infrastructure can ensure that traffic is rerouted efficiently during regional outages, thereby mitigating the latency that comes with cross-region retries. For more detailed information on setting up infrastructure-level failover, you can refer to [Azure Traffic Manager documentation](../../traffic-manager/index.yml). Some SDKs support implementing similar failover strategies directly at the SDK level. For example, see [high availability for Java SDK](performance-tips-java-sdk-v4.md#high-availability).
+Depending on the [circumstances](troubleshoot-sdk-availability.md), in most cases the Java SDK will route requests to either the local region, the write region (in a single-region write scenario) or the first region in the [preferred regions](tutorial-global-distribution.md#preferred-locations) list. This prioritization minimizes latency in healthy scenarios by primarily connecting to the nearest or most optimal data center.
+
+However, this prioritization also means that requests which are going to result in failure will always be tried in one specific region first for a given error scenario. If a failover is preferred in that scenario, this is typically handled at the infrastructure (traffic manager) layer rather than at the SDK level. Proper setup and configuration of your infrastructure can ensure that traffic is rerouted efficiently during regional outages, thereby mitigating the latency that can come with cross-region retries in an outage scenario. For more detailed information on setting up infrastructure-level failover, you can refer to [Azure Traffic Manager documentation](../../traffic-manager/index.yml). Some SDKs support implementing similar failover strategies directly at the SDK level. For example, see [high availability for Java SDK](performance-tips-java-sdk-v4.md#high-availability).
 
 ## What about regional outages?