acrolinx 1

Author: v-hhunter

articles/api-management/api-management-api-import-restrictions.md

@@ -32,7 +32,7 @@ During OpenAPI import, API Management:
 
 If you prefer a different behavior, you can either: 
 * Manually change via form-based editor, or 
-* Simply remove the "required" attribute from the OpenAPI definition, thus not converting them to template parameters.
+* Remove the "required" attribute from the OpenAPI definition, thus not converting them to template parameters.
 
 ## <a name="open-api"> </a>OpenAPI/Swagger import limitations
 
@@ -46,7 +46,7 @@ If you receive errors while importing your OpenAPI document, make sure you've va
 
 | Requirement | Description |
 | ----------- | ----------- |
-| **Unique names for required path and query parameters** | In OpenAPI: <ul><li>A parameter name only needs to be unique within a location, for example path, query, header.</li></ul>In API Management:<ul><li>We allow operations to be discriminated by both path and query parameters.</li><li>OpenAPI doesn't support this, so we require parameter names to be unique within the entire URL template.</li></ul>  |
+| **Unique names for required path and query parameters** | In OpenAPI: <ul><li>A parameter name only needs to be unique within a location, for example path, query, header.</li></ul>In API Management:<ul><li>We allow operations to be discriminated by both path and query parameters.</li><li>OpenAPI doesn't support this discrimination, so we require parameter names to be unique within the entire URL template.</li></ul>  |
 | **Defined URL parameter** | Must be part of the URL template. |
 | **Available source file URL** | Applied to relative server URLs. |
 | **`\$ref` pointers** | Can't reference external files. |
@@ -118,15 +118,21 @@ API definitions exported from an API Management service are:
 * Primarily intended for external applications that need to call the API hosted in API Management service. 
 * Not intended to be imported into the same or different API Management service. 
 
-For configuration management of API definitions across different services/environments, please refer to documentation regarding using API Management Service with Git. 
+For configuration management of API definitions across different services/environments, refer to documentation regarding using API Management service with Git. 
 
 ### Add new API via OpenAPI import
 
-For each operation found in the OpenAPI document, a new operation will be created with Azure resource name and display name set to `operationId` and `summary`, respectively. 
-* `operationId` value is normalized.
-    *  If `operationId` isn't specified (not present, `null`, or empty), Azure resource name value will be generated by combining HTTP method and path template, for example, `get-foo`.
-* `summary` value is imported as-is and its length is limited to 300 characters.
-    * If `summary` isn't specified (not present, `null`, or empty), `display name` value will set to `operationId`. 
+For each operation found in the OpenAPI document, a new operation will be created with:
+* Azure resource name set to `operationId`.
+    * `operationId` value is normalized.
+    *  If `operationId` isn't specified (not present, `null`, or empty), Azure resource name value will be generated by combining HTTP method and path template.
+        * For example, `get-foo`.
+
+* Display name set to `summary`. 
+    * `summary` value:
+        * Imported as-is.
+        * Length is limited to 300 characters.
+    * If `summary` isn't specified (not present, `null`, or empty), display name value will set to `operationId`. 
 
 ### Update an existing API via OpenAPI import
 
@@ -148,7 +154,7 @@ To make import more predictable, follow these guidelines:
 
 ### Export API as OpenAPI
 
-Each operation's:
+For each operation, its:
 * Azure resource name will be exported as an `operationId`.
 * Display name will be exported as a `summary`.