Fix some typos

Author: pwseg

src/engage/campaigns/mobile-push/index.md

@@ -10,7 +10,7 @@ This page walks you through the process of setting up mobile push notifications
 
 ## Overview
 
-You'll set up mobile push in four steps:
+You'll set up mobile push in four stages:
 
 1. [Set up analytics for mobile push](#1-set-up-analytics-for-mobile-push).
 2. [Add the Engage SDK plugin](#2-add-the-engage-sdk-plugin).
@@ -124,9 +124,7 @@ You can add the Engage SDK plugin using either Xcode or `Package.swift`.
     analytics.add(plugin: engage)
     ```
 
-3. Add or modify methods to `AppDelegate`:
-
-To start receiving and handling mobile push notifications, add or modify the following methods in your `AppDelegate`:
+3. To start receiving and handling mobile push notifications, add or modify the following methods in your `AppDelegate`:
 
 ```swift
    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
@@ -249,7 +247,7 @@ With your server key copied, finish steps 5 and 6 in the Twilio documentation.
 > success ""
 > If you've already configured SMS services for Twilio Engage, you can skip this step.
 
-Follow these steps to set up mobile push in Twilio Engage and complete mobile onboarding:
+Follow these steps to set up mobile push in Twilio Engage and complete mobile push onboarding:
 
 1. Follow the steps in the [Create and configure Twilio SMS services documentation](/docs/engage/onboarding/#stage-3-create-and-configure-twilio-sms-services).
 2. Return to your Segment workspace and navigate to **Engage > Engage settings**.

src/engage/campaigns/mobile-push/push-campaigns.md

@@ -9,7 +9,7 @@ Some knowledge of the Journeys product will benefit you as you read through this
 
 ## How Engage campaigns work
 
-Twilio Engage uses Journeys to campaigns.  With Journeys, you add conditions and steps that trigger actions like sending an email, an SMS, or a mobile push.
+Twilio Engage uses Journeys to send campaigns.  With Journeys, you add conditions and steps that trigger actions like sending an email, an SMS, or a mobile push.
 
 You’ll build and then send your campaign in three stages:
 
@@ -23,7 +23,7 @@ Because Engage campaigns exist within Journeys, begin by creating a journey:
 
 1. In Engage, select **Journeys**, then click **New Journey**.
 2. Name your journey and select its entry settings.
-3. Click **Build Journey** to create the Journey.
+3. Click **Build Journey** to create the journey.
 
 ### Add a Journey condition
 
@@ -63,4 +63,4 @@ Follow these steps to test your mobile push:
     - You can add recipients using an email address or user ID. 
 3. Click **Send test push**.
 
-Segment verifies that the the profile you're sending a test to has push tokens enabled, then sends the test. If the test push doesn't work as expected, confirm that the profile you're sending to has enabled push tokens.
+Segment verifies that the profile you're sending a test to has push tokens enabled, then sends the test. If the test push doesn't work as expected, confirm that the profile you're sending to has enabled push tokens.

src/engage/content/mobile-push.md

@@ -49,11 +49,12 @@ Follow these steps to test your mobile push:
 1. Choose a template to test:
     - For new templates, select **Test** once you've finished building a template. 
     - For existing templates, navigate to **Engage > Content > Push**, select the template you want to test, then click **Test**.
+    - Mobile push templates have a content size limit of 4KB.
 2. Choose a messaging service and add a recipient.
     - You can add recipients using an email address or user ID. 
 3. Click **Send test push**.
 
-Segment verifies that the the profile you're sending a test to has push tokens enabled, then sends the test. If the test mobile push doesn't work as expected, confirm that the profile you're sending to has enabled push tokens.
+Segment verifies that the profile you're sending a test to has push tokens enabled, then sends the test. If the test mobile push doesn't work as expected, confirm that the profile you're sending to has enabled push tokens.
 
 ## Personalize with merge tags