Merge pull request #219234 from kgremban/nov21-101470

Fix jobType property in query article

Author: prmerger-automator[bot]

articles/iot-hub/query-jobs.md

@@ -29,7 +29,7 @@ Here's a sample IoT hub device twin that is part of a job called **myJobId**:
         {
             "deviceId": "myDeviceId",
             "jobId": "myJobId",
-            "jobType": "scheduleTwinUpdate",
+            "jobType": "scheduleUpdateTwin",
             "status": "completed",
             "startTimeUtc": "2016-09-29T18:18:52.7418462",
             "endTimeUtc": "2016-09-29T18:20:52.7418462",
@@ -47,7 +47,7 @@ Here's a sample IoT hub device twin that is part of a job called **myJobId**:
 Currently, this collection is queryable as **devices.jobs** in the IoT Hub query language.
 
 > [!IMPORTANT]
-> Currently, the jobs property is never returned when querying device twins. That is, queries that contain `FROM devices`. The jobs property can only be accessed directly with queries using `FROM devices.jobs`.
+> Currently, the jobs property is not returned when querying device twins. That is, queries that contain `FROM devices`. The jobs property can only be accessed directly with queries using `FROM devices.jobs`.
 
 For example, the following query returns all jobs (past and scheduled) that affect a single device:
 
@@ -65,7 +65,7 @@ For example, the following query retrieves all completed device twin update jobs
 ```sql
 SELECT * FROM devices.jobs
   WHERE devices.jobs.deviceId = 'myDeviceId'
-    AND devices.jobs.jobType = 'scheduleTwinUpdate'
+    AND devices.jobs.jobType = 'scheduleUpdateTwin'
     AND devices.jobs.status = 'completed'
     AND devices.jobs.createdTimeUtc > '2016-09-01'
 ```