diff --git a/specification/batch/data-plane/Microsoft.Batch/stable/2015-12-01.2.2/BatchService.json b/specification/batch/data-plane/Microsoft.Batch/stable/2015-12-01.2.2/BatchService.json
index abf8f47f69b0..009f63beeb0a 100644
--- a/specification/batch/data-plane/Microsoft.Batch/stable/2015-12-01.2.2/BatchService.json
+++ b/specification/batch/data-plane/Microsoft.Batch/stable/2015-12-01.2.2/BatchService.json
@@ -11370,7 +11370,7 @@
         },
         "commandLine": {
           "type": "string",
-          "description": "Gets or sets the command line of the task. For multi-instance tasks, the command line is executed on the primary subtask after all the subtasks have finished executing the coordianation command line."
+          "description": "Gets or sets the command line of the task. For multi-instance tasks, the command line is executed on the primary subtask after all the subtasks have finished executing the coordination command line."
         },
         "resourceFiles": {
           "type": "array",
@@ -11433,7 +11433,7 @@
         },
         "commandLine": {
           "type": "string",
-          "description": "Gets or sets the command line of the task. For multi-instance tasks, the command line is executed on the primary subtask after all the subtasks have finished executing the coordianation command line."
+          "description": "Gets or sets the command line of the task. For multi-instance tasks, the command line is executed on the primary subtask after all the subtasks have finished executing the coordination command line."
         },
         "resourceFiles": {
           "type": "array",
diff --git a/specification/batch/data-plane/Microsoft.Batch/stable/2016-02-01.3.0/BatchService.json b/specification/batch/data-plane/Microsoft.Batch/stable/2016-02-01.3.0/BatchService.json
index 10ca4a85342c..85a34cb906bf 100644
--- a/specification/batch/data-plane/Microsoft.Batch/stable/2016-02-01.3.0/BatchService.json
+++ b/specification/batch/data-plane/Microsoft.Batch/stable/2016-02-01.3.0/BatchService.json
@@ -11812,7 +11812,7 @@
         },
         "commandLine": {
           "type": "string",
-          "description": "The command line of the task. For multi-instance tasks, the command line is executed on the primary subtask after all the subtasks have finished executing the coordianation command line."
+          "description": "The command line of the task. For multi-instance tasks, the command line is executed on the primary subtask after all the subtasks have finished executing the coordination command line."
         },
         "resourceFiles": {
           "type": "array",
@@ -11875,7 +11875,7 @@
         },
         "commandLine": {
           "type": "string",
-          "description": "The command line of the task. For multi-instance tasks, the command line is executed on the primary subtask after all the subtasks have finished executing the coordianation command line."
+          "description": "The command line of the task. For multi-instance tasks, the command line is executed on the primary subtask after all the subtasks have finished executing the coordination command line."
         },
         "resourceFiles": {
           "type": "array",
diff --git a/specification/batch/data-plane/Microsoft.Batch/stable/2016-07-01.3.1/BatchService.json b/specification/batch/data-plane/Microsoft.Batch/stable/2016-07-01.3.1/BatchService.json
index 5323a4b00787..d87ed82be381 100644
--- a/specification/batch/data-plane/Microsoft.Batch/stable/2016-07-01.3.1/BatchService.json
+++ b/specification/batch/data-plane/Microsoft.Batch/stable/2016-07-01.3.1/BatchService.json
@@ -2990,7 +2990,7 @@
         ],
         "operationId": "JobSchedule_Update",
         "summary": "Updates the properties of the specified job schedule.",
-        "description": "This fully replaces all the updateable properties of the job schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are unaffected.",
+        "description": "This fully replaces all the updatable properties of the job schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are unaffected.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -4255,7 +4255,7 @@
         ],
         "operationId": "Job_Update",
         "summary": "Updates the properties of the specified job.",
-        "description": "This fully replaces all the updateable properties of the job. For example, if the job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.",
+        "description": "This fully replaces all the updatable properties of the job. For example, if the job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -6878,7 +6878,7 @@
         ],
         "operationId": "Pool_UpdateProperties",
         "summary": "Updates the properties of the specified pool.",
-        "description": "This fully replaces all the updateable properties of the pool. For example, if the pool has a start task associated with it and if start task is not specified with this request, then the Batch service will remove the existing start task.",
+        "description": "This fully replaces all the updatable properties of the pool. For example, if the pool has a start task associated with it and if start task is not specified with this request, then the Batch service will remove the existing start task.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -8759,7 +8759,7 @@
         ],
         "operationId": "ComputeNode_UpdateUser",
         "summary": "Updates the password or expiration time of a user account on the specified compute node.",
