Fix typos in EFLOW DMZ networking guide

- Fix 'UPC UA' to 'OPC UA' (line 45)
- Fix 'ehtX' to 'ethX' (line 115)

Author: jlian

articles/iot-edge/how-to-configure-iot-edge-for-linux-on-windows-iiot-dmz.md

@@ -42,7 +42,7 @@ For the other network, the EFLOW host device is physically connected to the DMZ
 Secure network:
 
 - No internet connectivity - access restricted.
-- PLCs or UPC UA-compatible devices connected.
+- PLCs or OPC UA-compatible devices connected.
 - EFLOW VM connected using an External virtual switch.
 
 DMZ:
@@ -112,7 +112,7 @@ Once complete, you have the *OnlineOPCUA* switch assigned to the EFLOW VM. To ch
 
 ## Configure VM network routing 
 
-When using the EFLOW multiple NICs feature, you may want to set up the different route priorities. By default, EFLOW creates one *default* route per *ehtX* interface assigned to the VM. EFLOW assigns the default route a random priority. If all interfaces are connected to the internet, random priorities may not be a problem. However, if one of the NICs is connected to an *offline* network, you may want to prioritize the *online* NIC over the *offline* NIC to get the EFLOW VM connected to the internet.
+When using the EFLOW multiple NICs feature, you may want to set up the different route priorities. By default, EFLOW creates one *default* route per *ethX* interface assigned to the VM. EFLOW assigns the default route a random priority. If all interfaces are connected to the internet, random priorities may not be a problem. However, if one of the NICs is connected to an *offline* network, you may want to prioritize the *online* NIC over the *offline* NIC to get the EFLOW VM connected to the internet.
 
 EFLOW uses the [route](https://man7.org/linux/man-pages/man8/route.8.html) service to manage the network routing alternatives. In order to check the available EFLOW VM routes, use the following steps: