Merge pull request #184381 from v-steveadams/correct-net-version

Correct .NET version in prereqs

Author: PRMerger-2

articles/iot-dps/quick-create-simulated-device-symm-key.md

@@ -34,7 +34,7 @@ This quickstart demonstrates a solution for a Windows-based workstation. However
 
 ::: zone pivot="programming-language-csharp"
 
-* Install [.NET 6.0 SDK](https://dotnet.microsoft.com/download) on your Windows-based machine. You can use the following command to check your version.
+* Install [.NET Core 3.1 SDK](https://dotnet.microsoft.com/download) or later on your Windows-based machine. You can use the following command to check your version.
 
     ```cmd
     dotnet --info

articles/iot-dps/quick-create-simulated-device-tpm.md

@@ -44,7 +44,7 @@ The following prerequisites are for a Windows development environment. For Linux
 
 * A TPM 2.0 hardware security module on your Windows-based machine.
 
-* Install [.NET 6.0 SDK](https://dotnet.microsoft.com/download) on your Windows-based machine. You can use the following command to check your version.
+* Install [.NET Core 3.1 SDK](https://dotnet.microsoft.com/download) or later on your Windows-based machine. You can use the following command to check your version.
 
     ```bash
     dotnet --info

articles/iot-dps/quick-create-simulated-device-x509.md

@@ -37,7 +37,7 @@ The following prerequisites are for a Windows development environment. For Linux
 
 ::: zone pivot="programming-language-csharp"
 
-* Install [.NET Core 3.1 SDK or later](https://dotnet.microsoft.com/download) or later on your Windows-based machine. You can use the following command to check your version.
+* Install [.NET Core 3.1 SDK](https://dotnet.microsoft.com/download) or later on your Windows-based machine. You can use the following command to check your version.
 
     ```bash
     dotnet --info
@@ -47,7 +47,7 @@ The following prerequisites are for a Windows development environment. For Linux
 
 ::: zone pivot="programming-language-nodejs"
 
-* Install [Node.js v4.0 or above](https://nodejs.org) or later on your machine.
+* Install [Node.js v4.0 or above](https://nodejs.org) on your machine.
 
 * Install [OpenSSL](https://www.openssl.org/) on your machine and is added to the environment variables accessible to the command window. This library can either be built and installed from source or downloaded and installed from a [third party](https://wiki.openssl.org/index.php/Binaries) such as [this](https://sourceforge.net/projects/openssl/).
 
@@ -277,7 +277,7 @@ In addition to the tooling in the C SDK, the [Group certificate verification sam
     ----------------  End Nesting Level 1  ----------------
       Provider = Microsoft Strong Cryptographic Provider
     Signature test passed
-    CertUtil: -dump command completed successfully.    
+    CertUtil: -dump command completed successfully.
     ```
 
 ::: zone-end
@@ -339,15 +339,15 @@ A test certificate file (*python-device.pem*) and private key file (*python-devi
     java -jar ./provisioning-x509-cert-generator-{version}-with-deps.jar
     ```
 
-3. Enter **N** for _Do you want to input common name_. 
+3. Enter **N** for _Do you want to input common name_.
 
 4. Copy the output of `Client Cert` to the clipboard, starting from *-----BEGIN CERTIFICATE-----* through *-----END CERTIFICATE-----*.
 
    ![Individual certificate generator](./media/quick-create-simulated-device-x509/cert-generator-java.png)
 
 5. Create a file named *_X509individual.pem_* on your Windows machine.
 
-6. Open *_X509individual.pem_* in an editor of your choice, and copy the clipboard contents to this file. 
+6. Open *_X509individual.pem_* in an editor of your choice, and copy the clipboard contents to this file.
 
 7. Save the file and close your editor.
 
@@ -433,16 +433,16 @@ This article demonstrates an individual enrollment for a single device to be pro
 
 6. In the **Add Enrollment** panel, enter the following information:
    * Select **X.509** as the identity attestation *Mechanism*.
-   * Under the *Primary certificate .pem or .cer file*, choose *Select a file* to select the certificate file *X509individual.pem* created in the previous steps.  
+   * Under the *Primary certificate .pem or .cer file*, choose *Select a file* to select the certificate file *X509individual.pem* created in the previous steps.
    * Optionally, you may provide the following information:
      * Select an IoT hub linked with your provisioning service.
-     * Enter a unique device ID. Make sure to avoid sensitive data while naming your device. 
+     * Enter a unique device ID. Make sure to avoid sensitive data while naming your device.
      * Update the **Initial device twin state** with the desired initial configuration for the device.
-    
+
     :::image type="content" source="./media/quick-create-simulated-device-x509/device-enrollment.png" alt-text="Add device as individual enrollment with X.509 attestation.":::
 
 ::: zone-end
-    
+
 7. Select **Save**. You'll be returned to **Manage enrollments**.
 
 8. Select **Individual Enrollments**. Your X.509 enrollment entry should appear in the registration table.
@@ -461,7 +461,7 @@ In this section, we'll update the sample code to send the device's boot sequence
 
 3. In Visual Studio's *Solution Explorer* window, navigate to the **Provision\_Samples** folder. Expand the sample project named **prov\_dev\_client\_sample**. Expand **Source Files**, and open **prov\_dev\_client\_sample.c**.
 
-4. Find the `id_scope` constant, and replace the value with your **ID Scope** value that you copied earlier. 
+4. Find the `id_scope` constant, and replace the value with your **ID Scope** value that you copied earlier.
 
     ```c
     static const char* id_scope = "0ne00002193";
@@ -539,7 +539,7 @@ In this section, we'll update the sample code to send the device's boot sequence
 
 ::: zone pivot="programming-language-nodejs"
 
-1. In the Azure portal, select the **Overview** tab for your Device Provisioning Service. 
+1. In the Azure portal, select the **Overview** tab for your Device Provisioning Service.
 
 2. Copy the **_ID Scope_** and **Global device endpoint** values.
 
@@ -562,7 +562,7 @@ In this section, we'll update the sample code to send the device's boot sequence
 5. Edit the **register\_x509.js** file with the following changes:
 
     * Replace `provisioning host` with the **_Global Device Endpoint_** noted in **Step 1** above.
-    * Replace `id scope` with the **_ID Scope_** noted in **Step 1** above. 
+    * Replace `id scope` with the **_ID Scope_** noted in **Step 1** above.
     * Replace `registration id` with the **_Registration ID_** noted in the previous section.
     * Replace `cert filename` and `key filename` with the files you copied in **Step 2** above.
 
@@ -572,7 +572,7 @@ In this section, we'll update the sample code to send the device's boot sequence
 
     ```cmd/sh
     node register_x509.js
-    ``` 
+    ```
 
 >[!TIP]
 >The [Azure IoT Hub Node.js Device SDK](https://github.com/Azure/azure-iot-sdk-node) provides an easy way to simulate a device. For more information, see [Device concepts](./concepts-service.md).
@@ -585,12 +585,12 @@ The Python provisioning sample, [provision_x509.py](https://github.com/Azure/azu
 
 | Variable name              | Description                                     |
 | :------------------------- | :---------------------------------------------- |
-| `PROVISIONING_HOST`        |  This value is the global endpoint used for connecting to your DPS resource |    
-| `PROVISIONING_IDSCOPE`     |  This value is the ID Scope for your DPS resource |    
-| `DPS_X509_REGISTRATION_ID` |  This value is the ID for your device. It must also match the subject name on the device certificate |    
-| `X509_CERT_FILE`           |  Your device certificate filename |    
+| `PROVISIONING_HOST`        |  This value is the global endpoint used for connecting to your DPS resource |
+| `PROVISIONING_IDSCOPE`     |  This value is the ID Scope for your DPS resource |
+| `DPS_X509_REGISTRATION_ID` |  This value is the ID for your device. It must also match the subject name on the device certificate |
+| `X509_CERT_FILE`           |  Your device certificate filename |
 | `X509_KEY_FILE`            |  The private key filename for your device certificate |
-| `PASS_PHRASE`              |  The pass phrase you used to encrypt the certificate and private key file (`1234`). |    
+| `PASS_PHRASE`              |  The pass phrase you used to encrypt the certificate and private key file (`1234`). |
 
 1. In the Azure portal, select the **Overview** tab for your Device Provisioning Service.
 
@@ -622,10 +622,10 @@ The Python provisioning sample, [provision_x509.py](https://github.com/Azure/azu
         CN=Python-device-01
       Name Hash(sha1): 1dd88de40e9501fb64892b698afe12d027011000
       Name Hash(md5): a62c784820daa931b9d3977739b30d12
-    
+
      NotBefore: 1/29/2021 7:05 PM
      NotAfter: 1/29/2022 7:05 PM
-    
+
     Subject:
         ===> CN=Python-device-01 <===
       Name Hash(sha1): 1dd88de40e9501fb64892b698afe12d027011000
@@ -712,7 +712,7 @@ The Python provisioning sample, [provision_x509.py](https://github.com/Azure/azu
       ```
 
    * Use the following format when copying/pasting your certificate and private key:
-        
+
       ```java
       private static final String leafPublicPem = "-----BEGIN CERTIFICATE-----\n" +
         "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\n" +