Fix links.

Author: robinsh

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

@@ -40,7 +40,7 @@ There are _device SDKs_ available for multiple languages that enable you to crea
 
 ## Azure IoT Explorer
 
-The [Azure IoT Explorer](iot-pnp/howto-install-iot-explorer.md) is used to view the telemetry the device is sending, work with device properties, and call commands. You can also use the explorer to interact with and test your devices.
+The [Azure IoT Explorer](https://github.com/Azure/azure-iot-explorer) is used to view the telemetry the device is sending, work with device properties, and call commands. You can also use the explorer to interact with and test your devices, and to manage plug and play devices.
 
 ## Azure IoT service SDKs
 
@@ -140,7 +140,7 @@ Device data refers to the per-device data stored in the IoT Hub [identity regist
 
 ## Device explorer
 
-The device explorer has been replaced with the [Azure IoT Explorer](#azure-iot-explorer), which is used to view the telemetry a device is sending, work with device properties, and call commands. You can also use the explorer to interact with and test your devices.
+The device explorer has been replaced with the [Azure IoT Explorer](https://github.com/Azure/azure-iot-explorer), which is used to view the telemetry the device is sending, work with device properties, and call commands. You can also use the explorer to interact with and test your devices, and to manage plug and play devices.
 
 ## Device identity
 

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

@@ -152,7 +152,7 @@ Azure Provisioning device and service SDKs for Node.js:
 
 Azure Provisioning device and service SDKs for Python:
 
-* [Source code](https://github.com/Azure/azure-iot-device)
+* [Source code](https://github.com/Azure/azure-iot-sdk-python)
 * Download [Device SDK](https://pypi.org/project/azure-iot-device/) and [Service SDK](https://pypi.org/project/azure-iothub-provisioningserviceclient/) from pip
 
 ## Next steps

articles/iot-hub/iot-hub-device-sdk-c-intro.md

@@ -68,7 +68,7 @@ Now that you have the sample source code, the next thing to do is to get a set o
 
 There are several open source tools to help you manage your IoT hub.
 
-* A Windows application called [device explorer](https://github.com/Azure/azure-iot-sdk-csharp/tree/master/tools/DeviceExplorer).
+* A Windows application called [Azure IoT Explorer](https://github.com/Azure/azure-iot-explorer).
 
 * A cross-platform Visual Studio Code extension called [Azure IoT Tools](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-tools).
 

articles/iot-hub/iot-hub-mqtt-support.md

@@ -19,7 +19,7 @@ IoT Hub is not a full-featured MQTT broker and does not support all the behavior
 
 [!INCLUDE [iot-hub-basic](../../includes/iot-hub-basic-partial.md)]
 
-All device communication with IoT Hub must be secured using TLS/SSL. Therefore, IoT Hub doesn’t support non-secure connections over port 1883.
+All device communication with IoT Hub must be secured using TLS/SSL. Therefore, IoT Hub doesn't support non-secure connections over port 1883.
 
 ## Connecting to IoT Hub
 
@@ -112,7 +112,7 @@ If a device cannot use the device SDKs, it can still connect to the public devic
 
   For more information about how to generate SAS tokens, see the device section of [Using IoT Hub security tokens](iot-hub-devguide-security.md#use-sas-tokens-in-a-device-app).
 
-  When testing, you can also use the cross-platform [Azure IoT Tools for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-tools) or the [Device Explorer](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/tools/DeviceExplorer) tool to quickly generate a SAS token that you can copy and paste into your own code:
+  When testing, you can also use the cross-platform [Azure IoT Tools for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-tools) or the CLI extension command [az iot hub generate-sas-token](/cli/azure/ext/azure-cli-iot-ext/iot/hub?view=azure-cli-latest#ext-azure-cli-iot-ext-az-iot-hub-generate-sas-token) to quickly generate a SAS token that you can copy and paste into your own code:
 
 ### For Azure IoT Tools
 
@@ -124,16 +124,6 @@ If a device cannot use the device SDKs, it can still connect to the public devic
 
 4. The SAS token is created and copied to clipboard.
 
-### For Device Explorer
-
-1. Go to the **Management** tab in **Device Explorer**.
-
-2. Click **SAS Token** (top right).
-
-3. On **SASTokenForm**, select your device in the **DeviceID** drop down. Set your **TTL**.
-
-4. Click **Generate** to create your token.
-
    The SAS token that's generated has the following structure:
 
    `HostName={your hub name}.azure-devices.net;DeviceId=javadevice;SharedAccessSignature=SharedAccessSignature sr={your hub name}.azure-devices.net%2Fdevices%2FMyDevice01%2Fapi-version%3D2016-11-14&sig=vSgHBMUG.....Ntg%3d&se=1456481802`
@@ -353,7 +343,7 @@ The following sequence describes how a device updates the reported properties in
 
 3. The service then sends a response message that contains the new ETag value for the reported properties collection on topic `$iothub/twin/res/{status}/?$rid={request id}`. This response message uses the same **request ID** as the request.
 
-The request message body contains a JSON document, that contains new values for reported properties. Each member in the JSON document updates or add the corresponding member in the device twin’s document. A member set to `null`, deletes the member from the containing object. For example:
+The request message body contains a JSON document, that contains new values for reported properties. Each member in the JSON document updates or add the corresponding member in the device twin's document. A member set to `null`, deletes the member from the containing object. For example:
 
 ```json
 {