Updating files after Vale pass, adding Subnet to the accept.txt file

Author: forstisabella

src/connections/storage/data-lakes/data-lakes-manual-setup.md

@@ -32,7 +32,7 @@ The following lifecycle settings should be applied to your staging data:
 
 ## Step 2 - Configure an EMR cluster
 
-Segment requires access to an EMR cluster to perform necessary data processing. We recommend starting with a small cluster, with the option to add more compute resources as required.
+Segment requires access to an EMR cluster to perform necessary data processing. For best results, start with a small cluster and add more compute resources as required.
 
 ### Configure the hardware and networking configuration
 
@@ -216,7 +216,7 @@ Add a policy to the role created above to give Segment access to the relevant Gl
 ```
 
 > note ""
-> **NOTE:** The policy above grants full access to Athena, but the individual Glue and S3 policies decide which table is queryable. Segment queries for debugging purposes, and will notify you be for running any queries.
+> **NOTE:** The policy above grants full access to Athena, but the individual Glue and S3 policies determine which table will be queried. Segment queries for debugging purposes, and will notify you before running any queries.
 
 ## Debugging
 

src/connections/storage/data-lakes/update-emr-cluster.md

@@ -18,9 +18,9 @@ By updating your EMR cluster to 5.33.0, you can participate in [AWS Lake Formati
 
 ## Procedure
 1. Open your Segment app workspace and select the Data Lakes destination.
-2. On the Settings tab, select the EMR Cluster ID field and replace the existing ID with the ID of your v5.33.0 EMR cluster. For help finding the cluster ID in AWS, see Amazon's [View cluster status and details](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-manage-view-clusters.html). You do not need to update the Glue Catalog ID, IAM Role ARN, or S3 Bucket name fields.
+2. On the Settings tab, select the EMR Cluster ID field and replace the existing ID with the ID of your v5.33.0 EMR cluster. For help finding the cluster ID in AWS, see Amazon's [View cluster status and details](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-manage-view-clusters.html). You don't need to update the Glue Catalog ID, IAM Role ARN, or S3 Bucket name fields.
 3. Select **Save**.
-4. In AWS, view the Events tab for your cluster to verify it is receiving data.
+4. In the AWS EMR console, view the Events tab for your cluster to verify it is receiving data.
 
 You can delete the old EMR cluster from AWS after the following conditions have been met:
 * You have updated all Data Lakes to use the EMR cluster

vale-styles/Vocab/Docs/accept.txt

@@ -55,4 +55,5 @@ Smartly
 Hubspot
 Friendbuy
 Chargebee
-(?:L|l)ookback
+(?:L|l)ookback
+Subnet