Skip to content

Commit d3e1dbb

Browse files
committed
Fixed some typos.
1 parent 5cb2072 commit d3e1dbb

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Direct method invocations on a device are HTTPS calls that are made up of the fo
7070
7171
The value provided as `responseTimeoutInSeconds` in the request is the amount of time that IoT Hub service must await for completion of a direct method execution on a device. Set this timeout to be at least as long as the expected execution time of a direct method by a device. If timeout is not provided, it the default value of 30 seconds is used. The maximum value for `responseTimeoutInSeconds` is 300 seconds.
7272
73-
The value provided as `connectTimeoutInSeconds` in the request is the amount of time that IoT Hub serivce must await for a disconnected device to come online. The default value is 0, meaning that devices must already be online upon invocation of a direct method. The maximum calue for `connectTimeoutInSeconds` is 300 seconds.
73+
The value provided as `connectTimeoutInSeconds` in the request is the amount of time that IoT Hub service must await for a disconnected device to come online. The default value is 0, meaning that devices must already be online upon invocation of a direct method. The maximum value for `connectTimeoutInSeconds` is 300 seconds.
7474
7575
7676
#### Example
@@ -98,7 +98,7 @@ The back-end app receives a response that is made up of the following items:
9898

9999
* *HTTP status code*:
100100
* 200 indicates successful execution of direct method;
101-
* 404 indicates that eitehr device ID is not valid, or that the device was not connected during the `connectTimeoutInSeconds` (use accompanied error message to understand the root cause);
101+
* 404 indicates that either device ID is not valid, or that the device was not connected during the `connectTimeoutInSeconds` (use accompanied error message to understand the root cause);
102102
* 504 indicates gateway timeout caused by device responding to a direct method call within `responseTimeoutInSeconds`.
103103

104104
* *Headers* that contain the ETag, request ID, content type, and content encoding.

0 commit comments

Comments
 (0)