Skip to content

Commit 7ca291f

Browse files
committed
Adjusted image size to be more uniform
1 parent 2ee0d01 commit 7ca291f

File tree

6 files changed

+5
-5
lines changed

6 files changed

+5
-5
lines changed

articles/iot-edge/about-iot-edge.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ The Azure IoT Edge runtime runs on a large set of IoT devices that enables using
6161

6262
It's difficult to manage the software life cycle for millions of IoT devices that are often different makes and models or geographically scattered. Workloads are created and configured for a particular type of device, deployed to all of your devices, and monitored to catch any misbehaving devices. These activities can't be done on a per device basis and must be done at scale.
6363

64-
Azure IoT Edge integrates seamlessly with [Azure IoT Central](/azure/iot-central/) to provide one control plane for your solution's needs. Cloud services allow you to:
64+
Azure IoT Edge integrates seamlessly with [Azure IoT Central](../iot-central/index.yml) to provide one control plane for your solution's needs. Cloud services allow you to:
6565

6666
* Create and configure a workload to be run on a specific type of device.
6767
* Send a workload to a set of devices.
-11.3 KB
Loading
-2.48 KB
Loading
-8.13 KB
Loading
-12.1 KB
Loading

articles/iot-edge/quickstart.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ Run the following PowerShell commands on the target device where you want to dep
155155

156156
1. Enter 'O' or 'R' to toggle **Optional diagnostic data** on or off, depending on your preference. A successful deployment is pictured below.
157157

158-
:::image type="content" source="./media/quickstart/successful-powershell-deployment.png" alt-text="Screenshot that show that a successful deployment will say Deployment successful at the end of the messages in the console.":::
158+
:::image type="content" source="./media/quickstart/successful-powershell-deployment.png" alt-text="Screenshot that show that a successful deployment will say Deployment successful at the end of the messages in the console." lightbox="./media/quickstart/successful-powershell-deployment.png":::
159159

160160
1. Provision your device using the device connection string that you retrieved in the previous section. Replace the placeholder text with your own value.
161161

@@ -215,7 +215,7 @@ Follow these steps to deploy your first module from Azure Marketplace.
215215

216216
You should see three modules: **$edgeAgent**, **$edgeHub**, and **SimulatedTemperatureSensor**. If one or more of the modules has **Yes** under **Specified in Deployment** but not under **Reported by Device**, your IoT Edge device is still starting them. Wait a few minutes, and then refresh the page.
217217

218-
:::image type="content" source="./media/quickstart-linux/view-deployed-modules.png" alt-text="Screenshot that shows the Simulated Temperature Sensor in the list of deployed modules..":::
218+
:::image type="content" source="./media/quickstart-linux/view-deployed-modules.png" alt-text="Screenshot that shows the Simulated Temperature Sensor in the list of deployed modules." lightbox="./media/quickstart-linux/view-deployed-modules.png":::
219219

220220
## View the generated data
221221

@@ -238,7 +238,7 @@ The module that you pushed generates sample environment data that you can use fo
238238
sudo iotedge list
239239
```
240240

241-
:::image type="content" source="./media/quickstart/iotedge-list-screen.png" alt-text="Screenshot that shows where to verify that your temperature sensor, agent, and hub modules are running.":::
241+
:::image type="content" source="./media/quickstart/iotedge-list-screen.png" alt-text="Screenshot that shows where to verify that your temperature sensor, agent, and hub modules are running." lightbox="./media/quickstart/iotedge-list-screen.png":::
242242

243243
1. View the messages being sent from the temperature sensor module to the cloud using the following Linux command:
244244

@@ -249,7 +249,7 @@ The module that you pushed generates sample environment data that you can use fo
249249
>[!IMPORTANT]
250250
>IoT Edge commands are case-sensitive when they refer to module names.
251251
252-
:::image type="content" source="./media/quickstart/temperature-sensor-screen.png" alt-text="Screenshot that shows the output logs of the Simulated Temperature Sensor module when it's running.":::
252+
:::image type="content" source="./media/quickstart/temperature-sensor-screen.png" alt-text="Screenshot that shows the output logs of the Simulated Temperature Sensor module when it's running." lightbox="./media/quickstart/temperature-sensor-screen.png":::
253253

254254
You can also use the [Azure IoT Hub extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-toolkit) to watch messages arrive at your IoT hub.
255255

0 commit comments

Comments
 (0)