Line edits2

Author: lootle1

learn-pr/azure/build-serverless-api-with-functions-api-management/includes/1-introduction.md

@@ -6,7 +6,7 @@ In this module, you learn how to use API Management to assemble multiple microse
 
 ## Learning objectives
 
-In this module, you will:
+In this module, you'll:
 
 - Identify the value of Azure API Management in a serverless application.
 - Import an Azure Function App as an API in Azure API Management.

learn-pr/azure/build-serverless-api-with-functions-api-management/includes/2-import-function-app-api-management.md

@@ -2,25 +2,25 @@ The Azure API Management service enables you to construct an API from a set of d
 
 In your online store, each part of the application is implemented as a microservice - one for the product details, one for order details, and so on. A separate team manages each microservice, and each team uses continuous development and delivery to update and deploy their code regularly. You want to find a way to assemble these microservices into a single product and then manage that product centrally.
 
-In this unit, you learn how Azure API Management is useful in a serverless architecture, by building single APIs from individual microservices.
+In this unit, you learn how Azure API Management is useful in a serverless architecture by building single APIs from individual microservices.
 
 ## Serverless architecture and microservices
 
-Microservices are a popular approach to the architecture of distributed applications. When you build an application as a collection of microservices, you create many different small services. Each service has a defined domain of responsibility, and is developed, deployed, and scaled independently. This modular architecture results in an application that is easier to understand, improve, and test. It also makes continuous delivery easier, because you change only a small part of the whole application when you deploy a microservice.
+Microservices are a popular approach to the architecture of distributed applications. When you build an application as a collection of microservices, you create many different small services. Each service has a defined domain of responsibility and is developed, deployed, and scaled independently. This modular architecture results in an application that is easier to understand, improve, and test. It also makes continuous delivery easier, because you change only a small part of the whole application when you deploy a microservice.
 
 Another complementary trend in distributed software development is serverless architecture. In this approach, a host organization publishes a set of services that developers can use to run their code. The developers don't have to concern themselves with the supporting hardware, operating systems, underlying software, and other infrastructure. Instead, the code runs in stateless computing resources triggered by requests. Costs are only incurred when the services execute, so you don't pay much for services that are rarely used.
 
 ## Azure Functions
 
-Azure Functions is a service that enables serverless architectures in Azure. You can write functions, without worrying about the supporting infrastructure, in many different languages, including C#, Java, JavaScript, PowerShell, and Python. You can also use libraries from NuGet and the Node Package Manager (npm), and authenticate users with the OAuth standard from providers such as Active Directory, Facebook, Google, and Microsoft Account.
+Azure Functions is a service that enables serverless architectures in Azure. You can write functions without worrying about the supporting infrastructure in many different languages, including C#, Java, JavaScript, PowerShell, and Python. You can use libraries from NuGet and the Node Package Manager (npm). You can also authenticate users with the OAuth standard from providers such as Active Directory, Facebook, Google, and Microsoft Account.
 
-When you write a function, you choose a template to use, depending on how you want to trigger your code. For example, if you want to execute the function in response to an HTTP request, use the **HTTPTrigger** template. You can use other templates to execute when there are new messages in a queue, a Blob storage container, or on a predefined schedule.
+When you write a function, you choose a template to use depending on how you want to trigger your code. For example, if you want to execute the function in response to an HTTP request, use the **HTTPTrigger** template. You can use other templates to execute when there are new messages in a queue, a Blob storage container, or on a predefined schedule.
 
 When you use Azure Functions in a Consumption Plan, you're charged only for the time that your code runs.
 
 ## Azure API Management
 
