IoT Hub: terminology update

Author: elioda

articles/iot-hub/iot-hub-csharp-csharp-direct-methods.md

@@ -39,14 +39,14 @@ To complete this tutorial you need the following:
 [!INCLUDE [iot-hub-get-started-create-hub-pp](../../includes/iot-hub-get-started-create-hub-pp.md)]
 
 ## Create a simulated device app
-In this section, you create a Node.js console app that responds to a method called by the cloud.
+In this section, you create a Node.js console app that responds to a method called by the back end.
 
 1. Create a new empty folder called **simulateddevice**. In the **simulateddevice** folder, create a package.json file using the following command at your command-prompt. Accept all the defaults:
 
     ```
     npm init
     ```
-2. At your command-prompt in the **simulateddevice** folder, run the following command to install the **azure-iot-device** Device SDK package and **azure-iot-device-mqtt** package:
+2. At your command-prompt in the **simulateddevice** folder, run the following command to install the **azure-iot-device** and **azure-iot-device-mqtt** packages:
    
     ```
         npm install azure-iot-device azure-iot-device-mqtt --save
@@ -66,7 +66,7 @@ In this section, you create a Node.js console app that responds to a method call
     var connectionString = '{device connection string}';
     var client = DeviceClient.fromConnectionString(connectionString, Mqtt);
     ```
-6. Add the following function to implement the method on the device:
+6. Add the following function to implement the direct method on the device:
    
     ```
     function onWriteLine(request, response) {
@@ -81,7 +81,7 @@ In this section, you create a Node.js console app that responds to a method call
         });
     }
     ```
