Minor freshness updates

Author: dominicbetts

articles/iot-central/core/howto-configure-file-uploads.md

@@ -4,7 +4,7 @@ description: How to configure, implement, and manage file uploads from your devi
 services: iot-central
 author: dominicbetts
 ms.author: dobett
-ms.date: 08/25/2022
+ms.date: 11/27/2023
 ms.topic: how-to
 ms.service: iot-central
 

articles/iot-central/core/howto-connect-eflow.md

@@ -3,7 +3,7 @@ title: Connect Azure IoT Edge for Linux on Windows (EFLOW)
 description: Learn how to connect an Azure IoT Edge for Linux on Windows (EFLOW) device to an IoT Central application
 author: dominicbetts
 ms.author: dobett
-ms.date: 10/11/2022
+ms.date: 11/27/2023
 ms.topic: how-to
 ms.service: iot-central
 ---
@@ -161,7 +161,7 @@ You've now finished configuring your IoT Central application to enable an IoT Ed
 
 To install and provision your EFLOW device:
 
-1. In an elevated PowerShell session, run each of the following commands to download IoT Edge for Linux on Windows.
+1. In an elevated PowerShell session, run the following commands to download IoT Edge for Linux on Windows.
 
     ```powershell
     $msiPath = $([io.Path]::Combine($env:TEMP, 'AzureIoTEdge.msi'))

articles/iot-central/core/howto-connect-rigado-cascade-500.md

@@ -3,7 +3,7 @@ title: Connect a Rigado Cascade 500 in Azure IoT Central
 description: Learn how to configure and connect a Rigado Cascade 500 gateway device to your IoT Central application. 
 author: dominicbetts
 ms.author: dobett
-ms.date: 11/01/2022
+ms.date: 11/27/2023
 services: iot-central
 ms.service: iot-central
 ms.topic: how-to
@@ -58,7 +58,7 @@ To connect the Cascade 500 device to your IoT Central application, you need to r
 
 1. Now select **SAS-IoT-Edge-Devices** and make a note of the **Primary key**:
 
-    :::image type="content" source="media/howto-connect-rigado-cascade-500/primary-key-sas.png" alt-text="Screenshot that shows the primary SAS key for you device connection group." lightbox="media/howto-connect-rigado-cascade-500/primary-key-sas.png":::
+    :::image type="content" source="media/howto-connect-rigado-cascade-500/primary-key-sas.png" alt-text="Screenshot that shows the primary SAS key for your device connection group." lightbox="media/howto-connect-rigado-cascade-500/primary-key-sas.png":::
 
 ## Contact Rigado to connect the gateway
 

articles/iot-central/core/howto-create-custom-rules.md

@@ -3,7 +3,7 @@ title: Extend Azure IoT Central by using custom rules
 description: Configure an IoT Central application to send notifications when a device stops sending telemetry by using Azure Stream Analytics, Azure Functions, and SendGrid.
 author: dominicbetts 
 ms.author: dobett 
-ms.date: 11/28/2022
+ms.date: 11/27/2023
 ms.topic: how-to
 ms.service: iot-central
 services: iot-central
@@ -13,14 +13,14 @@ ms.custom: mvc, devx-track-csharp, devx-track-azurecli
 
 # Extend Azure IoT Central with custom rules using Stream Analytics, Azure Functions, and SendGrid
 
-This how-to guide shows you how to extend your IoT Central application with custom rules and notifications. The example shows sending a notification to an operator when a device stops sending telemetry. The solution uses an [Azure Stream Analytics](../../stream-analytics/index.yml) query to detect when a device has stopped sending telemetry. The Stream Analytics job uses [Azure Functions](../../azure-functions/index.yml) to send notification emails using [SendGrid](https://sendgrid.com/docs/for-developers/partners/microsoft-azure/).
+This how-to guide shows you how to extend your IoT Central application with custom rules and notifications. The example shows sending a notification to an operator when a device stops sending telemetry. The solution uses an [Azure Stream Analytics](../../stream-analytics/index.yml) query to detect when a device stops sending telemetry. The Stream Analytics job uses [Azure Functions](../../azure-functions/index.yml) to send notification emails using [SendGrid](https://sendgrid.com/docs/for-developers/partners/microsoft-azure/).
 
 This how-to guide shows you how to extend IoT Central beyond what it can already do with the built-in rules and actions.
 
 In this how-to guide, you learn how to:
 
 * Stream telemetry from an IoT Central application using *continuous data export*.
-* Create a Stream Analytics query that detects when a device has stopped sending data.
+* Create a Stream Analytics query that detects when a device stops sending data.
 * Send an email notification using the Azure Functions and SendGrid services.
 
 ## Prerequisites
@@ -346,7 +346,7 @@ To tidy up after this how-to and avoid unnecessary costs, delete the **DetectSto
 In this how-to guide, you learned how to:
 
 * Stream telemetry from an IoT Central application using the data export feature.
-* Create a Stream Analytics query that detects when a device has stopped sending data.
+* Create a Stream Analytics query that detects when a device stops sending data.
 * Send an email notification using the Azure Functions and SendGrid services.
 
 Now that you know how to create custom rules and notifications, the suggested next step is to learn how to [Extend Azure IoT Central with custom analytics](howto-create-custom-analytics.md).

articles/iot-central/core/howto-transform-data.md

@@ -3,7 +3,7 @@ title: Transform data for an IoT Central application
 description: IoT devices send data in various formats that you may need to transform. This article describes how to transform data both on the way in and out of IoT Central.
 author: dominicbetts
 ms.author: dobett
-ms.date: 01/10/2023
+ms.date: 11/27/2023
 ms.topic: how-to
 ms.service: iot-central
 services: iot-central
@@ -148,7 +148,7 @@ To build the custom module in the [Azure Cloud Shell](https://shell.azure.com/):
 
 This scenario uses an IoT Edge gateway device to transform the data from any downstream devices. This section describes how to create IoT Central device template for the gateway device in your IoT Central application. IoT Edge devices use a deployment manifest to configure their modules.
 
-In this example, the downstream device doesn't need a device template. The downstream device is registered in IoT Central so you can generate the credentials it needs to connect the IoT Edge device. Because the IoT Edge module transforms the data, all the downstream device telemetry arrives in IoT Central as if the IoT Edge device had sent it.
+In this example, the downstream device doesn't need a device template. The downstream device is registered in IoT Central so you can generate the credentials it needs to connect the IoT Edge device. Because the IoT Edge module transforms the data, all the downstream device telemetry arrives in IoT Central as if the IoT Edge device has sent it.
 
 To create a device template for the IoT Edge gateway device:
 
@@ -276,7 +276,7 @@ To check that the IoT Edge gateway device is running correctly:
 
 1. Open your IoT Central application. Then navigate to the **IoT Edge Gateway device** on the list of devices on the **Devices** page.
 
-1. Select the **Modules** tab and check the status of the three modules. It takes a few minutes for the IoT Edge runtime to start up in the virtual machine. When it's started, the status of the three modules is **Running**. If the IoT Edge runtime doesn't start, see [Troubleshoot your IoT Edge device](../../iot-edge/troubleshoot.md).
+1. Select the **Modules** tab and check the status of the three modules. It takes a few minutes for the IoT Edge runtime to start up in the virtual machine. When the virtual machine is running, the status of the three modules is **Running**. If the IoT Edge runtime doesn't start, see [Troubleshoot your IoT Edge device](../../iot-edge/troubleshoot.md).
 
 For your IoT Edge device to function as a gateway, it needs some certificates to prove its identity to any downstream devices. This article uses demo certificates. In a production environment, use certificates from your certificate authority.
 
@@ -600,7 +600,7 @@ Set up the data export to send data to your Device bridge:
 
 ### Verify
 
-The sample device you use to test the scenario is written in Node.js. Make sure you have Node.js and npm installed on your local machine. If you don't want to install these prerequisites, use the [Azure Cloud Shell](https://shell.azure.com/) that has them preinstalled.
+The sample device you use to test the scenario is written in Node.js. Make sure you have Node.js and npm installed on your local machine. If you don't want to install these prerequisites, use the [Azure Cloud Shell](https://shell.azure.com/) where they are preinstalled.
 
 To run a sample device that tests the scenario: