Apply suggestions from code review

Co-authored-by: Esther Fan <[email protected]>

Author: daviburg

articles/logic-apps/connectors/sap.md

@@ -169,11 +169,11 @@ SAP upgraded their .NET connector (NCo) to version 3.1, which changed the way th
 
 * By default, the SAP built-in connector operations are *stateless*. To run these operations in stateful mode, see [Enable stateful mode for stateless built-in connectors](/azure/connectors/enable-stateful-affinity-built-in-connectors). Stateful communications must remain in the same processing instance as the workflow for the following kinds of operations:
 
-  *  All actions that specify a **Session ID** value such as the action named **[BAPI] Commit transaction**.
+  *  All actions that specify a **Session ID** value, such as **[BAPI] Commit transaction**.
 
-  *  All actions that specify a **Transaction ID** value, except for the actions named **[IDOC - RFC] Confirm transaction Id** and **[IDoc] Get IDoc list for transaction**.
+  *  All actions that specify a **Transaction ID** value, except for the following actions: **[IDOC - RFC] Confirm transaction Id** and **[IDoc] Get IDoc list for transaction**.
 
-  *  The action named **Respond to SAP server**.
+  *  **Respond to SAP server**
 
 * To use either the SAP managed or built-in connector trigger named **When a message is received**, complete the following tasks: