updates

Author: davidctm

helix-control-m/2-external-monitoring-tools-examples/alerts-to-snmp/README.md

@@ -28,8 +28,6 @@ Before using the script, update the following variables:
 
 - The script sends all the alert fields received from Helix Control-M in the SNMP trap, including the "*notes*" field. Refer to the ["Alerts Template reference"](https://docs.bmc.com/docs/saas-api/alerts-template-reference-1144242602.html)) for more details.
 
-- The "snmptrap" command line is then completed by adding all the alert fields, passed as the payload of the trap. Each of them include the specific `OID`, the `type` ("s" for string) and the `value`.
-
 - This is an example of the "snmptrap" command line created by the script (showing only the first 2 alert fields - out of 21):
 
  ```
@@ -38,6 +36,8 @@ Before using the script, update the following variables:
 
  - The SNMP v1 trap definition in the "snmptrap" command line contains the `community` ("public"), the destination `host`, the `enterprise-OID` (as defined in the MIB file), the `agent` (IP address of the system generating the trap, empty to use the default value), the `generic-trap` number ("6" for traps defined in a custom MIB file), the `specific-trap` ("10" as defined in the MIB file for the TRAP-TYPE macro) and the `sysUpTime` of the generating application (empty to use the system generated value).
 
+ - The "snmptrap" command line is then completed by adding all the alert fields, passed as the payload of the trap. Each of them include the specific `OID`, the `type` ("s" for string) and the `value`.
+
 - This is an example of all the data and details from the generated SNMP v1 trap:
 
  ```