Merge pull request #42452 from vladvino/patch-1

Corrected open api spelling and added another Swagger constraint

Author: PRMerger9

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

@@ -21,10 +21,11 @@ ms.author: apipm
 ## About this list
 When importing an API, you might come across some restrictions or identify issues that need to be rectified before you can successfully import. This article documents these, organized by the import format of the API.
 
-## <a name="open-api"> </a>Open API/Swagger
-If you are receiving errors importing your Open API document, ensure you have validated it - either using the designer in the Azure portal (Design - Front End - Open API Specification Editor), or with a third-party tool such as <a href="http://www.swagger.io">Swagger Editor</a>.
+## <a name="open-api"> </a>OpenAPI/Swagger
+If you are receiving errors importing your OpenAPI document, ensure you have validated it - either using the designer in the Azure portal (Design - Front End - OpenAPI Specification Editor), or with a third-party tool such as <a href="http://www.swagger.io">Swagger Editor</a>.
 
 * Only JSON format for OpenAPI is supported.
+* Required parameters across both path and query must have unique names. (In OpenAPI a parameter name only needs to be unique within a location, e.g. path, query, header.  However, in API Management we allow operations to be discriminated by both path and query parameters (which OpenAPI does not support). Therefore we require parameter names to be unique within the entire URL template.)
 * Schemas referenced using **$ref** properties can't contain other **$ref** properties.
 * **$ref** pointers can't reference external files.
 * **x-ms-paths** and **x-servers** are the only supported extensions.