Use full ADT name

Author: baanders

articles/iot/iot-glossary.md

@@ -124,17 +124,17 @@ First and subsequent mentions: When you're referring to the service, always spel
 
 Example usage: The data in your *Azure Digital Twins* model can be routed to downstream Azure services for more analytics or storage.
 
-Applies to: Digital Twins
+Applies to: Azure Digital Twins
 
 ### Azure Digital Twins instance
 
-A single instance of the [Azure Digital Twins](#azure-digital-twins) service in a customer's subscription. While Azure [Digital Twins](#digital-twin) refers to the Azure service as a whole, your Azure Digital Twins *instance* is your individual Azure Digital Twins resource.
+A single instance of the [Azure Digital Twins](#azure-digital-twins) service in a customer's subscription. While [Azure Digital Twins](#digital-twin) refers to the Azure service as a whole, your Azure Digital Twins *instance* is your individual Azure Digital Twins resource.
 
 Casing rules: Always capitalize the service name.
 
 First and subsequent mentions: Always spell out in full as *Azure Digital Twins instance*.
 
-Applies to: Digital Twins
+Applies to: Azure Digital Twins
 
 ### Azure IoT
 
@@ -276,7 +276,7 @@ In IoT Plug and Play and [Azure Digital Twins](#azure-digital-twins), components
 
 Casing rules: Always lowercase.
 
-Applies to: IoT Hub, Digital Twins, Device developer
+Applies to: IoT Hub, Azure Digital Twins, Device developer
 
 ### Configuration
 
@@ -445,7 +445,7 @@ A description, that uses the [Digital Twins Definition Language](#digital-twins-
 
 Casing rules: Always lowercase.
 
-Applies to: IoT Hub, IoT Central, Device developer, Digital Twins
+Applies to: IoT Hub, IoT Central, Device developer, Azure Digital Twins
 
 ### Device provisioning
 
@@ -497,7 +497,7 @@ First and subsequent mentions: Spell out in full as *Digital Twins Definition La
 
 Abbreviation: DTDL
 
-Applies to: IoT Hub, IoT Central, Digital Twins
+Applies to: IoT Hub, IoT Central, Azure Digital Twins
 
 ### Digital twin
 
@@ -507,7 +507,7 @@ See also [Device twin](#device-twin)
 
 Casing rules: Always lowercase.
 
-Applies to: IoT Hub, IoT Central, Digital Twins, Device developer
+Applies to: IoT Hub, IoT Central, Azure Digital Twins, Device developer
 
 ### Digital twin change events
 
@@ -539,11 +539,11 @@ Applies to: IoT Hub
 
 ### Downstream service
 
-A relative term describing services that receive data from the current context. For example, in the context of [Azure Digital Twins](#azure-digital-twins), Time Series Insights is a downstream service if you set up your data to flow from Azure [Digital Twins](#digital-twin) into Time Series Insights.
+A relative term describing services that receive data from the current context. For example, in the context of [Azure Digital Twins](#azure-digital-twins), Time Series Insights is a downstream service if you set up your data to flow from [Azure Digital Twins](#azure-digital-twins) into Time Series Insights.
 
 Casing rules: Always lowercase.
 
-Applies to: IoT Hub, IoT Central, Digital Twins
+Applies to: IoT Hub, IoT Central, Azure Digital Twins
 
 ## E
 
@@ -603,11 +603,11 @@ Applies to: IoT Hub
 
 The process of sending events and their data from one [device](#device) or service to the [endpoint](#endpoint) of another.
 
-In [IoT Hub](#iot-hub), you can define [routing rules](#routing-rule) to describe how messages should be sent. In [Azure Digital Twins](#azure-digital-twins), event routes are entities that are created for this purpose. Azure [Digital Twins](#digital-twin) event routes can contain filters to limit what types of events are sent to each endpoint.
+In [IoT Hub](#iot-hub), you can define [routing rules](#routing-rule) to describe how messages should be sent. In [Azure Digital Twins](#azure-digital-twins), event routes are entities that are created for this purpose. [Azure Digital Twins](#azure-digital-twins) event routes can contain filters to limit what types of events are sent to each endpoint.
 
 Casing rules: Always lowercase.
 
-Applies to: IoT Hub, Digital Twins
+Applies to: IoT Hub, Azure Digital Twins
 
 ## F
 
@@ -689,7 +689,7 @@ In [Azure Digital Twins](#azure-digital-twins), *interface* may be used to refer
 
 Casing rules: Always lowercase.
 
-Applies to: Device developer, Digital Twins
+Applies to: Device developer, Azure Digital Twins
 
 ### IoT Edge
 
@@ -839,7 +839,7 @@ In [Azure Digital Twins](#azure-digital-twins), this type of event is fired when
 
 Casing rules: Always lowercase.
 
-Applies to: Digital Twins, IoT Hub, IoT Central
+Applies to: Azure Digital Twins, IoT Hub, IoT Central
 
 ### Linked IoT hub
 
@@ -879,31 +879,31 @@ In the [Azure Digital Twins](#azure-digital-twins) service, models define [devic
 
 Casing rules: Always lowercase.
 
-Applies to: IoT Hub, IoT Central, Digital Twins, Device developer
+Applies to: IoT Hub, IoT Central, Azure Digital Twins, Device developer
 
 ### Model ID
 
 When an [IoT Plug and Play device](#iot-plug-and-play-device) connects to an [IoT Hub](#iot-hub) or IoT Central application, it sends the [model](#model) ID of the [Digital Twins Definition Language](#digital-twins-definition-language) model it implements. Every model as a unique model ID. This model ID enables the [solution](#solution) to find the [device model](#device-model).
 
 Casing rules: Always capitalize as *model ID*.
 
-Applies to: IoT Hub, IoT Central, Device developer, Digital Twins
+Applies to: IoT Hub, IoT Central, Device developer, Azure Digital Twins
 
 ### Model repository
 
 Stores [Digital Twins Definition Language](#digital-twins-definition-language) [models](#model) and [interfaces](#interface). A [solution](#solution) uses a [model ID](#model-id) to retrieve a model from a repository.
 
 Casing rules: Always lowercase.
 
-Applies to: IoT Hub, IoT Central, Digital Twins
+Applies to: IoT Hub, IoT Central, Azure Digital Twins
 
 ### Model repository REST API
 
 An API for managing and interacting with a [model repository](#model-repository). For example, you can use the API to search for and retrieve [device models](#device-model).
 
 Casing rules: Always capitalize as *model repository REST API*.
 
-Applies to: IoT Hub, IoT Central, Digital Twins
+Applies to: IoT Hub, IoT Central, Azure Digital Twins
 
 ### Module
 
@@ -947,11 +947,11 @@ Applies to: IoT Hub
 
 ### Ontology
 
-In the context of [Digital Twins](#digital-twin), a set of [models](#model) for a particular domain, such as real estate, smart cities, IoT systems, energy grids, and more. Ontologies are often used as schemas for knowledge graphs like the ones in [Azure Digital Twins](#azure-digital-twins), because they provide a starting point based on industry standards and best practices.
+In the context of [digital twins](#digital-twin), a set of [models](#model) for a particular domain, such as real estate, smart cities, IoT systems, energy grids, and more. Ontologies are often used as schemas for knowledge graphs like the ones in [Azure Digital Twins](#azure-digital-twins), because they provide a starting point based on industry standards and best practices.
 
 [Learn more](../digital-twins/concepts-ontologies.md)
 
-Applies to: Digital Twins
+Applies to: Azure Digital Twins
 
 ### Operations experience
 
@@ -1003,15 +1003,15 @@ In the context of a [digital twin](#digital-twin), data fields defined in an [in
 
 Casing rules: Always lowercase.
 
-Applies to: IoT Hub, IoT Central, Digital Twins, Device developer
+Applies to: IoT Hub, IoT Central, Azure Digital Twins, Device developer
 
 ### Property change event
 
 An event that results from a property change in a [digital twin](#digital-twin).
 
 Casing rules: Always lowercase.
 
-Applies to: IoT Hub, IoT Central, Digital Twins
+Applies to: IoT Hub, IoT Central, Azure Digital Twins
 
 ### Protocol gateway
 
@@ -1045,7 +1045,7 @@ Used in the [Azure Digital Twins](#azure-digital-twins) service to connect [digi
 
 Casing rules: Always lowercase.
 
-Applies to: Digital Twins
+Applies to: Azure Digital Twins
 
 ### Reported configuration
 
@@ -1105,7 +1105,7 @@ An [endpoint](#endpoint) that an administrator uses to manage service settings.
 
 Casing rules: Always lowercase.
 
-Applies to: IoT Hub, Device Provisioning Service, IoT Edge, Digital Twins
+Applies to: IoT Hub, Device Provisioning Service, IoT Edge, Azure Digital Twins
 
 ### Shared access policy
 
@@ -1123,31 +1123,31 @@ Casing rules: Always lowercase.
 
 Abbreviation: SAS
 
-Applies to: IoT Hub, Digital Twins, IoT Central, IoT Edge
+Applies to: IoT Hub, Azure Digital Twins, IoT Central, IoT Edge
 
 ### Simulated device
 
 For convenience, many of the tutorials and quickstarts run [device](#device) code with simulated sensors on your local development machine. In contrast, a [physical device](#physical-device) such as an MXCHIP has real sensors and connects to an [IoT hub](#iot-hub).
 
 Casing rules: Always lowercase.
 
-Applies to: IoT Hub, IoT Central, Device developer, IoT Edge, Digital Twins, Device Provisioning Service
+Applies to: IoT Hub, IoT Central, Device developer, IoT Edge, Azure Digital Twins, Device Provisioning Service
 
 ### Solution
 
 In the context of IoT, *solution* typically refers to an end-to-end IoT solution that encompasses IoT devices or assets as well as the cloud services they connect to. A solution includes elements such as [devices](#device), [assets](#asset), [device apps](#device-app), an [IoT hub](#iot-hub), other Azure services, and [back-end apps](#back-end-app).
 
 Casing rules: Always lowercase.
 
-Applies to: IoT Hub, IoT Central, Device Provisioning Service, IoT Edge, Digital Twins
+Applies to: IoT Hub, IoT Central, Device Provisioning Service, IoT Edge, Azure Digital Twins
 
 ### Solution back end
 
 The subset of an IoT [solution](#solution) that tends to handle cloud-side tasks like device management or data processing and analytics, including an [IoT hub](#iot-hub), other Azure services, and [back-end apps](#back-end-app).
 
 Casing rules: Always lowercase.
 
-Applies to: IoT Hub, IoT Central, Device Provisioning Service, IoT Edge, Digital Twins
+Applies to: IoT Hub, IoT Central, Device Provisioning Service, IoT Edge, Azure Digital Twins
 
 ### System properties
 
@@ -1188,7 +1188,7 @@ Casing rules: Always lowercase.
 Example usage: Don't use the word *telemetries*, telemetry refers to the collection of data a device sends. For example: When the device connects to your IoT hub, it starts sending telemetry. One of the telemetry values the device sends is the environmental temperature.
 
 
-Applies to: IoT Hub, IoT Central, Digital Twins, IoT Edge, Device developer
+Applies to: IoT Hub, IoT Central, Azure Digital Twins, IoT Edge, Device developer
 
 ### Telemetry event
 
@@ -1218,8 +1218,8 @@ Applies to: IoT Hub
 
 ### Upstream service
 
-A relative term describing services that feed data into the current context. For instance, in the context of [Azure Digital Twins](#azure-digital-twins), [IoT Hub](#iot-hub) is considered an upstream service because data flows from IoT Hub into Azure [Digital Twins](#digital-twin).
+A relative term describing services that feed data into the current context. For instance, in the context of [Azure Digital Twins](#azure-digital-twins), [IoT Hub](#iot-hub) is considered an upstream service because data flows from IoT Hub into [Azure Digital Twins](#azure-digital-twins).
 
 Casing rules: Always lowercase.
 
-Applies to: IoT Hub, IoT Central, Digital Twins
+Applies to: IoT Hub, IoT Central, Azure Digital Twins