Apply suggestions from code review

Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>

Author: cmilesb

content/operate/rc/subscriptions/bring-your-own-cloud/_index.md

@@ -20,16 +20,16 @@ aliases:
 
 Redis Cloud Bring your own Cloud (BYOC) allows organizations to use their own cloud infrastructure to deploy Redis Cloud.
 
-By default, Redis is responsible for the infrastructure that runs Redis Cloud. However, if your organization has specific requirements, you may want to have more control over your data residency or security options. Redis Cloud BYOC lets you fulfill these requirements while keeping the managed service experience of Redis Cloud. Like standard Redis Cloud, Redis handles deployment, scaling, monitoring, and support, so you can focus on building applications while Redis manages the backend.
+By default, Redis hosts the infrastructure that runs Redis Cloud. However, if your organization has specific requirements, you may need to have more control over your data residency or security options. Redis Cloud BYOC lets you fulfill these requirements while still having a fully managed service experience of Redis Cloud. Like standard Redis Cloud, Redis manages deployment, scaling, monitoring, and support, so you can focus on building applications while Redis manages the backend.
 
-If you're interested in Redis Cloud BYOC, [contact sales](https://redis.io/meeting/).
+Redis Cloud BYOC availability requires approval from Redis. If you're interested, [contact sales](https://redis.io/meeting/).
 
 ## Benefits of Redis Cloud BYOC
 
 Redis Cloud BYOC has some benefits over standard Redis Cloud:
 
 - **Full Data Control**: All data stays within your environment, giving you complete control over data security and reducing risks associated with data sovereignty.
-- **Simplified Compliance**: BYOC simplifies adherence to regulatory standards like GDPR, HIPAA, and compliance frameworks like SOC 2 and PCI DSS since data remains within the your own cloud account.
+- **Simplified Compliance**: BYOC simplifies adherence to regulatory standards like GDPR, HIPAA, and compliance frameworks like SOC 2 and PCI DSS since data remains within your own cloud account.
 - **Maximize Cloud Commitments**: Infrastructure costs are billed directly through your cloud provider account, enabling you to fully utilize existing commitments.
 - **Separation of Costs**: Customers pay Redis only for licensing and management, while infrastructure costs go directly to the cloud provider, offering clear visibility into each cost stream.
 - **Instant Access Control**: You can revoke Redis’ access to your environment at any time, offering complete control over data and infrastructure.
@@ -40,7 +40,7 @@ Consider using Redis Cloud BYOC if you have specific organizational needs or req
 
 - **Data Residency and Compliance**: Organizations operating in heavily regulated industries (such as finance, healthcare, and government) can use Redis Cloud BYOC to meet strict data residency and sovereignty requirements, ensuring sensitive data remains within their controlled environments.
 - **Cloud spend optimization**: Companies with significant cloud provider commitments can use Redis Cloud BYOC to optimize their cloud spend. Since infrastructure costs are billed directly through the cloud provider, customers can fully utilize existing cloud provider discounts, improving cost efficiency.
-- **Enhanced Security and Control**: Redis Cloud BYOC is ideal for organizations that require a higher degree of security and control over their data. By keeping data within your own cloud account and leveraging existing security policies, tools, and procedures on your cloud’s security infrastructure, you are able to minimize external access to your data, and adhere to more strict organizational security guidelines.
+- **Enhanced Security and Control**: Redis Cloud BYOC is ideal for organizations that require a higher degree of security and control over their data. By keeping data within your own cloud account, you can use existing security policies, tools, and procedures in your cloud’s security infrastructure. In this way, you can minimize external access to your data, and adhere to more strict organizational security guidelines.
 
 ## Set up Redis Cloud BYOC
 

content/operate/rc/subscriptions/bring-your-own-cloud/cloud-account-settings.md

@@ -10,7 +10,7 @@ hideListLinks: true
 weight: 2
 ---
 
-Redis Cloud Bring your own Cloud (BYOC) allows organizations to use their own cloud infrastructure to deploy Redis Cloud.
+Redis Cloud Bring your own Cloud (BYOC) lets you use your own cloud infrastructure to deploy Redis Cloud.
 
 You can associate your existing AWS account as a _cloud account_ for your subscription.  This requires setting up and entering credentials that enable monitoring, maintenance, and technical support of your subscription.
 

content/operate/rc/subscriptions/bring-your-own-cloud/iam-resources/aws-console.md

@@ -117,8 +117,8 @@ To create the role that uses the policy:
 1. In the AWS IAM console, go to **Roles** and click **Create Role**.
 1. Select **AWS Service** as the trusted entity, **EC2** as the service
     and use case, and click **Next: Permissions**.
-1. Enter `RedisLabsInstanceRolePolicy` in the search box to look up the policy we just created,
-    select it, and click **Next: Review**.
+1. Enter `RedisLabsInstanceRolePolicy` in the search box to look up the policy we just created.
+    Select it, and click **Next: Review**.
 1. Name the role `redislabs-cluster-node-role` and click **Create Role**.
 
 ## Step 3: Create the user policy