Merge pull request #110979 from bluPhy/main

Updating multiple items in articles/api-management

Author: Court72

articles/api-management/api-management-configuration-repository-git.md

@@ -265,7 +265,7 @@ The `apis` folder contains a folder for each API in the service instance, which
 * `apis\<api name>\operations\` - Folder containing `<operation name>.description.html` files that map to the operations in the API. Each file contains the description of a single operation in the API, which maps to the `description` property of the [operation entity](/rest/api/apimanagement/current-ga/operation) in the REST API.
 
 ### apiVersionSets folder
-The `apiVerionSets` folder contains a folder for each API version set created for an API, and contains the following items.
+The `apiVersionSets` folder contains a folder for each API version set created for an API, and contains the following items.
 
 * `apiVersionSets\<api version set Id>\configuration.json` - Configuration for the version set. This is the same information that would be returned if you were to call the [Get a specific version set](/rest/api/apimanagement/current-ga/api-version-set/get) operation.
 

articles/api-management/api-management-howto-mutual-certificates-for-clients.md

@@ -71,7 +71,7 @@ You can also create policy expressions with the [`context` variable](api-managem
 
 > [!IMPORTANT]
 > * Starting May 2021, the `context.Request.Certificate` property only requests the certificate when the API Management instance's [`hostnameConfiguration`](/rest/api/apimanagement/current-ga/api-management-service/create-or-update#hostnameconfiguration) sets the `negotiateClientCertificate` property to True. By default, `negotiateClientCertificate` is set to False.
-> * If TLS renegotiation is disabled in your client, you may see TLS errors when requesting the certificate using the `context.Request.Certificate` property. If this occurs, enable TLS renegotation settings in the client. 
+> * If TLS renegotiation is disabled in your client, you may see TLS errors when requesting the certificate using the `context.Request.Certificate` property. If this occurs, enable TLS renegotiation settings in the client. 
 
 ### Checking the issuer and subject
 

articles/api-management/api-management-template-resources.md

@@ -476,7 +476,7 @@ The following localization options are supported:
 |ValidationErrorCredentialsInvalid|Email or password is invalid. Please correct the errors and try again.|  
 |WebAuthenticationRequestIsNotValid|Request is not valid|  
 |WebAuthenticationUserIsNotConfirm|Please confirm your registration before attempting to sign in.|  
-|WebAuthenticationInvalidEmailFormated|Email is invalid: {0}|  
+|WebAuthenticationInvalidEmailFormatted|Email is invalid: {0}|  
 |WebAuthenticationUserNotFound|User not found|  
 |WebAuthenticationTenantNotRegistered|Your account belongs to an Azure Active Directory tenant which is not authorized to access this portal.|  
 |WebAuthenticationAuthenticationFailed|Authentication has failed.|  

articles/api-management/import-logic-app-as-api.md

@@ -27,7 +27,7 @@ In this article, you learn how to:
 > -   Test the API in the Azure portal
 
 > [!NOTE]
-> API Management supports automated import of a Logic App (Consumption) resource. which runs in the multi-tenant Logic Apps environment. Learn more about [single-tenant versus muti-tenant Logic Apps](../logic-apps/single-tenant-overview-compare.md).
+> API Management supports automated import of a Logic App (Consumption) resource. which runs in the multi-tenant Logic Apps environment. Learn more about [single-tenant versus multi-tenant Logic Apps](../logic-apps/single-tenant-overview-compare.md).
 
 ## Prerequisites
 

articles/api-management/json-to-xml-policy.md

@@ -23,7 +23,7 @@ The `json-to-xml` policy converts a request or response body from JSON to XML.
     consider-accept-header="true | false" 
     parse-date="true | false" 
     namespace-separator="separator character"
-    namespace-prefix="namepsace prefix"
+    namespace-prefix="namespace prefix"
     attribute-block-name="name" />
 ```
 

articles/api-management/sap-api.md

@@ -63,7 +63,7 @@ In this article, you'll:
 1. From the side navigation menu, under the **APIs** section, select **APIs**.
 1. Under **Create a new definition**, select **OpenAPI specification**.
 
-    :::image type="content" source="./media/import-api-from-oas/oas-api.png" alt-text="OpenAPI specifiction":::
+    :::image type="content" source="./media/import-api-from-oas/oas-api.png" alt-text="OpenAPI specification":::
 
 1. Click **Select a file**, and select the `openapi-spec.json` file that you saved locally in a previous step.