-        "description": "This operation replaces of all the updateable properties of the account. For example, if the expiryTime element is not specified, the current value is replaced with the default value, not left unmodified. You can update a user account on a node only when it is in the idle or running state.",
+        "description": "This operation replaces of all the updatable properties of the account. For example, if the expiryTime element is not specified, the current value is replaced with the default value, not left unmodified. You can update a user account on a node only when it is in the idle or running state.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -10457,7 +10457,7 @@
         "default": {
           "$ref": "#/definitions/ExitOptions",
           "title": "How the Batch service should respond if the task fails with an exit condition not covered by any of the other properties – that is, any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, or a scheduling error if the schedulingError property is not present.",
-          "description": "Note that the default condition does not include exit code 0. If you want non-default behaviour on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection."
+          "description": "Note that the default condition does not include exit code 0. If you want non-default behavior on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection."
         }
       },
       "title": "Specifies how the Batch service should respond when the task completes."
@@ -10502,8 +10502,8 @@
       "properties": {
         "jobAction": {
           "type": "string",
-          "title": "An action to take on the job containing the task, if the task completes with the given exit condition and the job’s onTaskFailed property is 'performexitoptionsjobaction'.",
-          "description": "The default is none for exit code 0 and terminate for all other exit conditions. It is an error to specify this if the job's onTaskFailed is noaction. The add task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request).",
+          "title": "An action to take on the job containing the task, if the task completes with the given exit condition and the job’s onTaskFailed property is 'performExitOptionsJobAction'.",
+          "description": "The default is none for exit code 0 and terminate for all other exit conditions. It is an error to specify this if the job's onTaskFailed is noAction. The add task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request).",
           "enum": [
             "none",
             "disable",
@@ -10541,7 +10541,7 @@
       "properties": {
         "id": {
           "type": "string",
-          "title": "A string that uniquely identifies the Job Manager taskwithin the job.",
+          "title": "A string that uniquely identifies the Job Manager task within the job.",
           "description": "The id can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters."
         },
         "displayName": {
@@ -10978,7 +10978,7 @@
         "onAllTasksComplete": {
           "type": "string",
           "title": "The action the Batch service should take when all tasks in a job created under this schedule are in the completed state.",
-          "description": "Note that if a job contains no tasks, then all tasks are considered complete. This option is therefore most commonly used with a job manager task; if you want to use automatic job termination without a job manager, you should initially set onAllTasksComplete to noaction and update the job properties to set onAllTasksComplete to terminatejob once you have finished adding tasks. The default is noaction.",
+          "description": "Note that if a job contains no tasks, then all tasks are considered complete. This option is therefore most commonly used with a job manager task; if you want to use automatic job termination without a job manager, you should initially set onAllTasksComplete to noAction and update the job properties to set onAllTasksComplete to terminateJob once you have finished adding tasks. The default is noAction.",
           "enum": [
             "noAction",
             "terminateJob"
@@ -10988,7 +10988,7 @@
         "onTaskFailure": {
           "type": "string",
           "title": "The action the Batch service should take when any task fails in a job created under this schedule. A task is considered to have failed if it completes with a non-zero exit code and has exhausted its retry count, or if it had a scheduling error.",
-          "description": "The default is noaction.",
+          "description": "The default is noAction.",
           "enum": [
             "noAction",
             "performExitOptionsJobAction"
@@ -11350,7 +11350,7 @@
         "terminateReason": {
           "type": "string",
           "title": "A string describing the reason the job ended.",
-          "description": "This property is set only if the job is in the completed state. If the Batch service terminates the job, it sets the reason as follows: JMComplete – the Job Manager task completed, and killJobOnCompletion was set to true. MaxWallClockTimeExpiry – the job reached its maxWallClockTime constraint. TerminateJobSchedule – the job ran as part of a schedule, and the schedule terminated. AllTasksComplete – the job's onAllTasksComplete attribute is set to terminatejob, and all tasks in the job are complete. TaskFailed – the job's onTaskFailure attribute is set to performexitoptionsjobaction, and a task in the job failed with an exit condition that specified a jobAction of terminatejob. Any other string is a user-defined reason specified in a call to the 'Terminate a job' operation."
+          "description": "This property is set only if the job is in the completed state. If the Batch service terminates the job, it sets the reason as follows: JMComplete – the Job Manager task completed, and killJobOnCompletion was set to true. MaxWallClockTimeExpiry – the job reached its maxWallClockTime constraint. TerminateJobSchedule – the job ran as part of a schedule, and the schedule terminated. AllTasksComplete – the job's onAllTasksComplete attribute is set to terminateJob, and all tasks in the job are complete. TaskFailed – the job's onTaskFailure attribute is set to performExitOptionsJobAction, and a task in the job failed with an exit condition that specified a jobAction of terminateJob. Any other string is a user-defined reason specified in a call to the 'Terminate a job' operation."
         }
       },
       "required": ["startTime"],
@@ -11469,7 +11469,7 @@
         "onAllTasksComplete": {
           "type": "string",
           "title": "The action the Batch service should take when all tasks in the job are in the completed state.",
-          "description": "Permitted values are: noaction – do nothing. The job remains active unless terminated or disabled by some other means. terminatejob – terminate the job. The job's terminateReason is set to 'AllTasksComplete'. The default is noaction.",
+          "description": "Permitted values are: noAction – do nothing. The job remains active unless terminated or disabled by some other means. terminateJob – terminate the job. The job's terminateReason is set to 'AllTasksComplete'. The default is noAction.",
           "enum": [
             "noAction",
             "terminateJob"
@@ -11479,7 +11479,7 @@
         "onTaskFailure": {
           "type": "string",
           "title": "The action the Batch service should take when any task in the job fails. A task is considered to have failed if it completes with a non-zero exit code and has exhausted its retry count, or if it had a scheduling error.",
-          "description": "Permitted values are: noaction – do nothing. performexitoptionsjobaction – take the action associated with the task exit condition in the task's exitConditions collection. (This may still result in no action being taken, if that is what the task specifies.) The default is noaction.",
+          "description": "Permitted values are: noAction – do nothing. performExitOptionsJobAction – take the action associated with the task exit condition in the task's exitConditions collection. (This may still result in no action being taken, if that is what the task specifies.) The default is noAction.",
           "enum": [
             "noAction",
             "performExitOptionsJobAction"
@@ -11556,7 +11556,7 @@
         "onAllTasksComplete": {
           "type": "string",
           "title": "The action the Batch service should take when all tasks in the job are in the completed state.",
-          "description": "Note that if a job contains no tasks, then all tasks are considered complete. This option is therefore most commonly used with a job manager task; if you want to use automatic job termination without a job manager, you should initially set onAllTasksComplete to noaction and update the job properties to set onAllTasksComplete to terminatejob once you have finished adding tasks. Permitted values are: noaction – do nothing. The job remains active unless terminated or disabled by some other means. terminatejob – terminate the job. The job’s terminateReason is set to 'AllTasksComplete'. The default is noaction.",
+          "description": "Note that if a job contains no tasks, then all tasks are considered complete. This option is therefore most commonly used with a job manager task; if you want to use automatic job termination without a job manager, you should initially set onAllTasksComplete to noAction and update the job properties to set onAllTasksComplete to terminateJob once you have finished adding tasks. Permitted values are: noAction – do nothing. The job remains active unless terminated or disabled by some other means. terminateJob – terminate the job. The job’s terminateReason is set to 'AllTasksComplete'. The default is noAction.",
           "enum": [
             "noAction",
             "terminateJob"
@@ -11566,7 +11566,7 @@
         "onTaskFailure": {
           "type": "string",
           "title": "The action the Batch service should take when any task in the job fails. A task is considered to have failed if it completes with a non-zero exit code and has exhausted its retry count, or if it had a scheduling error.",
-          "description": "Permitted values are: noaction – do nothing. performexitoptionsjobaction – take the action associated with the task exit condition in the task's exitConditions collection. (This may still result in no action being taken, if that is what the task specifies.) The default is noaction.",
+          "description": "Permitted values are: noAction – do nothing. performExitOptionsJobAction – take the action associated with the task exit condition in the task's exitConditions collection. (This may still result in no action being taken, if that is what the task specifies.) The default is noAction.",
           "enum": [
             "noAction",
             "performExitOptionsJobAction"
@@ -13193,7 +13193,7 @@
         "onAllTasksComplete": {
           "type": "string",
           "title": "Specifies an action the Batch service should take when all tasks in the job are in the completed state.",
-          "description": "If omitted, the completion behavior is left unchanged. You may not change the value from terminatejob to noaction – that is, once you have engaged automatic job termination, you cannot turn it off again. If you try to do this, the request fails with an 'invalid property value' error response; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request).",
+          "description": "If omitted, the completion behavior is left unchanged. You may not change the value from terminateJob to noAction – that is, once you have engaged automatic job termination, you cannot turn it off again. If you try to do this, the request fails with an 'invalid property value' error response; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request).",
           "enum": [
             "noAction",
             "terminateJob"
@@ -13250,7 +13250,7 @@
         "onAllTasksComplete": {
           "type": "string",
           "title": "Specifies an action the Batch service should take when all tasks in the job are in the completed state.",
-          "description": "If omitted, the completion behavior is set to noaction. If the current value is terminatejob, this is an error because a job's completion behavior may not be changed from terminatejob to noaction.",
+          "description": "If omitted, the completion behavior is set to noAction. If the current value is terminateJob, this is an error because a job's completion behavior may not be changed from terminateJob to noAction.",
           "enum": [
             "noAction",
             "terminateJob"
diff --git a/specification/batch/data-plane/Microsoft.Batch/stable/2017-01-01.4.0/BatchService.json b/specification/batch/data-plane/Microsoft.Batch/stable/2017-01-01.4.0/BatchService.json
index 9a989687b1d7..e22497216879 100644
--- a/specification/batch/data-plane/Microsoft.Batch/stable/2017-01-01.4.0/BatchService.json
+++ b/specification/batch/data-plane/Microsoft.Batch/stable/2017-01-01.4.0/BatchService.json
@@ -3110,7 +3110,7 @@
           "JobSchedule update": { "$ref": "./examples/JobScheduleUpdate.json" }
         },
         "summary": "Updates the properties of the specified job schedule.",
-        "description": "This fully replaces all the updateable properties of the job schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are unaffected.",
+        "description": "This fully replaces all the updatable properties of the job schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are unaffected.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -4425,7 +4425,7 @@
           "Job update": { "$ref": "./examples/JobUpdate.json" }
         },
         "summary": "Updates the properties of the specified job.",
-        "description": "This fully replaces all the updateable properties of the job. For example, if the job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.",
+        "description": "This fully replaces all the updatable properties of the job. For example, if the job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -7150,7 +7150,7 @@
           "Pool update": { "$ref": "./examples/PoolUpdate.json" }
         },
         "summary": "Updates the properties of the specified pool.",
-        "description": "This fully replaces all the updateable properties of the pool. For example, if the pool has a start task associated with it and if start task is not specified with this request, then the Batch service will remove the existing start task.",
+        "description": "This fully replaces all the updatable properties of the pool. For example, if the pool has a start task associated with it and if start task is not specified with this request, then the Batch service will remove the existing start task.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -9108,7 +9108,7 @@
           "Node update user": { "$ref": "./examples/NodeUpdateUser.json" }
         },
         "summary": "Updates the password or expiration time of a user account on the specified compute node.",
-        "description": "This operation replaces of all the updateable properties of the account. For example, if the expiryTime element is not specified, the current value is replaced with the default value, not left unmodified. You can update a user account on a node only when it is in the idle or running state.",
+        "description": "This operation replaces of all the updatable properties of the account. For example, if the expiryTime element is not specified, the current value is replaced with the default value, not left unmodified. You can update a user account on a node only when it is in the idle or running state.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -10868,7 +10868,7 @@
         "default": {
           "$ref": "#/definitions/ExitOptions",
           "title": "How the Batch service should respond if the task fails with an exit condition not covered by any of the other properties - that is, any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, or a scheduling error if the schedulingError property is not present.",
-          "description": "Note that the default condition does not include exit code 0. If you want non-default behaviour on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection."
+          "description": "Note that the default condition does not include exit code 0. If you want non-default behavior on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection."
         }
       },
       "title": "Specifies how the Batch service should respond when the task completes."
@@ -11031,7 +11031,7 @@
       "properties": {
         "id": {
           "type": "string",
-          "title": "A string that uniquely identifies the Job Manager taskwithin the job.",
+          "title": "A string that uniquely identifies the Job Manager task within the job.",
           "description": "The id can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters."
         },
         "displayName": {
@@ -14176,4 +14176,4 @@
     }
   }
 }
-
+
diff --git a/specification/batch/data-plane/Microsoft.Batch/stable/2017-05-01.5.0/BatchService.json b/specification/batch/data-plane/Microsoft.Batch/stable/2017-05-01.5.0/BatchService.json
index 38fb75cbe280..a7d0272f4233 100644
--- a/specification/batch/data-plane/Microsoft.Batch/stable/2017-05-01.5.0/BatchService.json
+++ b/specification/batch/data-plane/Microsoft.Batch/stable/2017-05-01.5.0/BatchService.json
@@ -3110,7 +3110,7 @@
           "JobSchedule update": { "$ref": "./examples/JobScheduleUpdate.json" }
         },
         "summary": "Updates the properties of the specified job schedule.",
-        "description": "This fully replaces all the updateable properties of the job schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are unaffected.",
+        "description": "This fully replaces all the updatable properties of the job schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are unaffected.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -4425,7 +4425,7 @@
           "Job update": { "$ref": "./examples/JobUpdate.json" }
         },
         "summary": "Updates the properties of the specified job.",
-        "description": "This fully replaces all the updateable properties of the job. For example, if the job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.",
+        "description": "This fully replaces all the updatable properties of the job. For example, if the job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -7150,7 +7150,7 @@
           "Pool update": { "$ref": "./examples/PoolUpdate.json" }
         },
         "summary": "Updates the properties of the specified pool.",
-        "description": "This fully replaces all the updateable properties of the pool. For example, if the pool has a start task associated with it and if start task is not specified with this request, then the Batch service will remove the existing start task.",
+        "description": "This fully replaces all the updatable properties of the pool. For example, if the pool has a start task associated with it and if start task is not specified with this request, then the Batch service will remove the existing start task.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -9108,7 +9108,7 @@
           "Node update user": { "$ref": "./examples/NodeUpdateUser.json" }
         },
         "summary": "Updates the password or expiration time of a user account on the specified compute node.",
-        "description": "This operation replaces of all the updateable properties of the account. For example, if the expiryTime element is not specified, the current value is replaced with the default value, not left unmodified. You can update a user account on a node only when it is in the idle or running state.",
+        "description": "This operation replaces of all the updatable properties of the account. For example, if the expiryTime element is not specified, the current value is replaced with the default value, not left unmodified. You can update a user account on a node only when it is in the idle or running state.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -10872,7 +10872,7 @@
         "default": {
           "$ref": "#/definitions/ExitOptions",
           "title": "How the Batch service should respond if the task fails with an exit condition not covered by any of the other properties.",
-          "description": "This value is used if the task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behaviour on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection."
+          "description": "This value is used if the task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behavior on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection."
         }
       },
       "title": "Specifies how the Batch service should respond when the task completes."
@@ -11057,7 +11057,7 @@
       "properties": {
         "id": {
           "type": "string",
-          "title": "A string that uniquely identifies the Job Manager taskwithin the job.",
+          "title": "A string that uniquely identifies the Job Manager task within the job.",
           "description": "The id can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters."
         },
         "displayName": {
@@ -14394,4 +14394,4 @@
     }
   }
 }
-
+
diff --git a/specification/batch/data-plane/Microsoft.Batch/stable/2017-06-01.5.1/BatchService.json b/specification/batch/data-plane/Microsoft.Batch/stable/2017-06-01.5.1/BatchService.json
index 5c116e442a53..75d807361e01 100644
--- a/specification/batch/data-plane/Microsoft.Batch/stable/2017-06-01.5.1/BatchService.json
+++ b/specification/batch/data-plane/Microsoft.Batch/stable/2017-06-01.5.1/BatchService.json
@@ -3111,7 +3111,7 @@
           "JobSchedule update": { "$ref": "./examples/JobScheduleUpdate.json" }
         },
         "summary": "Updates the properties of the specified job schedule.",
-        "description": "This fully replaces all the updateable properties of the job schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are unaffected.",
+        "description": "This fully replaces all the updatable properties of the job schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are unaffected.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -4426,7 +4426,7 @@
           "Job update": { "$ref": "./examples/JobUpdate.json" }
         },
         "summary": "Updates the properties of the specified job.",
-        "description": "This fully replaces all the updateable properties of the job. For example, if the job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.",
+        "description": "This fully replaces all the updatable properties of the job. For example, if the job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -7249,7 +7249,7 @@
           "Pool update": { "$ref": "./examples/PoolUpdate.json" }
         },
         "summary": "Updates the properties of the specified pool.",
-        "description": "This fully replaces all the updateable properties of the pool. For example, if the pool has a start task associated with it and if start task is not specified with this request, then the Batch service will remove the existing start task.",
+        "description": "This fully replaces all the updatable properties of the pool. For example, if the pool has a start task associated with it and if start task is not specified with this request, then the Batch service will remove the existing start task.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -9207,7 +9207,7 @@
           "Node update user": { "$ref": "./examples/NodeUpdateUser.json" }
         },
         "summary": "Updates the password and expiration time of a user account on the specified compute node.",
-        "description": "This operation replaces of all the updateable properties of the account. For example, if the expiryTime element is not specified, the current value is replaced with the default value, not left unmodified. You can update a user account on a node only when it is in the idle or running state.",
+        "description": "This operation replaces of all the updatable properties of the account. For example, if the expiryTime element is not specified, the current value is replaced with the default value, not left unmodified. You can update a user account on a node only when it is in the idle or running state.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -10974,7 +10974,7 @@
         "default": {
           "$ref": "#/definitions/ExitOptions",
           "title": "How the Batch service should respond if the task fails with an exit condition not covered by any of the other properties.",
-          "description": "This value is used if the task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behaviour on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection."
+          "description": "This value is used if the task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behavior on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection."
         }
       },
       "title": "Specifies how the Batch service should respond when the task completes."
@@ -11033,7 +11033,7 @@
         "dependencyAction": {
           "type": "string",
           "title": "An action that the Batch service performs on tasks that depend on this task.",
-          "description": "Values are:\n\n satisfy - Satisfy the task's dependencies.\n block - Block the task's dependencies.\n\n The default is 'satisfy' for exit code 0, and 'block' for all other exit conditions. If the job's usesTaskDependencies property is set to false, then specifying the dependencyAction property returns an erro and the add task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400  (Bad Request).",
+          "description": "Values are:\n\n satisfy - Satisfy the task's dependencies.\n block - Block the task's dependencies.\n\n The default is 'satisfy' for exit code 0, and 'block' for all other exit conditions. If the job's usesTaskDependencies property is set to false, then specifying the dependencyAction property returns an error and the add task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400  (Bad Request).",
           "enum": [
             "satisfy",
             "block"
@@ -11276,7 +11276,7 @@
         "userIdentity": {
           "$ref": "#/definitions/UserIdentity",
           "title": "The user identity under which the Job Preparation task runs.",
-          "description": "If omitted, the task runs as a non-administrative user unique to the task on Windows nodes, or a a non-administrative user unique to the pool on Linux nodes."
+          "description": "If omitted, the task runs as a non-administrative user unique to the task on Windows nodes, or a non-administrative user unique to the pool on Linux nodes."
         },
         "rerunOnNodeRebootAfterSuccess": {
           "type": "boolean",
diff --git a/specification/batch/data-plane/Microsoft.Batch/stable/2017-09-01.6.0/BatchService.json b/specification/batch/data-plane/Microsoft.Batch/stable/2017-09-01.6.0/BatchService.json
index 000a8b1047c1..d4fd9d4145c2 100644
--- a/specification/batch/data-plane/Microsoft.Batch/stable/2017-09-01.6.0/BatchService.json
+++ b/specification/batch/data-plane/Microsoft.Batch/stable/2017-09-01.6.0/BatchService.json
@@ -3111,7 +3111,7 @@
           "JobSchedule update": { "$ref": "./examples/JobScheduleUpdate.json" }
         },
         "summary": "Updates the properties of the specified job schedule.",
-        "description": "This fully replaces all the updateable properties of the job schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are unaffected.",
+        "description": "This fully replaces all the updatable properties of the job schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are unaffected.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -4426,7 +4426,7 @@
           "Job update": { "$ref": "./examples/JobUpdate.json" }
         },
         "summary": "Updates the properties of the specified job.",
-        "description": "This fully replaces all the updateable properties of the job. For example, if the job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.",
+        "description": "This fully replaces all the updatable properties of the job. For example, if the job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -7250,7 +7250,7 @@
           "Pool update": { "$ref": "./examples/PoolUpdate.json" }
         },
         "summary": "Updates the properties of the specified pool.",
-        "description": "This fully replaces all the updateable properties of the pool. For example, if the pool has a start task associated with it and if start task is not specified with this request, then the Batch service will remove the existing start task.",
+        "description": "This fully replaces all the updatable properties of the pool. For example, if the pool has a start task associated with it and if start task is not specified with this request, then the Batch service will remove the existing start task.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -9210,7 +9210,7 @@
           "Node update user": { "$ref": "./examples/NodeUpdateUser.json" }
         },
         "summary": "Updates the password and expiration time of a user account on the specified compute node.",
-        "description": "This operation replaces of all the updateable properties of the account. For example, if the expiryTime element is not specified, the current value is replaced with the default value, not left unmodified. You can update a user account on a node only when it is in the idle or running state.",
+        "description": "This operation replaces of all the updatable properties of the account. For example, if the expiryTime element is not specified, the current value is replaced with the default value, not left unmodified. You can update a user account on a node only when it is in the idle or running state.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -11024,7 +11024,7 @@
         "default": {
           "$ref": "#/definitions/ExitOptions",
           "title": "How the Batch service should respond if the task fails with an exit condition not covered by any of the other properties.",
-          "description": "This value is used if the task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behaviour on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection."
+          "description": "This value is used if the task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behavior on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection."
         }
       },
       "title": "Specifies how the Batch service should respond when the task completes."
@@ -11069,7 +11069,7 @@
         "jobAction": {
           "type": "string",
           "title": "An action to take on the job containing the task, if the task completes with the given exit condition and the job's onTaskFailed property is 'performExitOptionsJobAction'.",
-          "description": "The default is none for exit code 0 and terminate for all other exit conditions. If the job's onTaskFailed property is noaction, then specifying this property returns an error and the add task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request).",
+          "description": "The default is none for exit code 0 and terminate for all other exit conditions. If the job's onTaskFailed property is noAction, then specifying this property returns an error and the add task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request).",
           "enum": [
             "none",
             "disable",
@@ -11370,7 +11370,7 @@
         "userIdentity": {
           "$ref": "#/definitions/UserIdentity",
           "title": "The user identity under which the Job Preparation task runs.",
-          "description": "If omitted, the task runs as a non-administrative user unique to the task on Windows nodes, or a a non-administrative user unique to the pool on Linux nodes."
+          "description": "If omitted, the task runs as a non-administrative user unique to the task on Windows nodes, or a non-administrative user unique to the pool on Linux nodes."
         },
         "rerunOnNodeRebootAfterSuccess": {
           "type": "boolean",
diff --git a/specification/batch/data-plane/Microsoft.Batch/stable/2018-03-01.6.1/BatchService.json b/specification/batch/data-plane/Microsoft.Batch/stable/2018-03-01.6.1/BatchService.json
index d474f05a9601..7e79e6181dcf 100644
--- a/specification/batch/data-plane/Microsoft.Batch/stable/2018-03-01.6.1/BatchService.json
+++ b/specification/batch/data-plane/Microsoft.Batch/stable/2018-03-01.6.1/BatchService.json
@@ -3251,7 +3251,7 @@
           "JobSchedule update": { "$ref": "./examples/JobScheduleUpdate.json" }
         },
         "summary": "Updates the properties of the specified job schedule.",
-        "description": "This fully replaces all the updateable properties of the job schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are unaffected.",
+        "description": "This fully replaces all the updatable properties of the job schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are unaffected.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -4569,7 +4569,7 @@
           "Job update": { "$ref": "./examples/JobUpdate.json" }
         },
         "summary": "Updates the properties of the specified job.",
-        "description": "This fully replaces all the updateable properties of the job. For example, if the job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.",
+        "description": "This fully replaces all the updatable properties of the job. For example, if the job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -7405,7 +7405,7 @@
           "Pool update": { "$ref": "./examples/PoolUpdate.json" }
         },
         "summary": "Updates the properties of the specified pool.",
-        "description": "This fully replaces all the updateable properties of the pool. For example, if the pool has a start task associated with it and if start task is not specified with this request, then the Batch service will remove the existing start task.",
+        "description": "This fully replaces all the updatable properties of the pool. For example, if the pool has a start task associated with it and if start task is not specified with this request, then the Batch service will remove the existing start task.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -9368,7 +9368,7 @@
           "Node update user": { "$ref": "./examples/NodeUpdateUser.json" }
         },
         "summary": "Updates the password and expiration time of a user account on the specified compute node.",
-        "description": "This operation replaces of all the updateable properties of the account. For example, if the expiryTime element is not specified, the current value is replaced with the default value, not left unmodified. You can update a user account on a node only when it is in the idle or running state.",
+        "description": "This operation replaces of all the updatable properties of the account. For example, if the expiryTime element is not specified, the current value is replaced with the default value, not left unmodified. You can update a user account on a node only when it is in the idle or running state.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -11303,7 +11303,7 @@
         "default": {
           "$ref": "#/definitions/ExitOptions",
           "title": "How the Batch service should respond if the task fails with an exit condition not covered by any of the other properties.",
-          "description": "This value is used if the task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behaviour on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection."
+          "description": "This value is used if the task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behavior on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection."
         }
       },
       "title": "Specifies how the Batch service should respond when the task completes."
@@ -11348,7 +11348,7 @@
         "jobAction": {
           "type": "string",
           "title": "An action to take on the job containing the task, if the task completes with the given exit condition and the job's onTaskFailed property is 'performExitOptionsJobAction'.",
-          "description": "The default is none for exit code 0 and terminate for all other exit conditions. If the job's onTaskFailed property is noaction, then specifying this property returns an error and the add task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request).",
+          "description": "The default is none for exit code 0 and terminate for all other exit conditions. If the job's onTaskFailed property is noAction, then specifying this property returns an error and the add task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request).",
           "enum": [
             "none",
             "disable",
@@ -11649,7 +11649,7 @@
         "userIdentity": {
           "$ref": "#/definitions/UserIdentity",
           "title": "The user identity under which the Job Preparation task runs.",
-          "description": "If omitted, the task runs as a non-administrative user unique to the task on Windows nodes, or a a non-administrative user unique to the pool on Linux nodes."
+          "description": "If omitted, the task runs as a non-administrative user unique to the task on Windows nodes, or a non-administrative user unique to the pool on Linux nodes."
         },
         "rerunOnNodeRebootAfterSuccess": {
           "type": "boolean",
diff --git a/specification/batch/data-plane/Microsoft.Batch/stable/2018-08-01.7.0/BatchService.json b/specification/batch/data-plane/Microsoft.Batch/stable/2018-08-01.7.0/BatchService.json
index 693ad843ae2e..59f829847444 100644
--- a/specification/batch/data-plane/Microsoft.Batch/stable/2018-08-01.7.0/BatchService.json
+++ b/specification/batch/data-plane/Microsoft.Batch/stable/2018-08-01.7.0/BatchService.json
@@ -3253,7 +3253,7 @@
           "JobSchedule update": { "$ref": "./examples/JobScheduleUpdate.json" }
         },
         "summary": "Updates the properties of the specified job schedule.",
-        "description": "This fully replaces all the updateable properties of the job schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are unaffected.",
+        "description": "This fully replaces all the updatable properties of the job schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are unaffected.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -4571,7 +4571,7 @@
           "Job update": { "$ref": "./examples/JobUpdate.json" }
         },
         "summary": "Updates the properties of the specified job.",
-        "description": "This fully replaces all the updateable properties of the job. For example, if the job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.",
+        "description": "This fully replaces all the updatable properties of the job. For example, if the job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -7407,7 +7407,7 @@
           "Pool update": { "$ref": "./examples/PoolUpdate.json" }
         },
         "summary": "Updates the properties of the specified pool.",
-        "description": "This fully replaces all the updateable properties of the pool. For example, if the pool has a start task associated with it and if start task is not specified with this request, then the Batch service will remove the existing start task.",
+        "description": "This fully replaces all the updatable properties of the pool. For example, if the pool has a start task associated with it and if start task is not specified with this request, then the Batch service will remove the existing start task.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -9370,7 +9370,7 @@
           "Node update user": { "$ref": "./examples/NodeUpdateUser.json" }
         },
         "summary": "Updates the password and expiration time of a user account on the specified compute node.",
-        "description": "This operation replaces of all the updateable properties of the account. For example, if the expiryTime element is not specified, the current value is replaced with the default value, not left unmodified. You can update a user account on a node only when it is in the idle or running state.",
+        "description": "This operation replaces of all the updatable properties of the account. For example, if the expiryTime element is not specified, the current value is replaced with the default value, not left unmodified. You can update a user account on a node only when it is in the idle or running state.",
         "x-ms-request-id": "request-id",
         "parameters": [
           {
@@ -11306,7 +11306,7 @@
         "default": {
           "$ref": "#/definitions/ExitOptions",
           "title": "How the Batch service should respond if the task fails with an exit condition not covered by any of the other properties.",
-          "description": "This value is used if the task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behaviour on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection."
+          "description": "This value is used if the task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behavior on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection."
         }
       },
       "title": "Specifies how the Batch service should respond when the task completes."
@@ -11351,7 +11351,7 @@
         "jobAction": {
           "type": "string",
           "title": "An action to take on the job containing the task, if the task completes with the given exit condition and the job's onTaskFailed property is 'performExitOptionsJobAction'.",
-          "description": "The default is none for exit code 0 and terminate for all other exit conditions. If the job's onTaskFailed property is noaction, then specifying this property returns an error and the add task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request).",
+          "description": "The default is none for exit code 0 and terminate for all other exit conditions. If the job's onTaskFailed property is noAction, then specifying this property returns an error and the add task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request).",
           "enum": [
             "none",
             "disable",
@@ -11652,7 +11652,7 @@
         "userIdentity": {
           "$ref": "#/definitions/UserIdentity",
           "title": "The user identity under which the Job Preparation task runs.",
-          "description": "If omitted, the task runs as a non-administrative user unique to the task on Windows nodes, or a a non-administrative user unique to the pool on Linux nodes."
+          "description": "If omitted, the task runs as a non-administrative user unique to the task on Windows nodes, or a non-administrative user unique to the pool on Linux nodes."
         },
         "rerunOnNodeRebootAfterSuccess": {
           "type": "boolean",
diff --git a/specification/batch/resource-manager/Microsoft.Batch/stable/2017-09-01/BatchManagement.json b/specification/batch/resource-manager/Microsoft.Batch/stable/2017-09-01/BatchManagement.json
index 25aa294e41df..8973929eee8b 100644
--- a/specification/batch/resource-manager/Microsoft.Batch/stable/2017-09-01/BatchManagement.json
+++ b/specification/batch/resource-manager/Microsoft.Batch/stable/2017-09-01/BatchManagement.json
@@ -3206,7 +3206,7 @@
           "description": "The virtual network must be in the same region and subscription as the Azure Batch account. The specified subnet should have enough free IP addresses to accommodate the number of nodes in the pool. If the subnet doesn't have enough free IP addresses, the pool will partially allocate compute nodes, and a resize error will occur. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet. The specified subnet must allow communication from the Azure Batch service to be able to schedule tasks on the compute nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the compute nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the compute nodes to unusable. For pools created via virtualMachineConfiguration the Batch account must have poolAllocationMode userSubscription in order to use a VNet. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication. For pools created with a virtual machine configuration, enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. For pools created with a cloud service configuration, enable ports 10100, 20100, and 30100. Also enable outbound connections to Azure Storage on port 443. For more details see: https://docs.microsoft.com/en-us/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration",
           "externalDocs": {
             "url": "https://azure.microsoft.com/en-us/documentation/articles/role-based-access-built-in-roles/#classic-virtual-machine-contributor",
-            "description": "Setting up RBAC for Azure Batch VNETs"
+            "description": "Setting up RBAC for Azure Batch VNets"
           }
         },
         "endpointConfiguration": {