Acrolinx

Author: gitName

learn-pr/azure/monitor-github-events-with-a-function-triggered-by-a-webhook/includes/10-summary.md

@@ -1,4 +1,4 @@
-In this module, you've learned about the benefits of webhooks. You created a function in Azure Functions triggered by a webhook. You saw how to set up a webhook for a GitHub repository and how to trigger your function with a GitHub event. Finally, you learned how to protect your function using a secret.
+In this module, you learned about the benefits of webhooks. You created a function in Azure Functions triggered by a webhook. You saw how to set up a webhook for a GitHub repository and how to trigger your function with a GitHub event. Finally, you learned how to protect your function using a secret.
 
 [!include[](../../../includes/azure-sandbox-cleanup.md)]
 

learn-pr/azure/monitor-github-events-with-a-function-triggered-by-a-webhook/includes/5-exercise-setup-webhook-for-github-repo.md

@@ -1,4 +1,4 @@
-In this exercise, you'll set up a webhook for a GitHub repository. You'll learn how to listen for specific events (in this case, the *Gollum* event), and how to make the webhook callback in your function when the event is triggered.
+In this exercise, you set up a webhook for a GitHub repository. You learn how to listen for specific events; in this case, the *Gollum* event. You also learn how to make the webhook callback in your function when the event is triggered.
 
 ## Setup
 
@@ -24,7 +24,7 @@ In this exercise, you'll set up a webhook for a GitHub repository. You'll learn
 
 **Gollum** is the name of a GitHub event that is fired whenever a page in a repository's wiki is created or updated.
 
-1. On the home page in the Wiki view is a **Pages** sidebar that lists the pages in your repo. Select **Home** to display the home page.
+1. On the home page in the Wiki view, there's a **Pages** sidebar that lists the pages in your repo. Select **Home** to display the home page.
 
 1. On the home page, in the top menu bar, select **Settings**. The **Settings** pane appears.
 
@@ -72,7 +72,7 @@ In this exercise, you'll set up a webhook for a GitHub repository. You'll learn
 
 1. In the list, select the top (latest) delivery entry by selecting the ellipsis (**...**).
 
-    You'll see the **Headers** section, including the *Event*:
+    You should see the **Headers** section, including the *Event*:
 
     ```json
     Request URL: https://testwh123456.azurewebsites.net/api/HttpTrigger1?code=aUjXIpqdJ0ZHPQuB0SzFegxGJu0nAXmsQBnmkCpJ6RYxleRaoxJ8cQ%3D%3D
@@ -87,7 +87,7 @@ In this exercise, you'll set up a webhook for a GitHub repository. You'll learn
     X-GitHub-Hook-Installation-Target-Type: repository
     ```
 
-   You'll also see that the **Payload** section contains information indicating that your wiki page was edited. The payload contains **pages**, **repository**, and **sender** sections, which should look something like the following example:
+   You should also see that the **Payload** section contains information indicating that your wiki page was edited. The payload contains **pages**, **repository**, and **sender** sections, which should look something like the following example:
 
     ```json
         "pages": [
@@ -113,4 +113,4 @@ In this exercise, you'll set up a webhook for a GitHub repository. You'll learn
 
 1. Under the **Recent Deliveries** tab, select the **Response** tab.
 
-    You'll see the response message generated by the Azure function. For this example, the body should contain the message: *This HTTP triggered function executed successfully. Pass a name in the query string or in the request body for a personalized response*.
+    You should see the response message generated by the Azure function. For this example, the body should contain the message: *This HTTP triggered function executed successfully. Pass a name in the query string or in the request body for a personalized response*.

learn-pr/azure/monitor-github-events-with-a-function-triggered-by-a-webhook/includes/6-trigger-function-with-github-event.md

@@ -1,8 +1,8 @@
 The GitHub *Gollum* event lets you listen for wiki updates. When this event occurs, your Azure HttpTrigger function is triggered, and you can parse the payload to retrieve and process the data that was sent.
 
-You've shown your IT department that you can listen for *Gollum* events on your company's GitHub repository by setting up a webhook. You've also demonstrated how Azure Function apps enable you to run code when a function receives a webhook request.
+You showed your IT department that you can listen for *Gollum* events on your company's GitHub repository by setting up a webhook. You also demonstrated how Azure Function apps enable you to run code when a function receives a webhook request.
 
-In this unit, we'll examine the payload from the *Gollum* event so we can update our function to parse it correctly.
+In this unit, we examine the payload from the *Gollum* event so we can update our function to parse it correctly.
 
 ## Gollum event payload
 
@@ -48,7 +48,7 @@ For example, a payload might look like the following code.
 }
 ```
 
-This information is passed as the body of an HTTP POST request. We'll need to update our function logic to parse and process this information correctly.
+This information is passed as the body of an HTTP POST request. We need to update our function logic to parse and process this information correctly.
 
 ## Parse information from the Gollum event
 

learn-pr/azure/monitor-github-events-with-a-function-triggered-by-a-webhook/includes/7-exercise-trigger-function-with-github-event.md

@@ -1,4 +1,4 @@
-In this exercise, you'll update your function to parse information from the GitHub webhook payload, and display the results.
+In this exercise, you update your function to parse information from the GitHub webhook payload, and display the results.
 
 ## Update your function to parse the webhook payload
 
@@ -28,7 +28,7 @@ In this exercise, you'll update your function to parse information from the GitH
     }
     ```
 
-    This code retrieves the event type from the request header, and the title and action fields from the message body. This information indicates that page has changed, and whether it has been edited or newly created. The code then constructs a response that summarizes the action. Here's what the JavaScript should look like:
+    This code retrieves the event type from the request header, and the title and action fields from the message body. This information indicates that page changed, and whether it's been edited or newly created. The code then constructs a response that summarizes the action. Here's what the JavaScript should look like:
 
     ```JavaScript
     module.exports = async function (context, req) {
@@ -77,7 +77,7 @@ In this exercise, you'll update your function to parse information from the GitH
 
 1. Select the latest (top) delivery entry (*redelivery*) by selecting its ellipsis button (**...**).
 
-1. Select the **Response** tab. You'll see how the webhook has triggered your function, which then parsed the information, and sent a response similar to the following text:
+1. Select the **Response** tab. You should see how the webhook has triggered your function, which then parsed the information, and sent a response similar to the following text:
 
     ```text
     Page is Home, Action is edited, Event Type is gollum

learn-pr/azure/monitor-github-events-with-a-function-triggered-by-a-webhook/includes/8-secure-webhook-payloads-with-secret.md

@@ -1,6 +1,6 @@
 After your function is configured to receive payloads, it listens for any payload sent to the endpoint you configured. For security reasons, you might want to limit requests to those coming from GitHub. There are a few ways to go about this. For example, you could opt to approve requests from GitHub's IP address. An easier method is to set up a secret token and validate the request using this token.
 
-In the example scenario, your IT Department's management are happy with the webhook-triggered function that you've created in an Azure Functions app. All of the information regarding updates to the company wiki are being parsed by that function and sent to the business each time the *Gollum* event is triggered. The management has asked how secure is the information passed from GitHub. They've asked you to find a way to secure the information, and verify it's GitHub that is sending updates.
+In the example scenario, your IT Department's management is happy with the webhook-triggered function that you've created in an Azure Functions app. All of the information regarding updates to the company wiki are being parsed by that function and sent to the business each time the *Gollum* event is triggered. The management has asked how secure is the information passed from GitHub. They've asked you to find a way to secure the information, and verify it's GitHub that is sending updates.
 
 In this unit, you'll learn how to secure your webhook payload with a secret and validate payloads from GitHub.
 

learn-pr/azure/monitor-github-events-with-a-function-triggered-by-a-webhook/index.yml

@@ -10,7 +10,7 @@ metadata:
   ms.service: azure-functions
   manager: susanpotter
 title: Monitor GitHub events by using a webhook with Azure Functions
-summary: Webhooks offer a lightweight mechanism for your app to be notified by another service when something of interest happens. In this module. you'll learn how to trigger an Azure function with a GitHub webhook and parse the payload for insights.
+summary: Webhooks offer a lightweight mechanism for your app to be notified by another service when something of interest happens. In this module, you'll learn how to trigger an Azure function with a GitHub webhook and parse the payload for insights.
 abstract: | 
   In this module, you will:
   - Trigger your function with a webhook.