-7. Open the connection to your IoT hub and start initialize the method listener:
+7. Open the connection to your IoT hub and initialize the method listener:
    
     ```
     client.open(function(err) {
@@ -100,8 +100,8 @@ In this section, you create a Node.js console app that responds to a method call
 > 
 > 
 
-## Call a method on a device
-In this section, you create a Node.js console app that calls a method on the simulated device and then displays the response.
+## Call a direct method on a device
+In this section, you create a .NET console app that calls a method on the simulated device and then displays the response.
 
 1. In Visual Studio, add a Visual C# Windows Classic Desktop project to the current solution by using the **Console Application** project template. Make sure the .NET Framework version is 4.5.1 or later. Name the project **CallMethodOnDevice**.
    

articles/iot-hub/iot-hub-devguide-direct-methods.md

@@ -19,26 +19,26 @@ ms.author: nberdy
 ---
 # Invoke a direct method on a device
 ## Overview
-IoT Hub gives you ability to invoke methods on devices from the cloud. Methods represent a request-reply interaction with a device similar to an HTTP call in that they succeed or fail immediately (after a user-specified timeout). This is useful for scenarios where the course of immediate action is different depending on whether the device was able to respond, such as sending an SMS wake-up to a device if a device is offline (SMS being more expensive than a method call).
+IoT Hub gives you ability to invoke direct methods on devices from the cloud. Direct methods represent a request-reply interaction with a device similar to an HTTP call in that they succeed or fail immediately (after a user-specified timeout). This is useful for scenarios where the course of immediate action is different depending on whether the device was able to respond, such as sending an SMS wake-up to a device if a device is offline (SMS being more expensive than a method call).
 
-Each device method targets a single device. [Jobs][lnk-devguide-jobs] provide a way to invoke methods on multiple devices, and schedule method invocation for disconnected devices.
+Each device method targets a single device. [Jobs][lnk-devguide-jobs] provide a way to invoke direct methods on multiple devices, and schedule method invocation for disconnected devices.
 
 Anyone with **service connect** permissions on IoT Hub may invoke a method on a device.
 
 ### When to use
-Methods follow a request-response pattern and are meant for communications that require immediate confirmation of their result, usually interactive control of the device, e.g. turn on a fan.
+Direct methods follow a request-response pattern and are meant for communications that require immediate confirmation of their result, usually interactive control of the device, for example to turn on a fan.
 
 Refer to [Cloud-to-device communication guidance][lnk-c2d-guidance] if in doubt between using desired properties, direct methods, or cloud-to-device messages.
 
 ## Method lifecycle
-Methods are implemented on the device and may require zero or more inputs in the method payload to correctly instantiate. You invoke a direct method through a service-facing URI (`{iot hub}/twins/{device id}/methods/`). A device receives direct methods through a device-specific MQTT topic (`$iothub/methods/POST/{method name}/`). We may support methods on additional device-side networking protocols in the future.
+Direct methods are implemented on the device and may require zero or more inputs in the method payload to correctly instantiate. You invoke a direct method through a service-facing URI (`{iot hub}/twins/{device id}/methods/`). A device receives direct methods through a device-specific MQTT topic (`$iothub/methods/POST/{method name}/`). We may support direct methods on additional device-side networking protocols in the future.
 
 > [!NOTE]
 > When you invoke a direct method on a device, property names and values can only contain US-ASCII printable alphanumeric, except any in the following set: ``{'$', '(', ')', '<', '>', '@', ',', ';', ':', '\', '"', '/', '[', ']', '?', '=', '{', '}', SP, HT}``.
 > 
 > 
 
-Methods are synchronous and either succeed or fail after the timeout period (default: 30 seconds, settable up to 3600 seconds). Methods are useful in interactive scenarios where you want a device to act if and only if the device is online and receiving commands, such as turning on a light from a phone. In these scenarios, you want to see an immediate success or failure so the cloud service can act on the result as soon as possible. The device may return some message body as a result of the method, but it isn't required for the method to do so. There is no guarantee on ordering or any concurrency semantics on method calls.
+Direct methods are synchronous and either succeed or fail after the timeout period (default: 30 seconds, settable up to 3600 seconds). Direct methods are useful in interactive scenarios where you want a device to act if and only if the device is online and receiving commands, such as turning on a light from a phone. In these scenarios, you want to see an immediate success or failure so the cloud service can act on the result as soon as possible. The device may return some message body as a result of the method, but it isn't required for the method to do so. There is no guarantee on ordering or any concurrency semantics on method calls.
 
 Device method calls are HTTP-only from the cloud side, and MQTT-only from the device side.
 

articles/iot-hub/iot-hub-devguide-query-language.md

@@ -167,7 +167,7 @@ Note how the **query** object is instantiated with a page size (up to 1000), and
 It is important to note that the query object exposes multiple **next\***, depending on the deserialization option required by the query, such as device twin or job objects, or plain Json to be used when using projections.
 
 ### Limitations
-Currently, comparisons are supported only between primitive types (i.e. no objects), for instance `... WHERE properties.desired.config = properties.reported.config` is supported only if those properties have primitive values.
+Currently, comparisons are supported only between primitive types (no objects), for instance `... WHERE properties.desired.config = properties.reported.config` is supported only if those properties have primitive values.
 
 ## Getting started with jobs queries
 [Jobs][lnk-jobs] provide a way to execute operations on sets of devices. Each device twin contains the information of the jobs of which it is part in a collection called **jobs**.
@@ -200,7 +200,7 @@ Logically,
             ]                                                             
         }
 
-Currently, this collection is queriable as **devices.jobs** in the IoT Hub query language.
+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 (i.e. queries that contains 'FROM devices'). It can only be accessed directly with queries using `FROM devices.jobs`.

articles/iot-hub/iot-hub-devguide.md

@@ -24,7 +24,7 @@ Azure IoT Hub provides you with:
 
 * Secure communications by using per-device security credentials and access control.
 * Multiple device-to-cloud and cloud-to-device hyper-scale communication options.
-* A queriable storage of per-device state information and meta-data.
+* A queryable storage of per-device state information and meta-data.
 * Easy device connectivity with device libraries for the most popular languages and platforms.
 
 This IoT Hub developer guide includes the following articles: