Update publish-notifications.md

Author: Ja-Dunn

articles/managed-applications/publish-notifications.md

@@ -14,12 +14,12 @@ ms.date: 11/01/2019
 Azure managed application notifications allow publishers to automate actions based on lifecycle events of the managed application instances. Publishers can specify custom notification webhook endpoints to receive event notifications about new and existing managed application instances. Publishers can set up custom workflows at the time of application provisioning, updates, and deletion.
 
 ## Getting started
-To start receiving managed applications, spin up a public HTTPS endpoint and specify it when you publish the service catalog application definition or the Azure Marketplace offer.
+To start receiving managed applications, spin up a public HTTPS endpoint and specify it when you publish the service catalog application definition or Azure Marketplace offer.
 
 Here are the recommended steps to get started quickly:
 1. Spin up a public HTTPS endpoint that logs the incoming POST requests and returns `200 OK`.
 2. Add the endpoint to the service catalog application definition or Azure Marketplace offer as explained later in this article.
-3. Create a managed application instance that references the application definition or the Azure Marketplace offer.
+3. Create a managed application instance that references the application definition or Azure Marketplace offer.
 4. Validate that the notifications are being received.
 5. Enable authorization as explained in the **Endpoint authentication** section of this article.
 6. Follow the instructions in the **Notification schema** section of this article to parse the notification requests and implement your business logic based on the notification.
@@ -191,4 +191,4 @@ To secure the webhook endpoint and ensure the authenticity of the notification:
 
 ## Notification retries
 
-The Managed Application Notification service expects a `200 OK` response from the webhook endpoint to the notification. The notification service will retry if the webhook endpoint returns an HTTP error code greater than or equal to 500, if it returns an error code of 429, or if the endpoint is temporarily unreachable. If the webhook endpoint doesn't become available within 10 hours, the notification message will be dropped and the retries will stop.
+The Managed Application Notification service expects a `200 OK` response from the webhook endpoint to the notification. The notification service will retry if the webhook endpoint returns an HTTP error code greater than or equal to 500, if it returns an error code of 429, or if the endpoint is temporarily unreachable. If the webhook endpoint doesn't become available within 10 hours, the notification message will be dropped and the retries will stop.