Line edits4

Author: lootle1

learn-pr/azure/introduction-to-azure-api-management/includes/1-introduction.md

@@ -1,10 +1,10 @@
-Publishing an application programming interface (API) is a great way to increase market share, generate revenue, and foster innovation. However, maintaining even one API brings significant challenges such as onboarding users, managing revisions, implementing security, and running analytics
+Publishing an application programming interface (API) is a great way to increase market share, generate revenue, and foster innovation. However, maintaining even one API brings significant challenges such as onboarding users, managing revisions, implementing security, and running analytics.
 
-Imagine that your organization publishes multiple APIs for different types of users including partners, developers, and employees. These APIs are used in multiple settings, including mobile apps, web apps, and Internet of Things (IoT) devices.
+Imagine that your organization publishes multiple APIs for different types of users, including partners, developers, and employees. These APIs are used in multiple settings, including mobile apps, web apps, and Internet of Things (IoT) devices.
 
 :::image type="content" source="../media/1-introduction-before.png" alt-text="Multiple APIs connect to multiple servers, where each API maintains its own set of users, security policies, and analytics data." lightbox="../media/1-introduction-before.png":::
 
-Microsoft Azure API Management reduces the complexity of managing all your API traffic, and it offers intuitive portals for managing your APIs as well as surfacing them to developers. It also provides tools for implementing security, managing revisions, and performing analytics.
+Microsoft Azure API Management reduces the complexity of managing all your API traffic. It offers intuitive portals for managing your APIs as well as surfacing them to developers. It also provides tools for implementing security, managing revisions, and performing analytics.
 
 :::image type="content" source="../media/1-introduction-after.png" alt-text="Azure API Management acts as a 'front door' for all of an organization's APIs. API calls are then routed to the server where the API is deployed." lightbox="../media/1-introduction-after.png":::
 
@@ -18,15 +18,15 @@ Here, you learn how Azure API Management can standardize, centralize, and help s
 
 We'll examine Azure API Management to help you decide if it's the correct solution to reduce your company's API complexity by studying these three main components:
 
-- **Gateway**. A single endpoint for all your API calls, which eases the implementation of security, rate limits, caching, and transformations.
-- **Administration interface**. A single interface where you import APIs, set policies, create API products, manage users and groups, and run analytics.
-- **Developer portal**. A website that brings all your APIs into a single location for developers to read documentation, test APIs, review code samples, get API keys, and run analytics.
+- **Gateway**: A single endpoint for all your API calls, which eases the implementation of security, rate limits, caching, and transformations.
+- **Administration interface**: A single interface where you import APIs, set policies, create API products, manage users and groups, and run analytics.
+- **Developer portal**: A website that brings all your APIs into a single location for developers to read documentation, test APIs, review code samples, get API keys, and run analytics.
 
 We'll also study Azure API Management from these three user angles:
 
-- **API consumers**. Entities (such as applications) that get value from using an API.
-- **API providers**. People who administer and maintain APIs.
-- **App developers**. People who build applications that consume APIs.
+- **API consumers**: Entities (such as applications) that get value from using an API.
+- **API providers**: People who administer and maintain APIs.
+- **App developers**: People who build applications that consume APIs.
 
 ## What is the main goal?
 

learn-pr/azure/introduction-to-azure-api-management/includes/2-what-is-azure-api-management.md

@@ -40,10 +40,10 @@ The *Azure API Management developer portal* is a fully customizable website that
 
 One of the biggest problems with having multiple published APIs is that each API requires a separate set of policies, which is a setting or action that controls the behavior of the API. Azure API Management solves the API policy problem by enabling you to set policies for all your APIs in a single place. You can set policies in many categories, but a partial list includes:
 
-- **Access restriction**. These policies determine when an API request is allowed through the gateway. For example, enforce rate limits and usage quotas, filter caller IPs, and check for a valid JSON Web Token (JWT).
-- **Authentication**. Authenticate API calls by using Basic authentication, a client certificate, or a managed identity as examples.
-- **Caching**. Improve API performance by storing and retrieving responses in the cache.
-- **Validation**. Validate API calls by comparing certain parameters to what's in your API specification. For example, validate the request or response body, the request header parameters, and the response headers.
+- **Access restriction**: These policies determine when an API request is allowed through the gateway. For example, enforce rate limits and usage quotas, filter caller IPs, and check for a valid JSON Web Token (JWT).
+- **Authentication**: Authenticate API calls by using Basic authentication, a client certificate, or a managed identity.
+- **Caching**: Improve API performance by storing and retrieving responses in the cache.
+- **Validation**: Validate API calls by comparing certain parameters to what's in your API specification. For example, you can validate the request or response body, the request header parameters, and the response headers.
 
 Flexibly combine your policies in *policy definitions*, which are XML documents that consist of a series of statements representing a policy and its parameters. Policy definitions let you configure separate policies at different stages of the API request-response pipeline as shown here:
 

learn-pr/azure/introduction-to-azure-api-management/includes/3-how-azure-api-management-works.md

@@ -20,15 +20,25 @@ If you're an API provider, you still have work to do after your APIs have been p
 
 The administration interface enables you to perform the following tasks:
 
-**Define and import API specs**: Import an OpenAPI specification, a REST API, a Simple Object Access Protocol (SOAP) API, a WebSocket API, or a GraphQL API. You can also create an API by importing instances of Azure services like Web App, Container App, Function App, Logic App, and Service Fabric. You can also create a blank API and define it manually.
+### Define and import API specs
 
-**Manage users and groups**: A *user* is a developer account for an API consumer that you can add manually or invite to create an account. A *group* is a collection of related users that you can associate with a particular API product, and then each group's user has access to the product.
+You can import an OpenAPI specification, a REST API, a Simple Object Access Protocol (SOAP) API, a WebSocket API, or a GraphQL API. You can also create an API by importing instances of Azure services like Web App, Container App, Function App, Logic App, and Service Fabric. In addition, you can create a blank API and define it manually.
 
