Azure Logic Apps: Clarify OpenAPI supported version

Author: ecfan

articles/connectors/connectors-native-http-swagger.md

@@ -1,6 +1,6 @@
 ---
-title: Connect to REST endpoints from Azure Logic Apps
-description: Connect to REST endpoints from automated workflows in Azure Logic Apps.
+title: Call or connect to REST endpoints from workflows
+description: Learn how to call or connect to REST endpoints from workflows in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
@@ -9,15 +9,15 @@ ms.date: 11/01/2019
 tags: connectors
 ---
 
-# Call REST endpoints by using Azure Logic Apps
+# Call REST endpoints from workflows in Azure Logic Apps
 
-With [Azure Logic Apps](../logic-apps/logic-apps-overview.md) and the built-in **HTTP + Swagger** operation, you can create automated integration workflows that regularly call any REST endpoint through a [Swagger file](https://swagger.io). The **HTTP + Swagger** trigger and action work the same as the [HTTP trigger and action](connectors-native-http.md) but provide a better experience in the workflow designer by exposing the API structure and outputs described by the Swagger file. To implement a polling trigger, follow the polling pattern that's described in [Create custom APIs to call other APIs, services, and systems from logic app workflows](../logic-apps/logic-apps-create-api-app.md#polling-triggers).
+With the built-in **HTTP + Swagger** operation and [Azure Logic Apps](../logic-apps/logic-apps-overview.md), you can create automated integration workflows that regularly call any REST endpoint through a [Swagger file](https://swagger.io). The **HTTP + Swagger** trigger and action work the same as the [HTTP trigger and action](connectors-native-http.md) but provide a better experience in the workflow designer by exposing the API structure and outputs described by the Swagger file. To implement a polling trigger, follow the polling pattern that's described in [Create custom APIs to call other APIs, services, and systems from logic app workflows](../logic-apps/logic-apps-create-api-app.md#polling-triggers).
 
 ## Prerequisites
 
 * An account and Azure subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
-* The URL for the Swagger (not OpenAPI) file that describes the target REST endpoint that you want to call
+* The URL for the Swagger file (OpenAPI 2.0, not OpenAPI 3.0) that describes the target REST endpoint that you want to call
 
   Typically, the REST endpoint has to meet the following criteria for the trigger or action to work:
 
@@ -30,9 +30,11 @@ With [Azure Logic Apps](../logic-apps/logic-apps-overview.md) and the built-in *
   The examples in this topic use the [Cognitive Services Face API](../cognitive-services/face/overview.md), which requires a [Cognitive Services account and access key](../cognitive-services/cognitive-services-apis-create-account.md).
 
   > [!NOTE]
-  > To reference a Swagger file that's unhosted or that doesn't meet the security and cross-origin requirements, you can [upload the Swagger file to a blob container in an Azure storage account](#host-swagger), and enable CORS on that storage account so that you can reference the file.
+  > To reference a Swagger file that's unhosted or that doesn't meet the security and cross-origin requirements, 
+  > you can [upload the Swagger file to a blob container in an Azure storage account](#host-swagger), and enable 
+  > CORS on that storage account so that you can reference the file.
 
-* The logic app workflow from where you want to call the target endpoint. To start with the **HTTP + Swagger** trigger, create a blank logic app workflow. To use the HTTP + Swagger action, start your workflow with any trigger that you want. This example uses the **HTTP + Swagger** trigger as the first step. 
+* The logic app workflow from where you want to call the target endpoint. To start with the **HTTP + Swagger** trigger, create a blank logic app workflow. To use the **HTTP + Swagger** action, start your workflow with any trigger that you want. This example uses the **HTTP + Swagger** trigger as the first step. 
 
   If you're new to logic app workflows, review [What is Azure Logic Apps?](../logic-apps/logic-apps-overview.md) and [how to create your first logic app workflow](../logic-apps/quickstart-create-first-logic-app-workflow.md).
 
@@ -66,7 +68,7 @@ This built-in trigger sends an HTTP request to a URL for a Swagger file that des
 
 1. To add other available parameters, open the **Add new parameter** list, and select the parameters that you want.
 
-   For more information about authentication types available for HTTP + Swagger, see [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
+   For more information about authentication types available for HTTP + Swagger, review [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
 
 1. Continue building your workflow with actions that run when the trigger fires.
 
@@ -106,7 +108,7 @@ This built-in action sends an HTTP request to the URL for the Swagger file that
 
 1. To add other available parameters, open the **Add new parameter** list, and select the parameters that you want.
 
-   For more information about authentication types available for HTTP + Swagger, see [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
+   For more information about authentication types available for HTTP + Swagger, review [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
 
 1. When you're finished, remember to save your logic app workflow. On the designer toolbar, select **Save**.
 
@@ -145,9 +147,9 @@ This section provides more information about the outputs from an **HTTP + Swagge
 
 | Property name | Type | Description |
 |---------------|------|-------------|
-| headers | object | The headers from the request |
-| body | object | The object with the body content from the request |
-| status code | int | The status code from the request |
+| **headers** | Object | The headers from the request |
+| **body** | Object | The object with the body content from the request |
+| **status code** | Integer | The status code from the request |
 ||||
 
 | Status code | Description |