Apply suggestions from code review

Co-authored-by: andy-stark-redis <[email protected]>

Author: cmilesb

content/operate/rc/changelog/february-2025.md

@@ -22,7 +22,7 @@ We added a Pico billing unit for Pro databases with a maximum size of 100 MB and
 
 Accounts created after February 23, 2025, can select the new [Redis hashing policy]({{< relref "/operate/rc/databases/configuration/clustering#redis-hashing-policy" >}}) for their databases when creating a new database. 
 
-The Redis hashing policy is identical to the [hashing policy used by Redis Community Edition]({{< relref "/operate/oss_and_stack/reference/cluster-spec#hash-tags" >}}). This policy is recommended for most users and should be selected if any of the following conditions apply:
+The Redis hashing policy is identical to the [hashing policy used by Redis Community Edition]({{< relref "/operate/oss_and_stack/reference/cluster-spec#hash-tags" >}}). This policy is recommended for most users. Select it if any of the following conditions apply:
 - This is your first Redis Cloud account, and you are starting fresh.
 - You are migrating data from Redis Community Edition or other Redis-managed platforms.
 - Your application does not use hashtags in database key names.

content/operate/rc/databases/configuration/clustering.md

@@ -136,7 +136,7 @@ However, this policy is less recommended and should be selected only if any of t
 - Your application uses multiple curly brackets within a key’s name
 
 In some cases, the Standard hashing policy behaves differently from the Redis hashing policy:
-1. Using empty hashtags (“{}”): the Standard hashing policy does not ignore empty hashtags, so 2 keys which start with empty hashtags will be hashed to the same hashslot (while the Redis hashing policy would ignore them). 
+1. Using empty hashtags (“{}”): the Standard hashing policy does not ignore empty hashtags, so two keys that start with empty hashtags will be hashed to the same hashslot (while the Redis hashing policy would ignore them). 
     For example: given 2 keys {}foo and {}bar, hashing would be:
     - Standard hashing policy: to the same hash slot
     - Redis hashing policy: to different hash slots

content/operate/rc/databases/create-database/create-pro-database-new.md

@@ -155,7 +155,7 @@ By default, you're shown basic settings, which include:
 | Database setting | Description |
 |:---------|:-----------|
 | **Name** | A custom name for your database (_required_) |
-| **Database version** | choose the Redis version of your databases. Choose **Redis 7.2** if you want to use the latest stable version of Redis, or select **Redis 7.4** for the Redis 7.4 Preview. <br/> Redis 7.4 offers hash field expiration and other feature set improvements. For more information on the changes in Redis 7.4, see the [Redis 7.4 release notes](https://redis.io/blog/announcing-redis-community-edition-and-redis-stack-74). |
+| **Database version** | The Redis version of your databases. Choose **Redis 7.2** if you want to use the latest stable version of Redis, or **Redis 7.4** for the Redis 7.4 Preview. <br/> Redis 7.4 offers hash field expiration and other feature set improvements. For more information on the changes in Redis 7.4, see the [Redis 7.4 release notes](https://redis.io/blog/announcing-redis-community-edition-and-redis-stack-74). |
 | **Dataset size (GB)** | The amount of data for your dataset. Specify small sizes as decimals of 1.0&nbsp;GB; example: `0.1` GB (minimum). We calculate the total memory limit for you based on the other settings you choose for your database. <br/> Databases with Search and query have specific sizing requirements, see [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. |
 | **High Availability** | Indicates whether a replica copy of the database is maintained in case the primary database becomes unavailable.  (Warning: Doubles memory consumption). See [High Availability]({{< relref "/operate/rc/databases/configuration/high-availability" >}}).  |
 | **Throughput** | Identifies maximum throughput for the database, which is specified in terms of operations per second (**Ops/sec**). See [Throughput]({{< relref "/operate/rc/databases/configuration/sizing#throughput" >}}) for more information. <br/> Databases with Search and query have specific throughput requirements, see [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. |