-**Package APIs into products**: A *product* is a group of related APIs. By packaging multiple APIs as a single product, you can configure just the product instead of configuring all the APIs separately. This configuration gets applied to all the APIs in the product, and after published consumers can subscribe with a single subscription key.
+### Manage users and groups
 
-**Monitor and analyze APIs**: The administration interface includes built-in monitoring tools to trace and review API traffic in real time and analytics for insights on how consumers are using your published APIs. Azure API Management also supports several Azure tools including Azure Monitor Logs, Application Insights, and Event Hubs.
+A *user* is a developer account for an API consumer that you can add manually or invite to create an account. A *group* is a collection of related users that you can associate with a particular API product, and then each group's user has access to the product.
 
-**Manage API revisions and versions**: When your API developer team needs to make changes to an API, expose the change in a safe and controlled manner by using revisions and versions. A *revision* is a relatively minor or nonbreaking change to an API. Your development team can code and test the revision separately from the production API, and then set the updated API as the current revision once ready as in the following image. A *version* is a relatively major or breaking change to an API. Azure API Management enables you to offer developers multiple versions of the API simultaneously and offers several versioning schemes.
+### Package APIs into products
+
+A *product* is a group of related APIs. By packaging multiple APIs as a single product, you can configure just the product instead of configuring all the APIs separately. This configuration gets applied to all the APIs in the product, and after published consumers can subscribe with a single subscription key.
+
+### Monitor and analyze APIs
+
+The administration interface includes built-in monitoring tools to trace and review API traffic in real time and analytics for insights on how consumers are using your published APIs. Azure API Management also supports several Azure tools including Azure Monitor Logs, Application Insights, and Event Hubs.
+
+### Manage API revisions and versions
+
+When your API developer team needs to make changes to an API, expose the change in a safe and controlled manner by using revisions and versions. A *revision* is a relatively minor or nonbreaking change to an API. Your development team can code and test the revision separately from the production API, and then set the updated API as the current revision once ready as in the following image. A *version* is a relatively major or breaking change to an API. Azure API Management enables you to offer developers multiple versions of the API simultaneously and offers several versioning schemes.
 
 :::image type="content" source="../media/3-how-azure-api-management-works-revisions.png" alt-text="Depiction of how revisions work in Azure API Management. API requests from consumers are routed to the current revision of the API, whereas API requests from the in-house development team are routed to the API revision." lightbox="../media/3-how-azure-api-management-works-revisions.png":::
 
@@ -37,7 +47,7 @@ The administration interface enables you to perform the following tasks:
 Except for the Consumption tier, all Azure API Management instances include a developer portal where you surface your APIs to potential and existing API consumers. The developer portal comes with a default interface that's customizable to match your organization's branding and requirements. Once signed in, developers are presented with a web interface that enables them to interact with APIs in the following ways:
 
 - **Accessing API documentation**: Developers can review the documentation you've provided for each API.
-- **Testing an API**: The developer portal offers an interactive console that enables a developer to test an API quickly and safely.
-- **Reviewing API code samples**: The developer portal offers API call samples in several programming languages, including C#, Java, JavaScript, PHP, and Python.
-- **Subscribing to an API**: When a consumer decides to use your API, the developer portal enables the user to create a subscription to the API and obtain a subscription key to use when calling the API.
-- **Running analytics**: The developer portal offers analytics on the developer's usage of an API.
+- **Testing an API**: Offers an interactive console that enables a developer to test an API quickly and safely.
+- **Reviewing API code samples**: API call samples in several programming languages, including C#, Java, JavaScript, PHP, and Python.
+- **Subscribing to an API**: When a consumer decides to use your API, it enables the user to create a subscription to the API and obtain a subscription key to use when calling the API.
+- **Running analytics**: Includes analytics on the developer's usage of an API.

learn-pr/azure/introduction-to-azure-api-management/includes/4-when-to-use-azure-api-management.md

@@ -1,6 +1,6 @@
-Now let's discuss some scenarios that illustrate when it's appropriate to use Azure API Management. Let's investigate API lifecycle management with respect to standardizing APIs, centralizing API management and exposure, and enhancing API security. These don't apply equally to all use cases, but let's look deeper at each one.
+Now let's discuss some scenarios that illustrate when it's appropriate to use Azure API Management. Let's investigate API lifecycle management with respect to standardizing APIs, centralizing API management and exposure, and enhancing API security. These don't apply equally to all use cases, but we'll look deeper at each one.
 
-### Should you use Azure API Management to standardize APIs?
+### Standardize APIs
 
 By enabling  management of multiple APIs from a single administrative interface, Azure API Management makes it easier to create consistency across multiple APIs. You can standardize many API features, including:
 
@@ -14,13 +14,13 @@ By enabling  management of multiple APIs from a single administrative interface,
 
 This is true of the food delivery scenario, which requires consistency across the APIs for consumers.
 
-### Should you use Azure API Management to centralize API operations?
+### Centralize API operations
 
 Azure API Management enhances the centralization of all API operations by bringing multiple APIs under a single administrative umbrella. Centralizing API operations can result in better admin operations, deployment centralization, and enhanced developer access.
 
 All these factors apply to our food delivery scenario. Centralized consumer access through the developer portal makes it easier to sign up new developers, enhancing the monetization of the platform's APIs.
 
-### Should you use Azure API Management to secure access to your APIs?
+### Secure access to your APIs
 
 Azure API Management was designed with API security in mind. So many organizations rely on APIs for the internal and external exchange of data between apps and devices. A proper API security strategy covers the following bases: