general edits to align this doc with our style guide

Author: rchinn1

src/connections/destinations/catalog/actions-liveramp-audiences/index.md

@@ -38,7 +38,7 @@ The LiveRamp Audiences destination can be connected to **Twilio Engage sources o
 4. On the **Mappings** tab, click **Add Mapping** and choose whether your will be using S3 or SFTP to upload the files. Within the mapping, configure which fields from your payload will be included in the files.
 5. Enable the destination and configured mappings.
 6. On the **Engage > Audiences > (your audience)** page, click **Add Destination** and select the destination just created.
-7. In the settings that appear in the side panel, toggle the Send Track option on and do not change the Audience Entered/Audience Exited event names. Click Save Settings
+7. In the settings that appear in the side panel, toggle the **Send Track** option on and do not change the Audience Entered/Audience Exited event names. Click **Save Settings**.
 8. File a [support case](https://docs.liveramp.com/connect/en/considerations-when-uploading-the-first-file-to-an-audience.html#creating-a-support-case){:target="_blank"} with the LiveRamp team to configure and enable ingestion.
 
 > info "Mapping tester availability"
@@ -49,28 +49,28 @@ The LiveRamp Audiences destination can be connected to **Twilio Engage sources o
 ## Limitations 
 
 * Audience must have at least 25 unique members, otherwise the destination will fail and the data will not be synced. This means the Actions Mapping Event Tester does not work (only one test event can be configured).
-* Audience sync happens once per day. On a 24-hour cadence, but can take up to 30 hours.
+* Audience sync happens once per day, on a 24-hour cadence, but can take up to 30 hours.
 * Audience Sync is a full sync, including only users or accounts in the audience at the time of sync.
 * Files are created per audience.
 * After initial ingestion is complete, changing the mappings will cause the LiveRamp ingestion to start failing until ingestion setup is run again.
 * Time to first sync can be up to 3 days, please be patient.
-* Currently, sFTP transfer is not supported in EMEA Region. Only US region is supported for sFTP file transfer.
-* At this moment, the Delivery Overviews/Event Delivery tabs does not reflect the correct status of the file transfers to either S3 or sFTP. 
+* LiveRamp Audiences doesn't support SFTP transfers in the EMEA region. This destination only supports the US region for SFTP file transfers.
+* The Delivery Overviews/Event Delivery tabs do not reflect the correct status of the file transfers to either S3 or SFTP. 
 
 ## Trait Enrichment 
 
-Use Trait Enrichment to access Segment profile traits when you sync Audiences to Destinations. With Trait Enrichment, you can use custom, SQL, computed, and predictive traits to enrich the data you map to your destinations.
+Use Trait Enrichment to access Segment profile traits when you sync Audiences to destinations. With Trait Enrichment, you can use custom, SQL, computed, and predictive traits to enrich the data you map to your destinations.
 
 > info "Trait Enrichment in beta"
 > Trait Enrichment is in beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
 
 Trait Enrichment setup 
 
-1. Confirm that **Send Track** is toggled on and select Customized Setup. Select **Add Trait**, select the traits you want to sync, and click **Save**. 
+1. Confirm that **Send Track** is toggled on and select **Customized Setup**. Select **Add Trait**, select the traits you want to sync, and click **Save**. 
 
 ![Alt text](traitEnrichment-EngageSettings.png)
 
-2. Update the **Identifier Data** Field in your destination **Audience Entered** Mapping (either SFTP or S3). 
+2. Update the **Identifier Data** field in your destination **Audience Entered** mapping (either SFTP or S3). 
 - To update a trait field mapping, click on the **Select event variable** section and in the dropdown search for `properties`, followed by your trait. For example, `properties.firstName`. If no matches are found, use `properties.TRAIT` as an event variable. 
 
 ![Alt text](traitEnrichment-Mappings.png)