-Azure API Management is a fully managed cloud service that you can use to publish, secure, transform, maintain, and monitor APIs. It helps organizations publish APIs to external, partner, and internal developers to unlock the potential of their data and services. API Management handles all the tasks involved in mediating API calls. Including, request authentication and authorization, rate limit and quota enforcement, request and response transformation, logging and tracing, and API version management. API Management enables you to create and manage modern API gateways for existing backend services no matter where they're hosted.
+Azure API Management is a fully managed cloud service that you can use to publish, secure, transform, maintain, and monitor APIs. It helps organizations publish APIs to external, partner, and internal developers to unlock the potential of their data and services. API Management handles all the tasks involved in mediating API calls including request authentication and authorization, rate limit and quota enforcement, request and response transformation, logging and tracing, and API version management. API Management enables you to create and manage modern API gateways for existing backend services no matter where they're hosted.
 
 Because you can publish Azure Functions through API Management, you can use them to implement a microservices architecture; each function implements a microservice. By adding several functions to a single API Management product, you can build those microservices into an integrated distributed application. Once the application is built, you can use API Management policies to implement caching or ensure security requirements.
 

learn-pr/azure/build-serverless-api-with-functions-api-management/includes/3-exercise-import-function-app-api-management.md

@@ -47,9 +47,7 @@ Now, let's test the ProductDetails function to see how it behaves before we add
 
 1. On the **Input** tab, in the **HTTP method** field dropdown list, select **GET**.
 
-1. Under **Query**, Select **Add parameter**
-
-1. In the **Name** field, enter *id*, and in the **Value** field, enter *3*, and then select **Run**.
+1. Under **Query** in the **Name** field, enter *id*, and in the **Value** field, enter *3*. Then select **Run**.
 
    :::image type="content" source="../media/3-test-input.png" alt-text="Screenshot of the input pane for Test + Run, with the input parameter for the HTTP GET method highlighted.":::
 
@@ -59,7 +57,7 @@ Now, let's test the ProductDetails function to see how it behaves before we add
 
     Optionally, you can also test the function by inputting ID values 1 and 2.
 
-1. Select **Close** to close the Input Output tabs for Code + Test.
+1. Select **Close** to close the Input/Output tabs for Code + Test.
 
 1. On the command bar of the ProductDetails Code + Test pane, select **Get function URL**. Notice that the URL subdomain is the name of your function app, followed by the  **azurewebsites.net** domain.
 
@@ -73,14 +71,14 @@ After the function app is deployed and tested, let's export it as an API using A
 1. In the resource menu, select **All resources**. The **All resources** pane appears.
 
 1. Sort the list of resources by type. Notice you have an OrderFunction app and a ProductFunction app.
- 
+
 1. Select the **ProductFunction** function app.
 
 1. In the Function App menu, scroll to the **API** category, and then select **API Management**. The **API Management** pane for ProductFunction function app appears.
 
     :::image type="content" source="../media/3-create-api.png" alt-text="Screenshot showing menu selection to open the API Management app service.":::
 
-1. Under the **API Management** field, select **Create new**. The **Install API Management gateway** pane appears.
+1. Under the **API Management** field, select **Create new**. The **Create API Management service** pane appears.
 
     :::image type="content" source="../media/3-api-details.png" alt-text="Screenshot showing settings for an API Management service.":::
 
@@ -96,7 +94,7 @@ After the function app is deployed and tested, let's export it as an API using A
     | Administrator email | Enter an email address. |
     | Pricing tier | Consumption (99.95% SLA) |
 
-1. Select **Next: Monitoring** and clear the **Application Insights** option.
+1. Select **Next: Monitor + secure** and clear the **Application Insights** option.
 
 1. Select **Review + Create**. When the validation completes, select **Create** to create a linked API Management instance. Allow several minutes for the export to complete.
 

learn-pr/azure/build-serverless-api-with-functions-api-management/includes/4-import-additional-functions-existing-api-gateway.md

@@ -1,6 +1,6 @@
 Microservices architectures can be difficult to manage. For example, you might rely on separate teams implementing cross-cutting requirements, such as security, in a consistent way.
 
-In the online store, your developer teams built the product details and order details microservices at different host URLs. Also the order details service responds by using XML. You want to ensure that all responses are in JSON format to make things easier for the client app developers.
+In the online store, your developer teams built the product details and order details microservices at different host URLs. Also, the order details service responds by using XML. You want to ensure that all responses are in JSON format to make things easier for the client app developers.
 
 In this unit, you learn about the features of API Management. You can use these features to integrate different microservices and present them to client applications with consistent behavior at a single URL.
 

