Merge pull request #235296 from PatAltimore/patricka-update-cert-store

Fix update-ca for distributions

Author: prmerger-automator[bot]

articles/iot-edge/how-to-connect-downstream-iot-edge-device.md

@@ -225,9 +225,9 @@ To enable secure connections, every IoT Edge parent device in a gateway scenario
     ```bash
     # Update the certificate store
 
-    # For Ubuntu and Debian, use update-ca-certificates command
+    # For Ubuntu or Debian - use update-ca-certificates
     sudo update-ca-certificates
-    # For EFLOW, use update-ca-trust
+    # For EFLOW or RHEL - use update-ca-trust
     sudo update-ca-trust
     ```
 
@@ -447,9 +447,9 @@ To enable secure connections, every IoT Edge downstream device in a gateway scen
     ```bash
     # Update the certificate store
 
-    # For Ubuntu and Debian, use update-ca-certificates command
+    # For Ubuntu or Debian - use update-ca-certificates
     sudo update-ca-certificates
-    # For EFLOW, use update-ca-trust
+    # For EFLOW or RHEL - use update-ca-trust
     sudo update-ca-trust
     ```
 

articles/iot-edge/how-to-manage-device-certificates.md

@@ -173,15 +173,15 @@ Using a self-signed certificate authority (CA) certificate as a root of trust wi
 
 Installing the certificate to the trust bundle file makes it available to container modules but not to host modules like Azure Device Update or Defender. If you use host level components or run into other TLS issues, also install the root CA certificate to the operating system certificate store:
 
-# [Linux](#tab/linux)
+# [Debian / Ubuntu](#tab/ubuntu)
 
   ```bash
   sudo cp /var/aziot/certs/my-root-ca.pem /usr/local/share/ca-certificates/my-root-ca.pem.crt
 
-  sudo update-ca-trust
+  sudo update-ca-certificates
   ```
 
-# [IoT Edge for Linux on Windows (EFLOW)](#tab/windows)
+# [EFLOW / RHEL](#tab/windows)
 
   ```bash
   sudo cp /var/aziot/certs/my-root-ca.pem /etc/pki/ca-trust/source/anchors/my-root-ca.pem.crt