Move includes

Author: baanders

articles/digital-twins/concepts-3d-scenes-studio.md

@@ -112,7 +112,7 @@ You can use the **Elements** list to explore all the elements and active conditi
 
 3D Scenes Studio is extensible to support additional viewing needs. The [viewer component](#viewer) can be embedded into custom applications, and can work in conjunction with 3rd party components.
 
-[!INCLUDE [digital-twins-3d-embed.md](../../includes/digital-twins-3d-embed.md)]
+[!INCLUDE [digital-twins-3d-embed.md](includes/digital-twins-3d-embed.md)]
 
 ## Limits and performance
 

articles/digital-twins/concepts-apis-sdks.md

@@ -27,13 +27,13 @@ Azure Digital Twins comes equipped with control plane APIs, data plane APIs, and
 
 ## Control plane overview
 
-[!INCLUDE [digital-twins-sdks-control-plane](../../includes/digital-twins-sdks-control-plane.md)]
+[!INCLUDE [digital-twins-sdks-control-plane](includes/digital-twins-sdks-control-plane.md)]
 
 You can also exercise the control plane APIs by interacting with Azure Digital Twins through the [Azure portal](https://portal.azure.com) and [CLI](/cli/azure/dt).
 
 ## Data plane overview
 
-[!INCLUDE [digital-twins-sdks-data-plane](../../includes/digital-twins-sdks-data-plane.md)]
+[!INCLUDE [digital-twins-sdks-data-plane](includes/digital-twins-sdks-data-plane.md)]
 
 You can also exercise the data plane APIs by interacting with Azure Digital Twins through the [CLI](/cli/azure/dt).
 

articles/digital-twins/concepts-azure-digital-twins-explorer.md

@@ -37,15 +37,15 @@ Developers may find this tool especially useful in the following scenarios:
 
 The explorer's main purpose is to help you visualize and understand your graph, and update your graph as needed. For large-scale solutions and for work that should be repeated or automated, consider using the [APIs and SDKs](./concepts-apis-sdks.md) to interact with your instance through code instead.
 
-[!INCLUDE [digital-twins-explorer-private-note.md](../../includes/digital-twins-explorer-private-note.md)]
+[!INCLUDE [digital-twins-explorer-private-note.md](includes/digital-twins-explorer-private-note.md)]
 
 ## How to access
 
 The main way to access Azure Digital Twins Explorer is through the [Azure portal](https://portal.azure.com).
 
 To open Azure Digital Twins Explorer for an Azure Digital Twins instance, first navigate to the instance in the portal, by searching for its name in the portal search bar.
 
-[!INCLUDE [digital-twins-access-explorer.md](../../includes/digital-twins-access-explorer.md)]
+[!INCLUDE [digital-twins-access-explorer.md](includes/digital-twins-access-explorer.md)]
 
 ## Features and capabilities
 
@@ -62,7 +62,7 @@ The sections of the explorer are as follows:
 
 For detailed instructions on how to use each feature, see [Use Azure Digital Twins Explorer](how-to-use-azure-digital-twins-explorer.md). 
 
-[!INCLUDE [digital-twins-explorer-dtdl](../../includes/digital-twins-explorer-dtdl.md)]
+[!INCLUDE [digital-twins-explorer-dtdl](includes/digital-twins-explorer-dtdl.md)]
 
 ## Other considerations
 

articles/digital-twins/concepts-cli.md

@@ -30,7 +30,7 @@ Some of the actions you can do using the command set include:
 
 The command set is called `az dt`, and is part of the [Azure IoT extension for Azure CLI](https://github.com/Azure/azure-iot-cli-extension). You can view the full list of commands and their usage as part of the reference documentation for the `az iot` command set: [az dt command reference](/cli/azure/dt).
 
-[!INCLUDE [digital-twins-cli-issue](../../includes/digital-twins-cli-issue.md)]
+[!INCLUDE [digital-twins-cli-issue](includes/digital-twins-cli-issue.md)]
 
 ## Uses (deploy and validate)
 

articles/digital-twins/concepts-event-notifications.md

@@ -25,7 +25,7 @@ There are several types of notifications that can be generated, and notification
 
 This chart shows the different notification types:
 
-[!INCLUDE [digital-twins-notifications.md](../../includes/digital-twins-notifications.md)]
+[!INCLUDE [digital-twins-notifications.md](includes/digital-twins-notifications.md)]
 
 ## Notification structure
 

articles/digital-twins/concepts-models.md

@@ -51,7 +51,7 @@ Azure Digital Twins also supports using a mix of v2 and v3 models within the sam
 
 You can also migrate existing v2 models to v3. For instructions on how to do this, see [Convert v2 models to v3](how-to-manage-model.md#convert-v2-models-to-v3).
 
-[!INCLUDE [digital-twins-explorer-dtdl](../../includes/digital-twins-explorer-dtdl.md)]
+[!INCLUDE [digital-twins-explorer-dtdl](includes/digital-twins-explorer-dtdl.md)]
 
 ## Model overview
 
@@ -312,7 +312,7 @@ While designing models to reflect the entities in your environment, it can be us
 
 ### Validate models
 
-[!INCLUDE [Azure Digital Twins: validate models info](../../includes/digital-twins-validate.md)]
+[!INCLUDE [Azure Digital Twins: validate models info](includes/digital-twins-validate.md)]
 
 ### Upload and delete models in bulk
 
@@ -330,7 +330,7 @@ Or, if you want to clear out the data in an instance by deleting all the models
 
 Once you have uploaded models into your Azure Digital Twins instance, you can use [Azure Digital Twins Explorer](https://explorer.digitaltwins.azure.net/) to view them. The explorer contains a list of all models in the instance, as well as a **model graph** that illustrates how they relate to each other, including any inheritance and model relationships.
 
-[!INCLUDE [digital-twins-explorer-dtdl](../../includes/digital-twins-explorer-dtdl.md)]
+[!INCLUDE [digital-twins-explorer-dtdl](includes/digital-twins-explorer-dtdl.md)]
 
 Here's an example of what a model graph might look like:
 

articles/digital-twins/concepts-query-language.md

@@ -31,7 +31,7 @@ You can use the Azure Digital Twins query language to retrieve digital twins acc
 
 To submit a query to the service from a client app, you'll use the Azure Digital Twins [Query API](/rest/api/digital-twins/dataplane/query). One way to use the API is through one of the [SDKs for Azure Digital Twins](concepts-apis-sdks.md#data-plane-overview).
 
-[!INCLUDE [digital-twins-query-reference.md](../../includes/digital-twins-query-reference.md)]
+[!INCLUDE [digital-twins-query-reference.md](includes/digital-twins-query-reference.md)]
 
 ## Considerations for querying
 
@@ -42,7 +42,7 @@ When writing queries for Azure Digital Twins, keep the following considerations
   :::code language="sql" source="~/digital-twins-docs-samples/queries/examples.sql" id="EscapedSingleQuote":::
 * If you're using the Azure CLI to run queries, you may need to escape certain additional characters to meet the requirements of various shells. For more information, see [Use special characters in different shells](concepts-cli.md#use-special-characters-in-different-shells)
 
-[!INCLUDE [digital-twins-query-latency-note.md](../../includes/digital-twins-query-latency-note.md)]
+[!INCLUDE [digital-twins-query-latency-note.md](includes/digital-twins-query-latency-note.md)]
 
 ## Querying historized twin data over time
 

articles/digital-twins/concepts-route-events.md

@@ -112,7 +112,7 @@ To learn how to set up an endpoint with dead-lettering, see [Endpoint options: D
 
 Different types of events in IoT Hub and Azure Digital Twins produce different types of notification messages, as described below.
 
-[!INCLUDE [digital-twins-notifications.md](../../includes/digital-twins-notifications.md)]
+[!INCLUDE [digital-twins-notifications.md](includes/digital-twins-notifications.md)]
 
 ## Next steps
 

articles/digital-twins/concepts-security.md

@@ -126,7 +126,7 @@ For instructions on how to set up Private Link for Azure Digital Twins, see [Ena
 >[!NOTE]
 > Private network access with Azure Private Link applies to accessing Azure Digital Twins through its rest APIs. This feature does not apply to egress scenarios using Azure Digital Twins's [event routing](concepts-route-events.md) feature.
 
-[!INCLUDE [digital-twins-explorer-private-note.md](../../includes/digital-twins-explorer-private-note.md)]
+[!INCLUDE [digital-twins-explorer-private-note.md](includes/digital-twins-explorer-private-note.md)]
 
 ### Design considerations 
 

articles/digital-twins/concepts-twins-graph.md

@@ -28,7 +28,7 @@ Before you can create a digital twin in your Azure Digital Twins instance, you n
 
 After creating and uploading a model, your client app can create an instance of the type. This instance is a digital twin. For example, after creating a model of Floor, you may create one or several digital twins that use this type (like a Floor-type twin called GroundFloor, another called Floor2, and so on).
 
-[!INCLUDE [digital-twins-versus-device-twins](../../includes/digital-twins-versus-device-twins.md)]
+[!INCLUDE [digital-twins-versus-device-twins](includes/digital-twins-versus-device-twins.md)]
 
 ## Relationships: A graph of digital twins
 
@@ -38,7 +38,7 @@ For example, the model Floor might define a `contains` relationship that targets
 
 The result of this process is a set of nodes (the digital twins) connected via edges (their relationships) in a graph.
 
-[!INCLUDE [visualizing with Azure Digital Twins explorer](../../includes/digital-twins-visualization.md)]
+[!INCLUDE [visualizing with Azure Digital Twins explorer](includes/digital-twins-visualization.md)]
 
 :::image type="content" source="media/concepts-azure-digital-twins-explorer/azure-digital-twins-explorer-demo.png" alt-text="Screenshot of Azure Digital Twins Explorer showing sample models and twins." lightbox="media/concepts-azure-digital-twins-explorer/azure-digital-twins-explorer-demo.png":::