Update content/operate/rs/databases/active-active/develop/app-failover-active-active.md

Co-authored-by: Rachel Elledge <[email protected]>

Author: mich-elle-luna

content/operate/rs/databases/active-active/develop/app-failover-active-active.md

@@ -19,10 +19,10 @@ This guide explains how to implement robust failover and failback mechanisms for
 
 Active-Active databases don't include built-in application failover mechanisms. Instead, your application must:
 
-1. **Monitor** local and remote replicas for availability
-2. **Detect** failures quickly and accurately
-3. **Failover** to a healthy remote replica when needed
-4. **Failback** to the local replica when it recovers
+1. Monitor local and remote replicas for availability.
+2. Detect failures quickly and accurately.
+3. Failover to a healthy remote replica when needed.
+4. Failback to the local replica when it recovers.
 
 {{< warning >}}
 **Data consistency considerations**: Active-Active replication is asynchronous. Applications that failover to another replica may miss recent write operations, which can impact data consistency. If the failed replica saved the write operations in persistent storage, then the write operations are processed when the failed replica recovers.