diff --git a/src/connections/spec/semantic.md b/src/connections/spec/semantic.md
index 795c306f6a..21387cb394 100644
--- a/src/connections/spec/semantic.md
+++ b/src/connections/spec/semantic.md
@@ -4,7 +4,7 @@ title: 'Spec: Semantic Events'
 
 One of the core components of the Segment [Spec](/docs/connections/spec) is the [Track](/docs/connections/spec/track) call. It describes any arbitrary event that the user has triggered. For some industry verticals and applications, Segment has standardized event names. For Ecommerce tracking, for example, there are **specific event names and properties** that we recognize semantically. This semantic meaning allows Segment to specially recognize and transform key events before sending them off to each different tool.
 
-There are a few places where Segment has standardized event names and properties already:
+Segment currently standardizes event names and properties in the following places:
 
 - [Mobile](/docs/connections/spec/mobile)
 - [A/B Testing](/docs/connections/spec/ab-testing)
@@ -12,5 +12,3 @@ There are a few places where Segment has standardized event names and properties
 - [Email](/docs/connections/spec/email)
 - [Live Chat](/docs/connections/spec/live-chat)
 - [Video](/docs/connections/spec/video)
-
-In the future Segment plans to standardize event names from other data sources as well.
diff --git a/src/connections/test-connections.md b/src/connections/test-connections.md
index 3270536975..d013c1bfca 100644
--- a/src/connections/test-connections.md
+++ b/src/connections/test-connections.md
@@ -1,9 +1,9 @@
 ---
-title: Testing Connections
+title: Testing connections
 ---
 
-Segment provides these 2 testing tools to enable you to test your connections between Segment and your destination:
-* [Event Tester](#event-tester): Test all of your enabled mappings within a destination. 
+Segment provides two tools for validating the connection between Segment and a destination:
+* [Event Tester](#event-tester): Test all enabled mappings within a destination. 
 * [Mappings Tester](#mappings-tester): Test a single mapping configuration for your destination. 
 
 Both testing tools share the same underlying testing infrastructure, which ensures consistent results across your testing workflows. The results from both testers display API requests, responses, and success/failure status to help you diagnose any issues.
@@ -36,7 +36,7 @@ The Event Tester sends a real event that appears in your end tool alongside your
 To use the Event Tester: 
 1. Navigate to **Connections > Destinations** and select your destination.
 2. Click the **Event Tester** tab. 
-3. Select the type of test event. You can choose from: Track, Identify, Page, Screen, Group. 
+3. Select the type of test event. You can choose from: Track, Identify, Page, Screen, and Group. 
 4. Enter your test event payload. You can type in your own event or choose from **Load event from source** or **Generate sample event**.
    * **Load event from source**: Segment loads an event based on your source. 
    * **Generate sample event**: Segment generates a sample event for you. 
@@ -77,7 +77,7 @@ To use the Mapppings Tester:
 
 #### The Event Tester experienced an error when sending my event. Why did this happen?
 
-If you experience an error, [let Segment know](mailto:friends@segment.com) and the Segment team will help you troubleshoot the issue.
+If you experience an error, [contact Segment support](mailto:friends@segment.com) and we'll help you troubleshoot the issue.
 
 #### Is this feature available for Data Lakes?
 
diff --git a/src/unify/profiles-sync/overview.md b/src/unify/profiles-sync/overview.md
index eb9e2e038f..081631ec56 100644
--- a/src/unify/profiles-sync/overview.md
+++ b/src/unify/profiles-sync/overview.md
@@ -1,5 +1,5 @@
 ---
-title: Profiles Sync Overview
+title: Profiles Sync overview
 plan: unify
 ---