Skip to content

Commit 9fb26a4

Browse files
authored
Merge pull request #125318 from changeworld/patch-52
Fix typo
2 parents 457cf0f + ed69390 commit 9fb26a4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/iot/iot-mqtt-connect-to-iot-dps.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,8 +74,8 @@ In a successful scenario, the device receives a response on the `$dps/registrati
7474

7575
The device must poll the service periodically to receive the result of the device registration operation. Assuming that the device has already subscribed to the `$dps/registrations/res/#` topic, it can publish a get operation status message to the `$dps/registrations/GET/iotdps-get-operationstatus/?$rid={request_id}&operationId={operationId}` topic name. The operation ID in this message should be the value received in the RegistrationOperationStatus response message in the previous step. In the successful case, the service responds on the `$dps/registrations/res/200/?$rid={request_id}` topic. The payload of the response contains the RegistrationOperationStatus object. The device should keep polling the service if the response code is 202 after a delay equal to the retry-after period. The device registration operation is successful if the service returns a 200 status code.
7676

77-
## Connecting over Websocket
78-
When connecting over Websocket, specify the subprotocol as `mqtt`. Follow [RFC 6455](https://tools.ietf.org/html/rfc6455).
77+
## Connecting over WebSocket
78+
When connecting over WebSocket, specify the subprotocol as `mqtt`. Follow [RFC 6455](https://tools.ietf.org/html/rfc6455).
7979

8080
## Next steps
8181

0 commit comments

Comments
 (0)