Apply suggestions from code review

Co-authored-by: Cristian Pop <[email protected]>

Author: kgremban

articles/iot-hub/module-twins-cli.md

@@ -39,7 +39,7 @@ This article shows you how to create an Azure CLI session in which you:
 You can use symmetric keys or X.509 certificates to authenticate module identities. For X.509 certificate authentication, the module's certificate *must* have its common name (CN) formatted like `CN=<deviceid>/<moduleid>`. For example:
 
 ```bash
-openssl req -new -key d1m1.key.pm -out d1m1.csr -subj "/CN=device01\/module01"
+openssl req -new -key d1m1.key.pem -out d1m1.csr -subj "/CN=device01\/module01"
 ```
 
 ## Prepare the Cloud Shell

articles/iot-hub/module-twins-dotnet.md

@@ -40,7 +40,7 @@ At the end of this article, you have two .NET console apps:
 You can use symmetric keys or X.509 certificates to authenticate module identities. For X.509 certificate authentication, the module's certificate *must* have its common name (CN) formatted like `CN=<deviceid>/<moduleid>`. For example:
 
 ```bash
-openssl req -new -key d1m1.key.pm -out d1m1.csr -subj "/CN=device01\/module01"
+openssl req -new -key d1m1.key.pem -out d1m1.csr -subj "/CN=device01\/module01"
 ```
 
 ## Get the IoT hub connection string

articles/iot-hub/module-twins-node.md

@@ -40,7 +40,7 @@ At the end of this article, you have two Node.js apps:
 You can use symmetric keys or X.509 certificates to authenticate module identities. For X.509 certificate authentication, the module's certificate *must* have its common name (CN) formatted like `CN=<deviceid>/<moduleid>`. For example:
 
 ```bash
-openssl req -new -key d1m1.key.pm -out d1m1.csr -subj "/CN=device01\/module01"
+openssl req -new -key d1m1.key.pem -out d1m1.csr -subj "/CN=device01\/module01"
 ```
 
 ## Get the IoT hub connection string

articles/iot-hub/module-twins-portal-dotnet.md

@@ -41,7 +41,7 @@ In this article, you will learn how to:
 You can use symmetric keys or X.509 certificates to authenticate module identities. For X.509 certificate authentication, the module's certificate *must* have its common name (CN) formatted like `CN=<deviceid>/<moduleid>`. For example:
 
 ```bash
-openssl req -new -key d1m1.key.pm -out d1m1.csr -subj "/CN=device01\/module01"
+openssl req -new -key d1m1.key.pem -out d1m1.csr -subj "/CN=device01\/module01"
 ```
 
 ## Create a module identity in the portal

articles/iot-hub/module-twins-python.md

@@ -44,7 +44,7 @@ At the end of this article, you have three Python apps:
 You can use symmetric keys or X.509 certificates to authenticate module identities. For X.509 certificate authentication, the module's certificate *must* have its common name (CN) formatted like `CN=<deviceid>/<moduleid>`. For example:
 
 ```bash
-openssl req -new -key d1m1.key.pm -out d1m1.csr -subj "/CN=device01\/module01"
+openssl req -new -key d1m1.key.pem -out d1m1.csr -subj "/CN=device01\/module01"
 ```
 
 ## Get the IoT hub connection string