Jira DOC-814: RC - Clarify high-availability article

content/rc/databases/high-availability.md

@@ -11,25 +11,39 @@ aliases:
 
 Database replication helps ensure high availability. When replication is enabled, your dataset is duplicated to create a replica, which stays in sync with the primary dataset. Replication allows for automatic failover and greater fault tolerance. This can prevent data loss in the event of a hardware or zone failure. 
 
+## Options and plan support
+
 Redis Enterprise Cloud supports three levels of replication:
 
 - _No replication_ means that you will have a single copy of your database.
 - _Single-zone replication_ means that your database will have a primary and a replica located in the same zone of a cloud region. 
 - _Multi-zone replication_ means that the primary and its replicas are stored in different zones of a cloud region. This means that your database can remain online even if an entire zone becomes unavailable.
 
-Your replication options depend on which subscription plan you're using:
+Your replication options depend on your [subscription plan]({{<relref "/rc/subscriptions/_index.md">}}):
 
 - _Free_ plans do not support replication.
 - _Fixed_ plans let you choose between no replication, single-zone replication, or multi-zone replication when creating a subscription.  
+- _Flexible_ and _Annual_ plans allow multi-zone or single-zone subscriptions by default.  You can also disable replication.
+
+## Performance impact 
+
+Replication can affect performance as traffic increases to synchronize all copies. 
+
+Database storage costs also increase:
+
+- For Fixed plans, single-zone and multi-zone replication effectively doubles storage costs
+
+- For Flexible and Annual plans, replication requires additional shards
+
+## Zone setting maintenance
 
-Zone settings cannot be changed once a subscription has been created.  This means you can't convert a multi-zone subscription to a single zone (or vice-versa).
+Zone settings can only be defined when a subscription is created.  You cannot change these settings once the subscription becomes active.
 
-If this becomes necessary, create a new subscription with the preferred settings and then migrate data from the original subscription.```
-- _Flexible_ plans allow multi-zone or single-zone subscriptions by default.  Each type allows replication to be disabled entirely.  
+This means you can't convert a multi-zone subscription to a single zone (or vice-versa).  
 
-   Once the subscription is created, though, you cannot switch zone settings. 
+To use different zone settings, create a new subscription with the preferred settings and then migrate data from the original subscription.
 
-To learn more about Redis Enterprise Cloud subscriptions, see [Manage subscriptions]({{<relref "/rc/subscriptions/_index.md">}}).
+## More info
 
 To learn more about high availability and replication, see:
 - [Highly Available Redis](https://redislabs.com/redis-enterprise/technology/highly-available-redis/)

content/rc/how-to/view-edit-cloud-account.md

@@ -1,5 +1,5 @@
 ---
-Title: Create and edit a Cloud Account for Redis Cloud Ultimate
+Title: Create and edit a Cloud Account
 description:
 weight: 20
 alwaysopen: false
@@ -8,27 +8,35 @@ aliases: /rv/how-to/view-edit-cloud-account/
         /rv/how-to/creating-cloud-account/
         /rc/how-to/creating-cloud-account/
 ---
-In Redis Cloud Ultimate subscriptions, most customers build their subscriptions in our AWS accounts
-so that we can take responsibility to make sure that the infrastructure is in optimal condition.
-If you need to build your subscriptions in your own AWS accounts,
-we need to have access to your AWS account to help with monitoring, maintenance, and technical support.
 
-To provide us with secure authorization to access your AWS accounts, you need to:
+Many customers use cloud provider accounts provisioned and maintained by Redis Labs.
 
-1. Create a programmatic user and provide us with the access key and secret access key for that user.
-1. Create a console role and provide us with that role name.
+Customers with existing Amazon Web Services accounts can provision their Flexible or Annual subscriptions to use their existing AWS accounts.  
+
+To do so, you associate your existing AWS account as a _cloud account_ for your subscription, which requires entering credentials to enable monitoring, maintenance, and technical support.
+
+You need to create:
+
+1. A programmatic user and provide us with the access key and secret access key for that user.
+1. A console role and provide us with that role name.
 
 To create or edit a cloud account in Redis Cloud:
 
-1. In **Cloud Accounts**, either:
-    - Click ![Add](/images/rs/icon_add.png#no-click "Add") to create a new account.
-    - Click on the account that you want to edit and then click **Edit**.
-1. Enter the cloud account details:
-    - **Account Name** - A meaningful name for the account.
+1. Sign into the admin console and then select the target subscription.
+
+1. From the console menu, select **Cloud Accounts** and then either:
+
+    - Select the ![Add](/images/rs/icon_add.png#no-click "Add") to add a new account.
+
+    - Select the account that you want to edit and then select **Edit**.
+
+1. Enter the cloud account details, which include:
+
+    - **Account Name** - A meaningful name for the account
     - **AWS_ACCESS_KEY_ID** - The AWS access key for the programmatic user
     - **AWS_SECRET_ACCESS_KEY** - The AWS secret access key for the programmatic user
     - **IAM Role Name** - The name of the console role with access to the console
-1. Click **Save**.
 
-You can click **Delete** to delete your Cloud Account from Redis Cloud,
-but only if it has no active subscription related to it.
+1. Select **Save**.
+
+Use the **Delete** button to remove a cloud account from your subscription.

content/rc/security/database-security/network-security.md

@@ -64,7 +64,7 @@ To restrict a database to a specific set of source IP addresses or subnets:
 
 A [Virtual Private Cloud](https://en.wikipedia.org/wiki/Virtual_private_cloud) (VPC) is an isolated set of resources within a [public cloud](https://en.wikipedia.org/wiki/Cloud_computing#Public_cloud), usually having its own subnets and VLAN.
 
-Databases in Redis Cloud Pro and Ultimate are almost always deployed in a Redis Labs VPC. In most cases, you'll need to create a **VPC peering connection** to access these databases. A VPC peering connection allows unrestricted network access between two VPCs.
+Databases in Flexible and Annual subscriptions are almost always deployed in a Redis Labs VPC. In most cases, you'll need to create a **VPC peering connection** to access these databases. A VPC peering connection allows unrestricted network access between two VPCs.
 
 How you create these connections, and the features supported, varies somewhat by public cloud. You can read about VPC usage for [AWS](#vpcs-with-aws), [GCP](#vpcs-with-gcp), and [Azure](#vpcs-with-azure) below.