Update articles/logic-apps/connectors/sap.md

Co-authored-by: Esther Fan <ecfan@users.noreply.github.com>

Author: GitHubber17

Diff for: articles/logic-apps/connectors/sap.md

@@ -629,7 +629,7 @@ For the SAP *built-in* connector, follow these steps that apply only to this con
    |-----------| ------------|
    | **SNC My Name** | In most cases, you can omit this value. The installed SNC solution usually knows its own SNC name. In the case where your solution supports multiple identities, you might have to specify the identity to use for this particular destination or server. |
    | **SNC Partner Name** | Enter the name for the backend SNC, for example, **p:CN=DV3, OU=LA, O=MS, C=US**. |
-   | **SNC Quality of Protection** | Select the quality of service to use for SNC communication with this particular destination or server. The back-end system defines the default value, and the security product used for SNC defines the maximum value. |
+   | **SNC Quality of Protection** | Select the quality of service to use for SNC communication with this particular destination or server. The back-end system defines the default value. The security product used for SNC defines the maximum value. |
    | **SNC Type** | Select the SNC authentication to use. |
    | **Certificate User** | Enter the user to connect when you have a certificate assigned to multiple users. |
    | **SNC Certificate** | Enter your SNC client's public certificate in base64-encoded format. This parameter specifies the certificates that this connection must use. <br><br>**Note**: - Don't include the PEM header or footer. <br><br>- Don't enter the private certificate here because the Personal Security Environment (PSE) might contain multiple private certificates. You specify this PSE by using the **SAP_PSE** app setting for your Standard logic app resource. <br><br>- If you use more than one SNC client certificate for your logic app resource, you must provide the same PSE for all connections. |