learn-pr/azure/build-serverless-api-with-functions-api-management/includes/5-exercise-import-additional-functions-existing-api-gateway.md

@@ -12,13 +12,11 @@ Before we add the Orders function app to the API, let's test the function it hos
 
 1. From the list of functions for your function app, select **OrderDetails**. The **OrderDetails** Function Overview pane appears.
 
-1. In the Order Details menu, under **Developer**, select **Code + Test**. The **Code + Test** pane for the OrderDetails function appears, showing the contents of the `function.json` file.
+1. In Order Details, the **Code + Test** pane shows the contents of the `function.json` file. On the command bar, select **Test/Run**. The **Input** parameters tab for your OrderDetails function appears.
 
     :::image type="content" source="../media/5-test-order-details.png" alt-text="OrderDetails JSON code, with Code + Test in menu and Test/Run in command bar highlighted.":::
 
-1. On the command bar, select **Test/Run**.  The **Input** parameters tab for your OrderDetails function appears.
-
-1. In the **HTTP method** field, select **GET** from the dropdown list, and then under **Query**, select **Add parameter**, and in the **Name** field, enter *name*, and in the **Value** field, enter *Chiba* (value is case-sensitive), and then select **Run**.
+1. In the **HTTP method** field, select **GET** from the dropdown list. Under **Query** in the **Name** field enter *name*. In the **Value** field enter *Chiba* (value is case-sensitive) and then select **Run**.
 
 1. A log console opens and displays the status of the request. The **Output** tab displays the HTTP response code and content in JSON format.
 
@@ -48,15 +46,15 @@ In this step, we add the Order function to the API Management resource that we c
 
 1. To select your function app, select **Browse**. The **Import Azure Functions** pane appears.
 
-1. On the **Configure required settings** field, select **Select**.
+1. On the **Configure required settings** field choose **Select**.
 
     ![Screenshot of the Import Azure Functions dialog box with Configure required settings field and Select button highlighted.](../media/5-import-azure-function-app-03-inline.png)(../media/5-import-azure-function-app-03-expanded.png#lightbox)
 
     The **Select Azure Function App** pane appears.
 
-1. Select **OrderFunctionNNNNNNN**, and then select **Select**. The **Import Azure Functions** pane reappears with your OrderDetails function app configured.
+1. Select your **OrderFunction**, and then choose **Select**. The **Import Azure Functions** pane reappears with your OrderDetails function app configured.
 
-1. Ensure that **OrderDetails** is checked, and then, at the bottom of the page, select **Select** to add the function. The **Create from Function App** dialog box appears.
+1. Ensure that **OrderDetails** is checked, and then at the bottom of the page choose **Select** to add the function. The **Create from Function App** dialog box appears.
 
 1. Replace the value in the **API URL suffix** field with *orders*. Notice how this change updates the Base URL. Select **Create** to create your API.
 
@@ -68,7 +66,7 @@ In this step, we add the Order function to the API Management resource that we c
 
 Now that we added OrderDetails to our API, let's test it by using the API Management tools in the Azure portal.
 
-1. On the OrderFunctionNNNNNN APIs Design tab, under **All operations**, select **GET OrderDetails**, and then select the **Test** tab.
+1. On your **OrderFunction** APIs Design tab under **All operations**, select **GET OrderDetails**, and then select the **Test** tab.
 
 1. In the **Query parameters** section, select **Add parameter**, and enter *name* in the **NAME** field and *Chiba* and in the **VALUE** field. Select **Send**.
 

learn-pr/azure/build-serverless-api-with-functions-api-management/includes/6-summary.md

@@ -6,4 +6,4 @@ In this module, you published a serverless API with two Azure Functions apps in
 
 - [An introduction to Azure Functions](/azure/azure-functions/functions-overview)
 - [API Management documentation](/azure/api-management/)
-- [Import an Azure Function App as an API in Azure API Management](/azure/api-management/import-function-app-as-api)
+- [Import an Azure Function App as an API in Azure API Management](/azure/api-management/import-function-app-as-api)