Skip to content

Commit 7818b45

Browse files
committed
Add . to alt text
1 parent b75750e commit 7818b45

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/iot-edge/tutorial-nested-iot-edge-for-linux-on-windows.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ In this tutorial, the following network layers are defined:
4545

4646
This tutorial uses a two device hierarchy for simplicity, pictured below. One device, the **top layer device**, represents a device at the top layer of the hierarchy, which can connect directly to the cloud. This device will also be referred to as the **parent device**. The other device, the **lower layer device**, represents a device at the lower layer of the hierarchy, which can't connect directly to the cloud. You can add more lower layer devices to represent your production environment, as needed. Devices at lower layers will also be referred to as **child devices**.
4747

48-
![Diagram that shows the structure of the tutorial hierarchy, containing two devices: the top layer device and the lower layer device](./media/tutorial-nested-iot-edge/tutorial-hierarchy-diagram.png)
48+
![Diagram that shows the structure of the tutorial hierarchy, containing two devices: the top layer device and the lower layer device.](./media/tutorial-nested-iot-edge/tutorial-hierarchy-diagram.png)
4949

5050
## Prerequisites
5151

@@ -133,7 +133,7 @@ To use the `iotedge-config` tool to create and configure your hierarchy, follow
133133

134134
You can define the parent-child relationships manually as well. See the [create a gateway hierarchy](how-to-connect-downstream-iot-edge-device.md#create-a-gateway-hierarchy) section of the how-to guide to learn more.
135135

136-
![Screenshot of the edgedevices section of the configuration file allows you to define your hierarchy](./media/tutorial-nested-iot-edge/hierarchy-config-sample.png)
136+
![Screenshot of the edgedevices section of the configuration file allows you to define your hierarchy.](./media/tutorial-nested-iot-edge/hierarchy-config-sample.png)
137137

138138
1. Save and close the file:
139139

@@ -156,7 +156,7 @@ To use the `iotedge-config` tool to create and configure your hierarchy, follow
156156

157157
The configuration tool creates your IoT Edge devices and sets up the parent-child relationships between them. Optionally, it creates certificates for your devices to use. If paths to deployment JSONs are provided, the tool will automatically create these deployments to your devices, but this isn't required. Finally, the tool will generate the configuration bundles for your devices and place them in the output directory. For a thorough look at the steps taken by the configuration tool, see the log file in the output directory.
158158

159-
![Screenshot of the output of the script will display a topology of your hierarchy upon execution](./media/tutorial-nested-iot-edge/successful-setup-tool-run.png)
159+
![Screenshot of the output of the script will display a topology of your hierarchy upon execution.](./media/tutorial-nested-iot-edge/successful-setup-tool-run.png)
160160

161161
1. Navigate to your `output` directory and download the _lower-layer.zip_ and _top-layer.zip_ files.
162162
```bash
@@ -211,7 +211,7 @@ Each device needs its corresponding configuration bundle. You can use a USB driv
211211
```
212212
The output of the install script is pictured below.
213213

214-
![Screenshot of the output of the script installing the configuration bundles will update the config.toml files on your device and restart all IoT Edge services automatically](./media/tutorial-nested-iot-edge/configuration-install-output.png)
214+
![Screenshot of the output of the script installing the configuration bundles will update the config.toml files on your device and restart all IoT Edge services automatically.](./media/tutorial-nested-iot-edge/configuration-install-output.png)
215215

216216
1. Apply the correct certificate permissions and restart the IoT Edge runtime.
217217

0 commit comments

Comments
 (0)