Merge pull request #134689 from baanders/10-20-fixes

ADT- Fixes

Author: denrea

articles/digital-twins/how-to-manage-routes-apis-cli.md

@@ -65,7 +65,7 @@ Once you have created the topic, you can link it to Azure Digital Twins with the
 az dt endpoint create eventgrid --endpoint-name <Event-Grid-endpoint-name> --eventgrid-resource-group <Event-Grid-resource-group-name> --eventgrid-topic <your-Event-Grid-topic-name> -n <your-Azure-Digital-Twins-instance-name>
 ```
 
-Now, the event grid topic is available as an endpoint inside of Azure Digital Twins, under the name specified with the `--endpoint-name` argument. You will typically use that name as the target of an **event route**, which you'll create [later in this article](#event-routes-with-apis-and-the-c-sdk) using the Azure Digital Twins service API.
+Now, the event grid topic is available as an endpoint inside of Azure Digital Twins, under the name specified with the `--endpoint-name` argument. You will typically use that name as the target of an **event route**, which you'll create [later in this article](#create-an-event-route) using the Azure Digital Twins service API.
 
 ### Create an Event Hubs or Service Bus endpoint
 
@@ -152,7 +152,7 @@ Here is an example of a dead-letter message for a [twin create notification](how
 }
 ```
 
-## Event routes (with APIs and the C# SDK)
+## Create an event route
 
 To actually send data from Azure Digital Twins to an endpoint, you'll need to define an **event route**. Azure Digital Twins **EventRoutes APIs** let developers wire up event flow, throughout the system and to downstream services. Read more about event routes in [*Concepts: Routing Azure Digital Twins events*](concepts-route-events.md).
 
