Acrolinx score

Author: v-regandowner

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

@@ -109,14 +109,14 @@ Security definitions are ignored.
 When importing query parameters, only the default array serialization method (`style: form`, `explode: true`) is supported.  For more details on query parameters in OpenAPI specifications, refer to [the serialization specification](https://swagger.io/docs/specification/serialization/).
 
 <!-- Ref: 1795433 Parameter limitations -->
-Parameters [defined in cookies](https://swagger.io/docs/specification/describing-parameters/#cookie-parameters) are not supported.  You can still use policy to decode and validate the contents of cookies.  
+Parameters [defined in cookies](https://swagger.io/docs/specification/describing-parameters/#cookie-parameters) aren't supported.  You can still use policy to decode and validate the contents of cookies.  
 
 ### <a name="open-api-v2"> </a>OpenAPI version 2
 
 OpenAPI version 2 support is limited to JSON format only.
 
 <!-- Ref: 1795433 Parameter limitations -->
-["Form" type parameters](https://swagger.io/specification/v2/#parameter-object) are not supported.  You can still use policy to decode and validate `application/x-www-form-urlencoded` and `application/form-data` payloads.
+["Form" type parameters](https://swagger.io/specification/v2/#parameter-object) aren't supported.  You can still use policy to decode and validate `application/x-www-form-urlencoded` and `application/form-data` payloads.
 
 ### <a name="open-api-v3"> </a>OpenAPI version 3.x
 
@@ -128,15 +128,15 @@ API Management supports the following specification versions:
 #### HTTPS URLs
 
 * If multiple `servers` are specified, API Management will use the first HTTPS URL it finds. 
-* If there aren't any HTTPS URLs, the server URL will be empty.
+* If there aren't any HTTPS URLs, the server URL is empty.
 
 #### Supported
 
 - `example`
 
 #### Unsupported
 
-The following fields are included in either [OpenAPI version 3.0.x](https://swagger.io/specification/) or [OpenAPI version 3.1.x](https://spec.openapis.org/oas/v3.1.0), but are not supported:
+The following fields are included in either [OpenAPI version 3.0.x](https://swagger.io/specification/) or [OpenAPI version 3.1.x](https://spec.openapis.org/oas/v3.1.0), but aren't supported:
 
 | Object | Field |
 | ----------- | ----------- |
@@ -160,10 +160,10 @@ For configuration management of API definitions across different services/enviro
 
 ### Add new API via OpenAPI import
 
-For each operation found in the OpenAPI document, a new operation will be created with:
+For each operation found in the OpenAPI document, a new operation is 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.
+    *  If `operationId` isn't specified (not present, `null`, or empty), Azure resource name value is generated by combining HTTP method and path template.
         * For example, `get-foo`.
 
 * Display name set to `summary`. 
@@ -175,9 +175,9 @@ For each operation found in the OpenAPI document, a new operation will be create
 **Normalization rules for `operationId`**
 - Convert to lower case.
 - Replace each sequence of non-alphanumeric characters with a single dash.
-    - For example, `GET-/foo/{bar}?buzz={quix}` will be transformed into `get-foo-bar-buzz-quix-`.
+    - For example, `GET-/foo/{bar}?buzz={quix}` is transformed into `get-foo-bar-buzz-quix-`.
 - Trim dashes on both sides.
-    - For example, `get-foo-bar-buzz-quix-` will become `get-foo-bar-buzz-quix`
+    - For example, `get-foo-bar-buzz-quix-` becomes `get-foo-bar-buzz-quix`
 - Truncate to fit 76 characters, four characters less than maximum limit for a resource name.
 - Use remaining four characters for a de-duplication suffix, if necessary, in the form of `-1, -2, ..., -999`.
 
@@ -186,12 +186,12 @@ For each operation found in the OpenAPI document, a new operation will be create
 During import, the existing API operation:
 * Changes to match the API described in the OpenAPI document. 
 * Matches to an operation in the OpenAPI document by comparing its `operationId` value to the existing operation's Azure resource name. 
-    * If a match is found, existing operation’s properties will be updated "in-place".
+    * If a match is found, existing operation’s properties are updated "in-place".
     * If a match isn't found:
-        * A new operation will be created by combining HTTP method and path template, for example, `get-foo`. 
+        * A new operation is created by combining HTTP method and path template, for example, `get-foo`. 
         * For each new operation, the import will attempt to copy policies from an existing operation with the same HTTP method and path template.
 
-All existing unmatched operations will be deleted.
+All existing unmatched operations are deleted.
 
 To make import more predictable, follow these guidelines:
 
@@ -202,17 +202,17 @@ To make import more predictable, follow these guidelines:
 **Normalization rules for `operationId`**
 - Convert to lower case.
 - Replace each sequence of non-alphanumeric characters with a single dash.
-    - For example, `GET-/foo/{bar}?buzz={quix}` will be transformed into `get-foo-bar-buzz-quix-`.
+    - For example, `GET-/foo/{bar}?buzz={quix}` is transformed into `get-foo-bar-buzz-quix-`.
 - Trim dashes on both sides.
-    - For example, `get-foo-bar-buzz-quix-` will become `get-foo-bar-buzz-quix`
+    - For example, `get-foo-bar-buzz-quix-` becomes `get-foo-bar-buzz-quix`
 - Truncate to fit 76 characters, four characters less than maximum limit for a resource name.
 - Use remaining four characters for a de-duplication suffix, if necessary, in the form of `-1, -2, ..., -999`.
 
 ### Export API as OpenAPI
 
-For each operation, its:
-* Azure resource name will be exported as an `operationId`.
-* Display name will be exported as a `summary`.
+For each operation, it's:
+* Azure resource name is exported as an `operationId`.
+* Display name is exported as a `summary`.
 
 Note that normalization of the `operationId` is done on import, not on export.
 
@@ -231,7 +231,7 @@ You can create [SOAP pass-through](import-soap-api.md) and [SOAP-to-REST](restif
 
 ### WS-* specifications
 
-WSDL files incorporating WS-* specifications are not supported.
+WSDL files incorporating WS-* specifications aren't supported.
 
 ### Messages with multiple parts 
 This message type is not supported.
@@ -245,13 +245,13 @@ This message type is not supported.
 - Official support isn't offered at this time.
 
 ### Recursion
-- Types defined recursively are not supported by API Management.
+- Types defined recursively aren't supported by API Management.
 - For example, refer to an array of themselves.
 
 ### Multiple Namespaces
 While multiple namespaces can be used in a schema, only the target namespace can be used to define message parts. These namespaces are used to define other input or output elements.
 
-Namespaces other than the target are not preserved on export. While you can import a WSDL document defining message parts with other namespaces, all message parts will have the WSDL target namespace on export.
+Namespaces other than the target aren't preserved on export. While you can import a WSDL document defining message parts with other namespaces, all message parts will have the WSDL target namespace on export.
 
 ### Arrays 
 SOAP-to-REST transformation supports only wrapped arrays shown in the example below: