Added to instructions

Added more to the Define the environment variable section.

articles/sap-integration/env-variables-connection-refs.md

@@ -30,10 +30,11 @@ SAP has multiple connection parameters, and manually entering the parameters int
 1. Open the **SAP Integration** solution.
 1. On the command bar, select **New** > **More** > **Environment variable**.
 1. Complete the fields in the Environment variable panel.
-    - **Display name**. Enter a name for the environment variable.
-    - **Name**. This is automatically generated, but you can change it.
-    - **Data Type**. Select **Text** (_do not_ select JSON).
-      - Enter a JSON blob with a combination of SAP properties. Not all properties are necessary—your SAP environment will determine which ones are applicable. Refer to the SAP property guidance.
+    - **Display name**. Enter a display name for the environment variable.
+    - **Name**. This name is automatically generated, but you can change it.
+    - **Data Type**. Select **Text** (_don't_ select JSON).
+      - **Default Value**. Offers a defined environment variable template.
+      - **New value** Update the JSON blob with SAP system's SAP properties. Not all properties are necessary—your SAP environment will determine which ones are applicable. Refer to the SAP property guidance.
 
     :::image type="content" source="media/env-refs/env-var-panel.png" alt-text="The environment panel in Power Apps.":::
 
@@ -43,31 +44,31 @@ SAP has multiple connection parameters, and manually entering the parameters int
 |----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | AppServerHost        | The hostname of the SAP application Server.                                                                                                                                                                                                 |
 | AppServerService     | The service name or port number of the specific SAP application server to connect to (Optional if connection type (Logon) is A - Application Server).                                                                                         |
-| Client               | The SAP client ID to connect to the SAP system. The SAP backends' client (or 'Mandant') into which to log in. It is a number ranging from 000 to 999.                                                                                       |
+| Client               | The SAP client ID to connect to the SAP system. The SAP backends' client (or 'Mandant') into which to log in. It's a number ranging from 000 to 999.                                                                                       |
 | LogonGroup           | The logon group for the SAP system, from which the message server selects an application server (Only available if connection type (Logon) is B - Message Server (Group)).                                                             |
-| LogonType            | The type of logon to the SAP system. The allowed values are either Application Server Logon (Type A) or Group Logon (Type B, AKA Message Server).|
-| MessageServerHost    | The hostname of the SAP system's message server (central instance) aka R3 system name (Mandatory if connection type (Logon) is B - Message Server (Group)).                                                                                 |
-| MessageServerService | The service name (as defined in etc/services) or the port number under which the message server is listening for load-balancing requests (Mandatory if connection type (Logon) is B - Message Server (Group) and system ID is not present). |
+| LogonType            | The type of logon to the SAP system. The allowed values are either Application Server Logon (Type A) or Group Logon (Type B, also known as Message Server).|
+| MessageServerHost    | The hostname of the SAP system's message server (central instance) also known as R3 system name (Mandatory if connection type (Logon) is B - Message Server (Group)).                                                                                 |
+| MessageServerService | The service name (as defined in etc/services) or the port number under which the message server is listening for load-balancing requests (Mandatory if connection type (Logon) is B - Message Server (Group) and system ID isn't present). |
 | SncCertificate       | The X.509 certificate in Base64 encoded form, without the begin or end certificate tags.                                                                                                                                                        |
 | SncMyName            | The installed SNC solution usually knows its own SNC name. For solutions supporting multiple identities, you may need to specify the identity to be used for this destination/server (optional).                                     |
 | SncLibraryPath       | The name or path of the SNC library to be used. With the on-premises data gateway, the path can be an absolute or relative to the NCo library.                                                                                                   |
 | SncPartnerName       | The backends' SNC name (Required when type of logon is Application Server).                                                                                                                                                                    |
 | SncQop               | The quality of service to be used for SNC communication of this destination/server. The allowed values are Authentication, Integrity, Privacy, Default, and Maximum.                                                                                        |
 | SncSso               | The SNC SSO specifies whether to use SNC identity or credentials provided on RFC level.                                                                                                                                                     |
-| SystemId             | The SAP system's three-letter system ID (Mandatory if connection type (Logon) is B - Message Server (Group) and message server service is not present).                                                                                     |
+| SystemId             | The SAP system's three-letter system ID (Mandatory if connection type (Logon) is B - Message Server (Group) and message server service isn't present).                                                                                     |
 | SystemNumber         | The SAP system's system number. It's a number ranging from 00 to 99 (Mandatory if connection type (Logon) is A - Application Server).                                                                                                      |
 | UseSnc           |
  ||
 
 ## Use the environment variable in a flow
 
-Environment variables can be used in solution cloud flows since they are available in the dynamic content selector.
+Environment variables can be used in solution cloud flows since they're available in the dynamic content selector.
 
  For more information: [Use environment variables in Power Automate solution cloud flows](/power-apps/maker/data-platform/environmentvariables#use-environment-variables-in-power-automate-solution-cloud-flows)
 
 ### Known issue
 
-If an environment variable is updated after it has been used in a flow, the updated values will not be used the next time the flow runs. **The flow must be edited or resaved** for the updated values in the environment variable to take effect.
+If an environment variable is updated after it has been used in a flow, the updated values won't be used the next time the flow runs. **The flow must be edited or resaved** for the updated values in the environment variable to take effect.
 
 ### See also