Regenerated library to pick up latest schema changes

Author: petemoore

codegenerator/model/model-data.txt

@@ -6490,7 +6490,7 @@ failed instead of exception. You should `reportException` if,
   * Declared actions cannot be executed due to unavailable resources,
   * The worker had to shutdown prematurely,
   * The worker experienced an unknown error, or,
-  * The task explicitely requested a retry.
+  * The task explicitly requested a retry.
 
 Do not use this to signal that some user-specified code crashed for any
 reason specific to this code. If user-specific code hits a resource that
@@ -7446,7 +7446,7 @@ Properties
           [REST API](http://msdn.microsoft.com/en-us/library/azure/dd179474.aspx)
           for details.
           When you have a message you can use `claimTask` to claim the task.
-          You will need to parse the XML reponse and base64 decode and
+          You will need to parse the XML response and base64 decode and
           JSON parse the `MessageText`.
           After you have called `claimTask` you **must** us the
           `signedDeleteUrl` to delete the message.
@@ -8287,7 +8287,7 @@ Properties
     convention in this case to create an artifact entitled
     `public/superseded-by` containing the taskId of the task that superseded
     this one.
-    **Report `intermittent-task`** if the task explicitely requested a retry
+    **Report `intermittent-task`** if the task explicitly requested a retry
     because task is intermittent. Workers can choose whether or not to
     support this, but workers shouldn't blindly report this for every task
     that fails.

src/main/java/org/mozilla/taskcluster/client/queue/PollTaskUrlsResponse.java

@@ -44,7 +44,7 @@ public class SignedURLsForAQueue {
          * [REST API](http://msdn.microsoft.com/en-us/library/azure/dd179474.aspx)
          * for details.
          * When you have a message you can use `claimTask` to claim the task.
-         * You will need to parse the XML reponse and base64 decode and
+         * You will need to parse the XML response and base64 decode and
          * JSON parse the `MessageText`.
          * After you have called `claimTask` you **must** us the
          * `signedDeleteUrl` to delete the message.

src/main/java/org/mozilla/taskcluster/client/queue/Queue.java

@@ -350,7 +350,7 @@ public CallSummary<EmptyPayload, TaskStatusResponse> reportFailed(String taskId,
      *   * Declared actions cannot be executed due to unavailable resources,
      *   * The worker had to shutdown prematurely,
      *   * The worker experienced an unknown error, or,
-     *   * The task explicitely requested a retry.
+     *   * The task explicitly requested a retry.
      * 
      * Do not use this to signal that some user-specified code crashed for any
      * reason specific to this code. If user-specific code hits a resource that

src/main/java/org/mozilla/taskcluster/client/queue/TaskExceptionRequest.java

@@ -39,7 +39,7 @@ public class TaskExceptionRequest {
      * convention in this case to create an artifact entitled
      * `public/superseded-by` containing the taskId of the task that superseded
      * this one.
-     * **Report `intermittent-task`** if the task explicitely requested a retry
+     * **Report `intermittent-task`** if the task explicitly requested a retry
      * because task is intermittent. Workers can choose whether or not to
      * support this, but workers shouldn't blindly report this for every task
      * that fails.