Updated per feedback

Author: ecfan

articles/connectors/connectors-create-api-mq.md

@@ -115,8 +115,8 @@ For more information, review the [MQ managed connector reference](/connectors/mq
 
       | Incoming MQ server certificate | Requirements |
       |--------------------------------|---------------|
-      | Publicly trusted private key certificate issued by a trusted [certificate authority](https://www.ssl.com/faqs/what-is-a-certificate-authority/) | Usually, your logic app doesn't need any other setup because your logic app's virtual machine host usually has the required public key certificates to validate the incoming MQ server's private key certificate. To check that these public key certificates exist, follow the steps to [View and confirm thumbprints for existing public key certificates](#view-existing-public-key-certificates). <br><br>If the virtual machine host doesn't have all the required public key certificates to validate the incoming MQ server's private key certificate and any chaining certificates, complete the following steps: <br><br>1. Recreate your Standard logic app using an [Azure App Service Environment v3 (ASE) with a Windows-only and ASE-based App Service plan](../app-service/environment/overview.md). <br><br>2. Manually add the required public key certificates to the host's Trusted Root CA Store. For more information, see [Add a public key certificate](#view-existing-public-key-certificates). |
-      | Non-publicly trusted private key certificate, such as a self-signed or private CA certificate | Your logic app's virtual machine host won't have the required public key certificates in the host's Trusted Root CA Store to validate the MQ server's certificate chain. In this case, complete the following steps: <br><br>1. Recreate your Standard logic app using an [Azure App Service Environment v3 (ASE) with a Windows-only and ASE-based App Service plan](../app-service/environment/overview.md). <br><br>2. Manually add the required public key certificates to the host's Trusted Root CA Store. For more information, see [Add a public key certificate](#view-existing-public-key-certificates). |
+      | Publicly trusted private key certificate issued by a trusted [certificate authority](https://www.ssl.com/faqs/what-is-a-certificate-authority/) | Usually, your logic app doesn't need any other setup because your logic app's virtual machine host usually has the required public key certificates to validate the incoming MQ server's private key certificate. To check that these public key certificates exist, follow the steps to [View and confirm thumbprints for existing public key certificates](#view-existing-public-key-certificates). <br><br>If the virtual machine host doesn't have all the required public key certificates to validate the incoming MQ server's private key certificate and any chaining certificates, complete the following steps: <br><br>1. Recreate your Standard logic app using an [Azure App Service Environment v3 (ASE) with a Windows-only and ASE-based App Service plan](../app-service/environment/overview.md). <br><br>2. Manually [add the required public key certificates to the host's Trusted Root CA Store](#view-existing-public-key-certificates). |
+      | Non-publicly trusted private key certificate, such as a self-signed or private CA certificate | Your logic app's virtual machine host won't have the required public key certificates in the host's Trusted Root CA Store to validate the MQ server's certificate chain. In this case, complete the following steps: <br><br>1. Recreate your Standard logic app using an [Azure App Service Environment v3 (ASE) with a Windows-only and ASE-based App Service plan](../app-service/environment/overview.md). <br><br>2. Manually [add the required public key certificates to the host's Trusted Root CA Store](#view-existing-public-key-certificates). <br><br>For more information, see the following documentation: <br>- [Certificate bindings and the App Service Environment](../app-service/environment/certificates.md) <br>- [Add and manage TLS/SSL certificates in Azure App Service](../app-service/configure-ssl-certificate.md) |
 
     * Logic app client authentication
 
@@ -311,7 +311,7 @@ To add a public key certificate to the Trusted Root CA Store on that virtual mac
    > [!NOTE]
    >
    > If you specify a thumbprint for a private CA certificate, the MQ built-in connector doesn't run any certificate validation, 
-   > such as checking the certificate's source or expiration date. If standard .NET SSL validation fails, the connector 
+   > such as checking the certificate's expiration date or source. If standard .NET SSL validation fails, the connector 
    > only compares any thumbprint value that's passed in against the value in the **WEBSITE_LOAD_ROOT_CERTIFICATES** setting.
 
 1. If the added certificate doesn't appear in the public key certificates list, on the toolbar, select **Refresh**.