Merge pull request #227142 from dominicbetts/central-freshness

IoT Central: freshness

Author: v-dirichards

articles/iot-central/.openpublishing.redirection.iot-central.json

@@ -1122,7 +1122,12 @@
     },
     {
       "source_path_from_root": "/articles/iot-central/healthcare/howto-health-data-triage.md",
-      "redirect_url": "/azure/iot-central/healthcare/tutorial-health-data-triage/",
+      "redirect_url": "/azure/iot-central/healthcare/tutorial-continuous-patient-monitoring/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/iot-central/healthcare/tutorial-health-data-triage.md",
+      "redirect_url": "/azure/iot-central/healthcare/tutorial-continuous-patient-monitoring/",
       "redirect_document_id": false
     },
     {

articles/iot-central/TOC.yml

@@ -75,8 +75,6 @@
         items:
         - name: Create a continuous patient monitoring app
           href: healthcare/tutorial-continuous-patient-monitoring.md 
-        - name: Create a health data triage dashboard
-          href: ./healthcare/tutorial-health-data-triage.md
 
 - name: Concepts
   items:

articles/iot-central/core/concepts-device-implementation.md

@@ -1,9 +1,10 @@
 ---
-title: Device implementation in Azure IoT Central | Microsoft Docs
+title: Device implementation
+titleSuffix: Azure IoT Central
 description: This article introduces the key concepts and best practices for implementing a device that connects to your IoT Central application.
 author: dominicbetts
 ms.author: dobett
-ms.date: 03/04/2022
+ms.date: 02/13/2023
 ms.topic: conceptual
 ms.service: iot-central
 services: iot-central
@@ -131,7 +132,7 @@ az iot central device manual-failover \
 > [!TIP]
 > To find the **Application ID**, navigate to **Application > Management** in your IoT Central application.
 
-If the command succeeds, you see output that looks like the following:
+If the command succeeds, you see output that looks like the following example:
 
 ```output
 Command group 'iot central device' is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus

articles/iot-central/core/concepts-faq-scalability-availability.md

@@ -1,9 +1,10 @@
 ---
-title: Azure IoT Central scalability and high availability | Microsoft Docs
+title: Scalability and high availability
+titleSuffix: Azure IoT Central
 description: This article describes how IoT Central automatically scales to handle more devices, its high availability disaster recovery capabilities.
 author: dominicbetts
 ms.author: dobett
-ms.date: 03/01/2022
+ms.date: 02/13/2023
 ms.topic: conceptual
 ms.service: iot-central
 services: iot-central
@@ -24,7 +25,7 @@ IoT Central automatically scales its IoT hubs based on the load profiles in your
 
 ## High availability and disaster recovery
 
-For highly available device connectivity, an IoT Central application always have at least two IoT hubs. For exceptions to to this rule, see [Limitations](#limitations). The number of hubs can grow or shrink as IoT Central scales the application in response to changes in the load profile.
+For highly available device connectivity, an IoT Central application always has at least two IoT hubs. For exceptions to this rule, see [Limitations](#limitations). The number of hubs can grow or shrink as IoT Central scales the application in response to changes in the load profile.
 
 IoT Central also uses [availability zones](../../availability-zones/az-overview.md#availability-zones) to make various services it uses highly available.
 

articles/iot-central/core/howto-manage-devices-individually.md

@@ -1,9 +1,10 @@
 ---
-title: Manage devices individually in your Azure IoT Central application | Microsoft Docs
+title: Manage devices individually in your application
+titleSuffix: Azure IoT Central
 description: Learn how to manage devices individually in your Azure IoT Central application. Monitor, manage, create, delete, and update devices.
 author: dominicbetts
 ms.author: dobett
-ms.date: 03/02/2022
+ms.date: 02/13/2023
 ms.topic: how-to
 ms.service: iot-central
 services: iot-central
@@ -34,7 +35,7 @@ To view an individual device:
 
 1. In the right-hand pane of the **Devices** page, you see a list of devices accessible to your organization created from that device template:
 
-    :::image type="content" source="media/howto-manage-devices-individually/device-list.png" alt-text="Screenshot showing the device list." lightbox="media/howto-manage-devices-individually/device-list.png":::
+    :::image type="content" source="media/howto-manage-devices-individually/device-list.png" alt-text="Screenshot that shows the list of Thermostat devices." lightbox="media/howto-manage-devices-individually/device-list.png":::
 
     Choose an individual device to see the device details page for that device.
 
@@ -61,7 +62,7 @@ When a device connects to your IoT Central application, its device status change
 
 1. An operator can block a device. When a device is blocked, it can't send data to your IoT Central application. Blocked devices have a status of **Blocked**. An operator must reset the device before it can resume sending data. When an operator unblocks a device the status returns to its previous value, **Registered** or **Provisioned**.
 
-1. If the device status is **Waiting for Approval**, it means the **Auto approve** option is disabled. An operator must explicitly approve a device before it starts sending data. Devices not registered manually on the **Devices** page, but connected with valid credentials will have the device status **Waiting for Approval**. Operators can approve these devices from the **Devices** page using the **Approve** button.
+1. If the device status is **Waiting for Approval**, it means the **Auto approve** option is disabled. An operator must explicitly approve a device before it starts sending data. Devices not registered manually on the **Devices** page, but connected with valid credentials have the device status **Waiting for Approval**. Operators can approve these devices from the **Devices** page using the **Approve** button.
 
 1. If the device status is **Unassigned**, it means the device connecting to IoT Central isn't assigned to a device template. This situation typically happens in the following scenarios:
 

articles/iot-central/core/overview-iot-central-developer.md

@@ -1,15 +1,15 @@
 ---
-title: Azure IoT Central device connectivity guide | Microsoft Docs
-description: Azure IoT Central is an IoT application platform that simplifies the creation of IoT solutions. This guide describes how IoT devices connect to your IoT Central application. After a device connects, it uses telemetry to send streaming data and properties to report device state. Iot Central can set device state using writable properties and call commands on a device.
+title: Device connectivity guide
+titleSuffix: Azure IoT Central
+description: This guide describes how IoT devices connect to and communicate with your IoT Central application. The article describes telemetry, properties, and commands.
 author: dominicbetts
 ms.author: dobett
-ms.date: 03/02/2022
+ms.date: 02/13/2023
 ms.topic: conceptual
 ms.service: iot-central
 services: iot-central
 ms.custom: [mvc, device-developer, iot-central-frontdoor]
 
-
 # This article applies to device developers.
 ---