Merge pull request #73 from infor-cloud/BatchSchedulingFixSpelling

Fixed spelling

docs/documentation/batch-scheduling.md

@@ -20,7 +20,7 @@ Scheduling XtendM3 Batch Extensions
 ---
 
 ## SHS010/SHS010MI
-SHS010, or SHS010MI for the interactive version, is the scheduler for XtendM3 Batch Extensions. It works in a similar fashion to SHS050, which is used to schedule M3 Batch Jobs, and in the background also schedules executions through this.
+SHS010, or SHS010MI for the non-interactive version, is the scheduler for XtendM3 Batch Extensions. It works in a similar fashion to SHS050, which is used to schedule M3 Batch Jobs, and in the background also schedules executions through this.
 
 ### Available parameters
 This section lists the available SHS010MI parameters. 
@@ -30,7 +30,7 @@ This section lists the available SHS010MI parameters.
 * XTOD: execute today, needs to be paired with XJTM
 
 #### Next weekday once
-To consider, each of these parameters needs to be pared with a time(XJTM).
+To consider, each of these parameters needs to be paired with a time(XJTM).
 * XNMO: execute next Monday
 * XNTU: execute next Tuesday
 * XNWE: execute next Wednesday
@@ -40,7 +40,7 @@ To consider, each of these parameters needs to be pared with a time(XJTM).
 * XNSU: execute next Sunday
 
 #### Schedule executions
-To consider, each of these parameters needs to be pared with a time(XJTM).
+To consider, each of these parameters needs to be paired with a time(XJTM).
 * XEMO: execute every Monday
 * XETU: execute every Tuesday
 * XEWE: execute every Wednesday
@@ -52,5 +52,5 @@ To consider, each of these parameters needs to be pared with a time(XJTM).
 
 <b>Note</b>, mon-sun is allowed to be multi-submission. All others must be single-submission.
 
-* XJTM: time, format is xxxx. Ex. 1340. Timezone will be the users local timezone, gathered from MNS151, MNS150 and MNS100
+* XJTM: time, format is xxxx. Ex. 1340. Timezone will be the users' local timezone, gathered from MNS151, MNS150 and MNS100
 * XRDY: day, format is xx. Ex. 25