@@ -165,7 +165,7 @@ The samples in this section use the [.NET (C#) SDK](https://www.nuget.org/packag
 >
 > If you are scripting this flow, you may want to account for this by building in 2-3 minutes of wait time for the endpoint service to finish deploying before moving on to route setup.
 
-### Create an event route
+### Creation code with APIs and the C# SDK
 
 Event routes are defined using [data plane APIs](how-to-use-apis-sdks.md#overview-data-plane-apis). 
 
@@ -221,7 +221,7 @@ catch (RequestFailedException e)
 }
 ```
 
-### Filter events
+## Filter events
 
 Without filtering, endpoints receive a variety of events from Azure Digital Twins:
 * Telemetry fired by [digital twins](concepts-twins-graph.md) using the Azure Digital Twins service API

articles/digital-twins/how-to-manage-routes-portal.md

@@ -73,7 +73,7 @@ You can also view the endpoint that was created back on the *Endpoints* page for
 
 If the endpoint creation fails, observe the error message and retry after a few minutes.
 
-Now, the event grid topic is available as an endpoint inside of Azure Digital Twins, under the name specified in the _Name_ field. You will typically use that name as the target of an **event route**, which you'll create [later in this article](#event-routes).
+Now, the event grid topic is available as an endpoint inside of Azure Digital Twins, under the name specified in the _Name_ field. You will typically use that name as the target of an **event route**, which you'll create [later in this article](#create-an-event-route).
 
 ### Create an Event Hubs endpoint
 
@@ -95,7 +95,7 @@ You can verify that the endpoint is successfully created by checking the notific
 
 If the endpoint creation fails, observe the error message and retry after a few minutes.
 
-Now, the Event hub is available as an endpoint inside of Azure Digital Twins, under the name specified in the _Name_ field. You will typically use that name as the target of an **event route**, which you'll create [later in this article](#event-routes).
+Now, the Event hub is available as an endpoint inside of Azure Digital Twins, under the name specified in the _Name_ field. You will typically use that name as the target of an **event route**, which you'll create [later in this article](#create-an-event-route).
 
 ### Create a Service Bus endpoint
 
@@ -117,7 +117,7 @@ You can verify that the endpoint is successfully created by checking the notific
 
 If the endpoint creation fails, observe the error message and retry after a few minutes.
 
-Now, the Service Bus topic is available as an endpoint inside of Azure Digital Twins, under the name specified in the _Name_ field. You will typically use that name as the target of an **event route**, which you'll create [later in this article](#event-routes).
+Now, the Service Bus topic is available as an endpoint inside of Azure Digital Twins, under the name specified in the _Name_ field. You will typically use that name as the target of an **event route**, which you'll create [later in this article](#create-an-event-route).
 
 ### Create an endpoint with dead-lettering
 
@@ -127,7 +127,7 @@ In order to create an endpoint with dead-lettering enabled, you must use the [AR
 
 For instructions on how to do this with the APIs, see the [*APIs and CLI*](how-to-manage-routes-apis-cli.md#create-an-endpoint-with-dead-lettering) version of this article.
 
-## Event routes
+## Create an event route
 
 To actually send data from Azure Digital Twins to an endpoint, you'll need to define an **event route**. These routes let developers wire up event flow, throughout the system and to downstream services. Read more about event routes in [*Concepts: Routing Azure Digital Twins events*](concepts-route-events.md).
 
@@ -136,7 +136,7 @@ To actually send data from Azure Digital Twins to an endpoint, you'll need to de
 >[!NOTE]
 >If you have recently deployed your endpoints, validate that they're finished deploying **before** attempting to use them for a new event route. If you're unable to set up the route because the endpoints aren't ready, wait a few minutes and try again.
 
-### Create an event route 
+### Creation steps with the Azure portal
 
 An event route definition contains these elements:
 * The route name you want to use
@@ -162,7 +162,7 @@ For the route to be enabled, you must also **Add an event route filter** of at l
 
 When finished, hit the _Save_ button to create your event route.
 
-### Filter events
+## Filter events
 
 As described above, routes have a **filter** field. If the filter value on your route is `false`, no events will be sent to your endpoint. 
 

articles/digital-twins/media/includes/copy-config.png

@@ -54,7 +54,7 @@ First, **set up an Azure Digital Twins instance** and the required authenticatio
 * After setting up your Azure Digital Twins instance, you'll need the instance's **_host name_** ([find in portal](how-to-set-up-instance-portal.md#verify-success-and-collect-important-values)).
 
 To authenticate the ADT Explorer application, you'll also need to set up an **app registration**. Follow the instructions in [*How-to: Create an app registration*](how-to-create-app-registration.md) to set this up. 
-* Once you have an app registration, you'll need the registration's **_Application (client) ID_** and **_Directory (tenant) ID_** ([find these in the portal](how-to-create-app-registration.md#collect-client-id-and-tenant-id).
+* Once you have an app registration, you'll need the registration's **_Application (client) ID_** and **_Directory (tenant) ID_** ([find these in the portal](how-to-create-app-registration.md#collect-client-id-and-tenant-id)).
 
 ### Set ADT Explorer permissions
 

articles/digital-twins/quickstart-adt-explorer.md

@@ -15,23 +15,21 @@ Navigate on your machine to file you downloaded earlier from [*Azure Digital Twi
 
 Once inside the folder, navigate into _AdtSampleApp_. Open _**AdtE2ESample.sln**_ in Visual Studio 2019. 
 
-In Visual Studio, use the *Solution Explorer* pane to create a copy of the _SampleClientApp > **serviceConfig.json.TEMPLATE**_ file (you can use the right-select menus to copy and paste). Rename the copy *serviceConfig.json*. This will serve as a pre-set JSON file with the necessary configuration variables to run the project.
+In Visual Studio, select the _SampleClientApp > **appsettings.json**_ file to open it in the editing window. This will serve as a pre-set JSON file with the necessary configuration variables to run the project.
 
-Select the *serviceConfig.json* file to open it in the editing window. Change the `instanceUrl` to your Azure Digital Twins instance *hostName* URL (with *https://* in front of it as shown below).
+In the file body, change the `instanceUrl` to your Azure Digital Twins instance *hostName* URL (with *https://* in front of it as shown below).
 
 ```json
 {
   "instanceUrl": "https://<your-Azure-Digital-Twins-instance-hostName>"
 }
 ```
 
-
-
 Save and close the file. 
 
-Next, configure the *serviceConfig.json* file to be copied to the output directory when you build the *SampleClientApp*. To do this, right-select the *serviceConfig.json* file, and choose *Properties.* In the *Properties* inspector, change the value of the *Copy to Output Directory* property to *Copy if newer*.
+Next, configure the *appsettings.json* file to be copied to the output directory when you build the *SampleClientApp*. To do this, right-select the *appsettings.json* file, and choose *Properties.* In the *Properties* inspector, change the value of the *Copy to Output Directory* property to *Copy if newer*.
 
-:::image type="content" source="../articles/digital-twins/media/includes/copy-config.png" alt-text="Excerpt from Visual Studio window showing the Solution Explorer pane with serviceConfig.json highlighted, and the Properties pane with 'Copy to Output Directory' property set to 'Copy if newer'" border="false":::
+:::image type="content" source="../articles/digital-twins/media/includes/copy-config.png" alt-text="Excerpt from Visual Studio window showing the Solution Explorer pane with appsettings.json highlighted, and the Properties pane with 'Copy to Output Directory' property set to 'Copy if newer'" border="false":::
 
 Keep the _**AdtE2ESample**_ project open in Visual Studio to continue using it in the tutorial.