DOC-1720: Edit down descriptions for databases/durability-ha index page

content/rs/databases/durability-ha/_index.md

@@ -19,40 +19,24 @@ Redis Enterprise Software comes with several features that make your data more d
 
 ## [Replication]({{<relref "/rs/databases/durability-ha/replication.md">}})
 
-When you replicate your database, each database instance (shard) is copied one or more times. Your database will then have one primary shard, and one or more replica shards. The primary handles both writes and reads from users. The replicas receive copies of changes from the primary to stay consistent with the primary.
-
-When a primary shard fails, Redis Enterprise automatically promotes the replica shard to primary. When the failed shard comes back into a stable state, the data is copied to it and it becomes the new replica.
-
-For more details, see [Replication]({{<relref "/rs/databases/durability-ha/replication.md">}}).
+When you replicate your database, each database instance (shard) is copied one or more times. Your database will have one primary shard and one or more replica shards. When a primary shard fails, Redis Enterprise automatically promotes a replica shard to primary. 
 
 ## [Clustering]({{<relref "/rs/databases/durability-ha/clustering.md">}})
 
-Clustering (or sharding) breaks your database into individual instances (shards) that are then spread across several nodes. As you increase the number of shards, your throughput and memory will also increase. Scaling out this way allows you to scale your database as you add computing and resources to your cluster.
-
-Clustering also helps stop node failure from causing data availability loss. The cluster automatically syncs between nodes to make sure the replicas are up to date with their primary shards, even if they don’t reside on the same node.
-
-For more details, see [Clustering]({{<relref "/rs/databases/durability-ha/clustering.md">}}).
+Clustering (or sharding) breaks your database into individual instances (shards) and spreads them across several nodes. Clustering lets you add resources to your cluster to scale your database and prevents node failures from causing availability loss.
 
 ## [Database persistence]({{<relref "/rs/databases/configure/database-persistence.md">}})
 
-Database persistence gives your database durability against process or server failures by persisting data information to disk at set intervals. There are two persistence strategies available for each database: append-only files (AoF) and snapshots. Snapshots write a snapshot of your database to disk at set intervals of time (every 1, 6, or 12 hours). Append-only files append new write operations to a file after every write or every second.
-
-For more details, see [Database persistence]({{<relref "/rs/databases/configure/database-persistence.md">}}).
+Database persistence gives your database durability against process or server failures by saving data to disk at set intervals.
 
 ## [Active-Active geo-distributed replication]({{<relref "/rs/databases/active-active/_index.md">}})
 
-Redis Enterprise Active-Active distributes your replicated data across multiple nodes and availability zones. This increases the durability of your database by reducing the likelihood of data or availability loss. It also reduces the latency of your data access.
-
-For more details, see [Active-Active geo-distributed Redis]({{<relref "/rs/databases/active-active/_index.md">}}).
+Active-Active Redis Enterprise databases distribute your replicated data across multiple nodes and availability zones. This increases the durability of your database by reducing the likelihood of data or availability loss. It also reduces data access latency.
 
 ## [Rack-zone awareness]({{<relref "/rs/clusters/configure/rack-zone-awareness.md">}})
 
-Rack-zone awareness maps each node in your Redis Enterprise cluster to a physical rack or logical zone. The cluster then uses that information to distribute primary shards and their replica shards in different racks or zones. This protects your data and ensures data availability if there is rack or zone failure.
-
-For more details, see [Rack-zone awareness]({{<relref "/rs/clusters/configure/rack-zone-awareness.md">}}).
+Rack-zone awareness maps each node in your Redis Enterprise cluster to a physical rack or logical zone. The cluster uses this information to distribute primary shards and their replica shards in different racks or zones. This ensures data availability if a rack or zone fails.
 
 ## [Discovery service]({{<relref "/rs/databases/durability-ha/discovery-service.md">}})
 
-The Discovery service provides an IP-based connection management service used when connecting to Redis Enterprise Software databases. When used in conjunction with Redis Enterprise Software’s other high availability features, the Discovery Service assists an application scope with topology changes such as adding, removing of nodes, node failovers and so on. It does this by providing your application with the ability to easily discover which node hosts the database endpoint. The API used for discovery service is compliant with the Redis Sentinel API.
-
-For more details, see [Discovery service]({{<relref "/rs/databases/durability-ha/discovery-service.md">}}).
+The discovery service provides an IP-based connection management service used when connecting to Redis Enterprise Software databases. It lets your application discover which node hosts the database endpoint. The discovery service API complies with the [Redis Sentinel API](https://redis.io/docs/management/sentinel/#sentinel-api).