Merge pull request #6241 from segmentio/housekeeping-fixes

Typo Housekeeping

Author: pwseg

src/_data/actions/braze-cloud.yml

@@ -173,7 +173,7 @@ actions:
       description: Set to true to use the Braze API in "Update Only" mode.
       default: false
   - action: Track Purchase
-    blurb: Track Purchase sends Braze a Track Purchase call when the destination recieves any event that matches the specified name.
+    blurb: Track Purchase sends Braze a Track Purchase call when the destination receives any event that matches the specified name.
     fields:
     - name: Time
       description: The timestamp of when the event occured.

src/_data/actions/braze-web.yml

@@ -221,7 +221,7 @@ actions:
       description: Set to true to use the Braze API in "Update Only" mode.
       default: false
   - action: Track Purchase
-    blurb: Track Purchase sends Braze a Track Purchase call when the destination recieves any event named `Order Completed`.
+    blurb: Track Purchase sends Braze a Track Purchase call when the destination receives any event named `Order Completed`.
     fields:
     - name: Time
       description: The timestamp of when the event occured.

src/connections/destinations/catalog/braze/index.md

@@ -353,7 +353,7 @@ The `inAppMessages` parameter will be an array of [`appboy.ab.InAppMessage`](htt
     // When you get the push token
     String receivedToken;
 
-    appboyPushToken = recievedToken;
+    appboyPushToken = receivedToken;
     if (appboyInitialized) {
       Appboy.getInstance(getContext()).registerAppboyPushMessages(appboyPushToken);
     }

src/connections/destinations/catalog/google-analytics/index.md

@@ -839,7 +839,7 @@ To enable user deletion for Google Universal Analytics:
 2. Authenticate your Google Universal Analytics account using OAuth.
 
 > info ""
-> **NOTE:** Segment supports user deletion for Google Universal Analytics in Universal Analytics and not Classic Analytics. You can send user deletion requests using a `userId` through the Privacy Tool. This means you must  have the User-Id feature enabled in your Google Universal Analytics Property within the your Google Universal Analytics dashboard and have Segment sending your Property `userIds` by enabling the setting **Send User-ID to GA**.
+> **NOTE:** Segment supports user deletion for Google Universal Analytics in Universal Analytics and not Classic Analytics. You can send user deletion requests using a `userId` through the Privacy Tool. This means you must  have the User-Id feature enabled in your Google Universal Analytics Property within your Google Universal Analytics dashboard and have Segment sending your Property `userIds` by enabling the setting **Send User-ID to GA**.
 
 
 

src/connections/destinations/catalog/split/index.md

@@ -94,4 +94,4 @@ Each event may have a `value` field which you would like to use in Split metric
 
 If you would not like Split to receive `track` calls, you can configure in your integration settings in Split.
 
-_**NOTE:** Split currently does not capture the properties of the your track events. The Split team is currently working to accept these properties for use in creating metrics in Split._
+_**NOTE:** Split currently does not capture the properties of your track events. The Split team is currently working to accept these properties for use in creating metrics in Split._

src/connections/sources/catalog/cloud-apps/engage-events/index.md

@@ -87,7 +87,7 @@ SendGrid powers Engage email delivery. For more information, view [SendGrid's Ev
 
 | Event                        | Definition                                            |
 | ---------------------------- | ----------------------------------------------------- |
-| WhatsApp Message Queued      | The WhatsApp message creation requested was recieved. |
+| WhatsApp Message Queued      | The WhatsApp message creation requested was received. |
 | WhatsApp Message Accepted    | The WhatsApp message creation request was accepted.   |
 | WhatsApp Message Sending     | The WhatsApp message is being sent.                   |
 | WhatsApp Message Sent        | The WhatsApp message was successfully sent.           |

src/connections/sources/catalog/cloud-apps/freshchat/index.md

@@ -20,7 +20,7 @@ Before you start, make sure that you have admin rights in Freshchat and [Workspa
 5. Copy the Write key from the Segment UI to use in Freshchat.
 6. Log in to your Freshchat account.
 7. In Freshchat, navigate to Admin → Marketplace Apps → Segment Integration.
-8. Paste the your Segment write key and click **Authenticate account** to connect.
+8. Paste your Segment write key and click **Authenticate account** to connect.
 9. After your account is authenticated, select one or more of the following events to send to Segment:
     - On Agent Activity Create
     - On Conversation Create

src/connections/spec/best-practices-identify.md

@@ -91,7 +91,7 @@ You can see in this full page event, the `anonymousId` is populated, and the `us
       "title": "Home Page",
       "url": "https://somesite.com"
     },
-  "recievedAt": "2020-04-23T22:38:48.55Z",
+  "receivedAt": "2020-04-23T22:38:48.55Z",
   "sentAt": "2020-04-23T22:38:48.55Z",
   "timestamp": "2020-04-23T22:38:48.55Z",
   "type": "page",
@@ -144,7 +144,7 @@ You'll notice the Identify call contains no `userId`. These traits will be assoc
       "title": "Home Page",
       "url": "https://somesite.com"
     },
-  "recievedAt": "2020-04-23T22:38:48.55Z",
+  "receivedAt": "2020-04-23T22:38:48.55Z",
   "sentAt": "2020-04-23T22:38:48.55Z",
   "timestamp": "2020-04-23T22:38:48.55Z",
   "traits"{
@@ -210,7 +210,7 @@ After you fire the Identify call with the `userId`, you'll notice that the paylo
       "title": "Home Page",
       "url": "https://somesite.com"
     },
-  "recievedAt": "2020-04-23T22:38:48.55Z",
+  "receivedAt": "2020-04-23T22:38:48.55Z",
   "sentAt": "2020-04-23T22:38:48.55Z",
   "timestamp": "2020-04-23T22:38:48.55Z",
   "traits"{

src/connections/storage/warehouses/warehouse-syncs.md

@@ -70,7 +70,7 @@ When you disable a source, collection or property, Segment no longer syncs data
 > For each warehouse only the first 5,000 collections per source and 5,000 properties per collection are visible in the Selective Sync user interface. [Learn more about the limits](#selective-sync-user-interface-limits).
 
 > warning ""
-> Disabling the `recieved_at` column will cause your syncs to fail, as all tables use `receieved_at` as the sort key.
+> Disabling the `received_at` column will cause your syncs to fail, as all tables use `receieved_at` as the sort key.
  
 ### When to use Selective Sync
 

src/engage/quickstart.md

@@ -89,7 +89,7 @@ After you build your audience, click **Preview Results** to see the total number
 
 ## Step 6:  Connect the Audience to a Destination
 
-After you create your test audience, click **Select Destinations**. Engage guides you through configuration steps to set up a destination for your audience. If you don't already have destinations configured for the Engage space, the you are prompted to select one or more. Finally, enter a name for the audience.
+After you create your test audience, click **Select Destinations**. Engage guides you through configuration steps to set up a destination for your audience. If you don't already have destinations configured for the Engage space, you are prompted to select one or more. Finally, enter a name for the audience.
 
 The larger the audience you're creating, the longer it takes Engage to successfully compute the Audience. The Audience page shows a status that indicates if the audience is still being calculated. When the total number of users appears in the Audience overview, as in the example screenshot below, the audience has successfully finished computing, and Engage then sends the audience to the destination you selected.