Merge pull request #215427 from timlt/freshness3

Freshness pass

Author: prmerger-automator[bot]

articles/iot-develop/quickstart-devkit-microchip-atsame54-xpro.md

@@ -6,15 +6,15 @@ ms.author: timlt
 ms.service: iot-develop
 ms.devlang: c
 ms.topic: quickstart
-ms.date: 10/18/2021
+ms.date: 10/21/2022
+ms.custom: engagement-fy23
 zone_pivot_groups: iot-develop-toolset
 #- id: iot-develop-toolset
 ## Owner: timlt
 #  title: IoT Devices
 #  prompt: Choose a build environment
 #  - id: iot-toolset-mplab
 #    title: MPLAB
-ms.custom: mode-other, contperf-fy22q3
 #Customer intent: As a device builder, I want to see a working IoT device sample connecting to IoT Hub and sending properties and telemetry, and responding to commands. As a solution builder, I want to use a tool to view the properties, commands, and telemetry an IoT Plug and Play device reports to the IoT hub it connects to.
 ---
 
@@ -310,7 +310,7 @@ Termite is now ready to receive output from the Microchip E54.
 
 1. Expand the sample, then expand the **Sample** folder and open the sample_config.h file.
 
-1. Near the top of the file uncomment the `#define ENABLE_DPS_SAMPLE` directive.
+1. Near the top of the file, uncomment the `#define ENABLE_DPS_SAMPLE` directive.
 
     ```c
     #define ENABLE_DPS_SAMPLE
@@ -437,7 +437,7 @@ Termite is now ready to receive output from the Microchip E54.
 
 1. Expand the **sample_azure_iot_embedded_sdk_pnp** project, then expand the **Header Files** folder and open the sample_config.h file.
 
-1. Near the top of the file uncomment the `#define ENABLE_DPS_SAMPLE` directive.
+1. Near the top of the file, uncomment the `#define ENABLE_DPS_SAMPLE` directive.
 
     ```c
     #define ENABLE_DPS_SAMPLE

articles/iot-develop/quickstart-devkit-mxchip-az3166-iot-hub.md

@@ -6,8 +6,8 @@ ms.author: timlt
 ms.service: iot-develop
 ms.devlang: c
 ms.topic: quickstart
-ms.date: 06/09/2021
-ms.custom: mode-other, devx-track-azurecli, contperf-fy22q3
+ms.date: 10/21/2022
+ms.custom: mode-other, engagement-fy23, devx-track-azurecli
 ---
 
 # Connect an MXCHIP AZ3166 devkit to IoT Hub

articles/iot-develop/quickstart-devkit-mxchip-az3166.md

@@ -6,8 +6,8 @@ ms.author: timlt
 ms.service: iot-develop
 ms.devlang: c
 ms.topic: quickstart
-ms.date: 06/02/2021
-ms.custom: mode-other
+ms.date: 10/21/2022
+ms.custom: mode-other, engagement-fy23
 ---
 
 # Quickstart: Connect an MXCHIP AZ3166 devkit to IoT Central

articles/iot-develop/quickstart-devkit-nxp-mimxrt1050-evkb.md

@@ -6,8 +6,8 @@ ms.author: timlt
 ms.service: iot-develop
 ms.devlang: c
 ms.topic: quickstart
-ms.date: 06/04/2021
-ms.custom: mode-other
+ms.date: 10/21/2022
+ms.custom: mode-other, engagement-fy23
 ---
 
 # Quickstart: Connect an NXP MIMXRT1050-EVKB Evaluation kit to IoT Central

articles/iot-develop/quickstart-devkit-nxp-mimxrt1060-evk.md

@@ -6,8 +6,8 @@ ms.author: timlt
 ms.service: iot-develop
 ms.devlang: c
 ms.topic: quickstart
-ms.date: 11/16/2021
-ms.custom: mode-other, contperf-fy22q3
+ms.date: 10/21/2022
+ms.custom: mode-other, engagement-fy23
 zone_pivot_groups: iot-develop-nxp-toolset
 
 # Owner: timlt
@@ -237,7 +237,7 @@ In this section, you use IAR EW IDE to modify a configuration file for Azure IoT
 
 1. Expand the project, then expand the **Sample** subfolder and open the *sample_config.h* file.
 
-1. Near the top of the file uncomment the `#define ENABLE_DPS_SAMPLE` directive.
+1. Near the top of the file, uncomment the `#define ENABLE_DPS_SAMPLE` directive.
 
     ```c
     #define ENABLE_DPS_SAMPLE
@@ -309,7 +309,7 @@ Keep the terminal open to monitor device output in the following steps.
 
 * MCUXpresso IDE (MCUXpresso), version 11.3.1 or later. Download and install a [free copy of MCUXPresso](https://www.nxp.com/design/software/development-software/mcuxpresso-software-and-tools-/mcuxpresso-integrated-development-environment-ide:MCUXpresso-IDE).
 
-* Download the [MIMXRT1060-EVK SDK 2.9.0 or later](https://mcuxpresso.nxp.com/en/builder). After you sign in, the website lets you build a custom SDK archive to download. After you select the EVK MIMXRT1060 board and click the option to build the SDK, you can download the zip archive.  The only SDK component to include is the preselected **SDMMC Stack**.
+* Download the [MIMXRT1060-EVK SDK 2.9.0 or later](https://mcuxpresso.nxp.com/en/builder). After you sign in, the website lets you build a custom SDK archive to download. After you select the EVK MIMXRT1060 board and select the option to build the SDK, you can download the zip archive.  The only SDK component to include is the preselected **SDMMC Stack**.
 
 * Download the NXP MIMXRT1060-EVK MCUXpresso sample from [Azure RTOS samples](https://github.com/azure-rtos/samples/), and unzip it to a working directory. Choose a directory with a short path to avoid compiler errors when you build.
 
@@ -343,7 +343,7 @@ In this section, you prepare your environment, and use MCUXpresso to build and r
 
     :::image type="content" source="media/quickstart-devkit-nxp-mimxrt1060-evk/mcu-load-project.png" alt-text="Screenshot showing a loaded project in MCUXpresso.":::
 
-1. Near the top of the file uncomment the `#define ENABLE_DPS_SAMPLE` directive.
+1. Near the top of the file, uncomment the `#define ENABLE_DPS_SAMPLE` directive.
 
     ```c
     #define ENABLE_DPS_SAMPLE
@@ -384,7 +384,7 @@ In this section, you prepare your environment, and use MCUXpresso to build and r
     > [!NOTE]
     > The terminal window appears in the lower half of the IDE and might initially display garbage characters until you download and run the sample.
 
-1. Select the **Start Debugging project [project name]** toolbar button.  This downloads the project to the device, and runs it.
+1. Select the **Start Debugging project [project name]** toolbar button.  This action downloads the project to the device, and runs it.
 
 1. After the code hits a break in the IDE, select the **Resume (F8)** toolbar button.
 
@@ -509,10 +509,10 @@ If you experience issues building the device code, flashing the device, or conne
 For debugging the application, see [Debugging with Visual Studio Code](https://github.com/azure-rtos/getting-started/blob/master/docs/debugging.md).
 :::zone-end
 :::zone pivot="iot-toolset-iar-ewarm"
-If you need help debugging the application, see the selections under **Help** in **IAR EW for ARM**.  
+If you need help with debugging the application, see the selections under **Help** in **IAR EW for ARM**.  
 :::zone-end
 :::zone pivot="iot-toolset-iar-ewarm"
-If you need help debugging the application, in MCUXpresso open the **Help > MCUXPresso IDE User Guide** and see the content on Azure RTOS debugging. 
+If you need help with debugging the application, in MCUXpresso open the **Help > MCUXPresso IDE User Guide** and see the content on Azure RTOS debugging. 
 :::zone-end
 
 ## Clean up resources

articles/iot-develop/quickstart-devkit-renesas-rx65n-2mb.md

@@ -6,8 +6,8 @@ ms.author: timlt
 ms.service: iot-develop
 ms.devlang: c
 ms.topic: quickstart
-ms.date: 06/04/2021
-ms.custom: mode-other
+ms.date: 10/21/2022
+ms.custom: mode-other, engagement-fy23
 ---
 
 # Quickstart: Connect a Renesas Starter Kit+ for RX65N-2MB to IoT Central

articles/iot-develop/quickstart-devkit-stm-b-l475e.md

@@ -6,8 +6,8 @@ ms.author: timlt
 ms.service: iot-develop
 ms.devlang: c
 ms.topic: quickstart
-ms.date: 06/02/2021
-ms.custom: mode-other
+ms.date: 10/21/2022
+ms.custom: mode-other, engagement-fy23
 ---
 
 # Quickstart: Connect an STMicroelectronics B-L475E-IOT01A Discovery kit to IoT Central
@@ -19,7 +19,7 @@ ms.custom: mode-other
 
 In this quickstart, you use Azure RTOS to connect the STMicroelectronics [B-L475E-IOT01A](https://www.st.com/en/evaluation-tools/b-l475e-iot01a.html) Discovery kit (from now on, the STM DevKit) to Azure IoT.
 
-You will complete the following tasks:
+You'll complete the following tasks:
 
 * Install a set of embedded development tools for programming the STM DevKit in C
 * Build an image and flash it onto the STM DevKit
@@ -114,7 +114,7 @@ To connect the STM DevKit to Azure, you'll modify a configuration file for Wi-Fi
 
 ### Flash the image
 
-1. On the STM DevKit MCU, locate the **Reset** button (1), the Micro USB port (2), which is labeled **USB STLink**, and the board part number (3). You will refer to these items in the next steps. All of them are highlighted in the following picture:
+1. On the STM DevKit MCU, locate the **Reset** button (1), the Micro USB port (2), which is labeled **USB STLink**, and the board part number (3). You'll refer to these items in the next steps. All of them are highlighted in the following picture:
 
     :::image type="content" source="media/quickstart-devkit-stm-b-l475e/stm-devkit-board-475.png" alt-text="Locate key components on the STM DevKit board":::
 
@@ -222,7 +222,7 @@ To view telemetry in IoT Central portal:
 
 ## Call a direct method on the device
 
-You can also use IoT Central to call a direct method that you have implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that enables you to turn an LED on or off.
+You can also use IoT Central to call a direct method that you've implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that enables you to turn an LED on or off.
 
 To call a method in IoT Central portal:
 

articles/iot-develop/quickstart-devkit-stm-b-l4s5i.md

@@ -6,8 +6,8 @@ ms.author: timlt
 ms.service: iot-develop
 ms.devlang: c
 ms.topic: quickstart
-ms.date: 06/02/2021
-ms.custom: mode-other
+ms.date: 10/21/2022
+ms.custom: mode-other, engagement-fy23
 zone_pivot_groups: iot-develop-stm32-toolset
 
 # Owner: timlt
@@ -371,7 +371,7 @@ To view telemetry in IoT Central portal:
 
 ## Call a direct method on the device
 
-You can also use IoT Central to call a direct method that you have implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout.
+You can also use IoT Central to call a direct method that you've implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout.
 
 To call a method in IoT Central portal:
 
@@ -403,10 +403,10 @@ Select the **About** tab from the device page.
 
 ## Download the STM32Cube IDE
 
-You can download a free version of STM32Cube IDE, but you will need to create an account. Follow the instructions on the ST website. THe STM32Cube IDE can be downloaded from this website: 
+You can download a free version of STM32Cube IDE, but you'll need to create an account. Follow the instructions on the ST website. The STM32Cube IDE can be downloaded from this website: 
 https://www.st.com/en/development-tools/stm32cubeide.html
 
-The sample distribution zip file contains the following sub-folders that you will use later:
+The sample distribution zip file contains the following subfolders that you'll use later:
 
 |Folder|Contents|
 |-------------|-----|
@@ -451,11 +451,11 @@ To connect the device to Azure, you'll modify a configuration file for Azure IoT
 
 ### Build the project
 
-In STM32CubeIDE, select ***Project > Build All*** to build sample projects and its dependent libraries. You will observe compilation and linking of the sample project.
+In STM32CubeIDE, select ***Project > Build All*** to build sample projects and its dependent libraries. You'll observe compilation and linking of the sample project.
 
 Download and run the project
 
-1. On the STM DevKit MCU, locate the **Reset** button (1), the Micro USB port (2), which is labeled **USB STLink**, and the board part number (3). You will refer to these items in the next steps. All of them are highlighted in the following picture:
+1. On the STM DevKit MCU, locate the **Reset** button (1), the Micro USB port (2), which is labeled **USB STLink**, and the board part number (3). You'll refer to these items in the next steps. All of them are highlighted in the following picture:
 
     :::image type="content" source="media/quickstart-devkit-stm-b-l4s5i/stm-b-l4s5i.png" alt-text="Locate key components on the STM DevKit board":::
 
@@ -550,7 +550,7 @@ To view telemetry in IoT Central portal:
 
 ## Call a direct method on the device
 
-You can also use IoT Central to call a direct method that you have implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout.
+You can also use IoT Central to call a direct method that you've implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout.
 
 To call a method in IoT Central portal:
 
@@ -602,7 +602,7 @@ To view telemetry in IoT Central portal:
 
 ## Call a direct method on the device
 
-You can also use IoT Central to call a direct method that you have implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that enables you to turn an LED on or off.
+You can also use IoT Central to call a direct method that you've implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that enables you to turn an LED on or off.
 
 To call a method in IoT Central portal:
 
@@ -645,7 +645,7 @@ To remove the entire Azure IoT Central sample application and all its devices an
 
 ## Next steps
 
-In this quickstart, you built a custom image that contains Azure RTOS sample code, and then flashed the image to the STM DevKit device. You also used the IoT Central portal to create Azure resources, connect the STM DevKit securely to Azure, view customer content, and send messages.
+In this quickstart, you built a custom image that contains Azure RTOS sample code, and then flashed the image to the STM DevKit device. You also used the IoT Central portal to create Azure resources, connect the STM DevKit securely to Azure, view device data, and send messages.
 
 As a next step, explore the following articles to learn more about using the IoT device SDKs to connect devices to Azure IoT.