Update articles/iot-edge/how-to-provision-devices-at-scale-linux-tpm.md

Co-authored-by: Pat Altimore <[email protected]>

Author: MO2k4

articles/iot-edge/how-to-provision-devices-at-scale-linux-tpm.md

@@ -321,7 +321,7 @@ After the runtime is installed on your device, configure the device with the inf
 <!-- iotedge-1.4 -->
 :::moniker range=">=iotedge-1.4"
 
-7. Optionally, uncomment the `payload` parameter to specify the path to a local JSON file. The contents of the file will be [sent to DPS as additional data](../iot-dps/how-to-send-additional-data.md#iot-edge-support) when the device registers. This is useful for [custom allocation](../iot-dps/how-to-use-custom-allocation-policies.md). For example, if you want to allocate your devices based on an IoT Plug and Play model ID without human intervention.
+Optionally, uncomment the `payload` parameter to specify the path to a local JSON file. The contents of the file will be [sent to DPS as additional data](../iot-dps/how-to-send-additional-data.md#iot-edge-support) when the device registers. This is useful for [custom allocation](../iot-dps/how-to-use-custom-allocation-policies.md). For example, if you want to allocate your devices based on an IoT Plug and Play model ID without human intervention.
 :::moniker-end
 
 <!-- iotedge-2020-11 -->