Skip to content

Commit 83eec9f

Browse files
committed
corrections and a few more
1 parent 1597dcd commit 83eec9f

9 files changed

+13
-13
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ Azure Digital Twins currently supports the following **EventTypes** that will be
4848

4949
> [!IMPORTANT]
5050
> Not all **EndpointTypes** support all **EventTypes**.
51-
> Read the following table for the **EventTypes** that are allowed for each **EndpointType**.
51+
> Review the following table for the **EventTypes** that are allowed for each **EndpointType**.
5252
5353
| | DeviceMessages | TopologyOperation | SpaceChange | SensorChange | UdfCustom |
5454
| ----------- | -------------- | ----------------- | ----------- | ------------ | --------- |

articles/digital-twins/how-to-configure-monitoring.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ Examples of use include:
9292
Full log querying is provided through [Azure Monitor logs](../azure-monitor/log-query/log-query-overview.md). To set up these powerful features:
9393

9494
1. Search for **Log Analytics** in the Azure portal.
95-
1. You will read your available **Log Analytics workspace** instances. Choose one and select **Logs** to query:
95+
1. Your available **Log Analytics workspace** instances will be displayed. Choose one and select **Logs** to query:
9696

9797
[![Log analytics](media/how-to-configure-monitoring/log-analytics.png)](media/how-to-configure-monitoring/log-analytics.png#lightbox)
9898

articles/digital-twins/how-to-configure-postman.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ After completing the previous steps, configure Postman to make an authenticated
125125
> * You do not need to specify those headers for each part.
126126
> * You must select `multipart/mixed` or another appropriate **Content-Type** for the entire request.
127127
128-
1. Lastly, select **Send** to submit your multipart HTTP POST request. A status code of `200` or `201` indicates a successful request. You will also read the appropriate response message.
128+
1. Lastly, select **Send** to submit your multipart HTTP POST request. A status code of `200` or `201` indicates a successful request. The appropriate response message will appear in the client interface.
129129
130130
## Next steps
131131

articles/digital-twins/how-to-use-swagger.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Management API object models are also listed.
4545

4646
You can select each listed object model for a more detailed summary of key attributes.
4747

48-
[![Swagger models expanded to read contents of models](media/how-to-use-swagger/swagger-management-model-img.png)](media/how-to-use-swagger/swagger-management-model-img.png#lightbox)
48+
[![Swagger models expanded to read the contents of models](media/how-to-use-swagger/swagger-management-model-img.png)](media/how-to-use-swagger/swagger-management-model-img.png#lightbox)
4949

5050
The generated Swagger object models are convenient to read all available Azure Digital Twins [objects and APIs](./concepts-objectmodel-spatialgraph.md). Developers can use this resource when they build solutions on Azure Digital Twins.
5151

@@ -61,13 +61,13 @@ Each listed endpoint also includes the required request information, such as the
6161

6262
[![Swagger endpoints displayed in Swagger UI](media/how-to-use-swagger/swagger-management-endpoints-img.png)](media/how-to-use-swagger/swagger-management-endpoints-img.png#lightbox)
6363

64-
To read a more detailed overview, select each resource.
64+
Select each resource to display their additional contents to get a more detailed overview.
6565

6666
## Use Swagger to test endpoints
6767

6868
One of the powerful functionalities Swagger provides is the ability to test an API endpoint directly through the documentation UI.
6969

70-
After you select a specific endpoint, you read **Try it out**.
70+
After you select a specific endpoint, the **Try it out** button will be displayed.
7171

7272
[![Swagger Try it out button](media/how-to-use-swagger/swagger-management-try-img.png)](media/how-to-use-swagger/swagger-management-try-img.png#lightbox)
7373

@@ -79,7 +79,7 @@ After you execute the test, you can validate the response data.
7979

8080
## Swagger response data
8181

82-
Each listed endpoint also includes response body data to validate your development and tests. These examples include the status codes and JSON you want to read for successful HTTP requests.
82+
Each listed endpoint also includes response body data to validate your development and tests. These examples include the status codes and JSON for successful HTTP requests.
8383

8484
[![Swagger JSON response example](media/how-to-use-swagger/swagger-management-response-img.png)](media/how-to-use-swagger/swagger-management-response-img.png#lightbox)
8585

articles/digital-twins/quickstart-view-occupancy-dotnet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ Build and run the sensor simulator device application by following these steps.
9999
1. Run `cd device-connectivity`.
100100
1. Run `dotnet restore`.
101101
1. Edit [appsettings.json](https://github.com/Azure-Samples/digital-twins-samples-csharp/blob/master/device-connectivity/appsettings.json) to update **DeviceConnectionString** with the previous `ConnectionString`. Save the updated file.
102-
1. Run `dotnet run` to start sending sensor data. You read it sent to Digital Twins as shown in the following image.
102+
1. Run `dotnet run` to start sending sensor data. It will be sent to Azure Digital Twins as shown in the following image.
103103

104104
[![Device Connectivity](media/quickstart-view-occupancy-dotnet/digital-twins-device-connectivity.png)](media/quickstart-view-occupancy-dotnet/digital-twins-device-connectivity.png#lightbox)
105105

articles/digital-twins/tutorial-facilities-analyze.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ You can use the [Event Hubs](../event-hubs/event-hubs-about.md) service to creat
153153

154154
1. The **Go to Environment** button opens the [Time Series Insights explorer](../time-series-insights/time-series-insights-explorer.md). If it doesn't show any events, simulate device events by browsing to the **device-connectivity** project of your Digital Twins sample, and running `dotnet run`.
155155

156-
1. After a few simulated events are generated, go back to the Time Series Insights explorer, and select the refresh button at the top. You should read analytical charts being created for your simulated sensor data.
156+
1. After a few simulated events are generated, go back to the Time Series Insights explorer, and select the refresh button at the top. Your analytical charts that are being created for your simulated sensor data will appear.
157157

158158
[![Chart in the Time Series Insights explorer](./media/tutorial-facilities-analyze/tsi-explorer.png)](./media/tutorial-facilities-analyze/tsi-explorer.png#lightbox)
159159

articles/digital-twins/tutorial-facilities-setup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ In the extracted sample folder, open the file **digital-twins-samples-csharp\dig
7171

7272
* You can use the provisioning sample **occupancy-quickstart** to configure and provision a [spatial intelligence graph](concepts-objectmodel-spatialgraph.md#digital-twins-object-models). This graph is the digitized image of your physical spaces and the resources in them. It uses an [object model](concepts-objectmodel-spatialgraph.md#digital-twins-object-models), which defines objects for a smart building. For a complete list of Digital Twins objects and REST APIs, visit [this REST API documentation](https://docs.westcentralus.azuresmartspaces.net/management/swagger) or the Management API URL that was created for [your instance](#deploy-digital-twins).
7373

74-
To explore the sample to read how it communicates with your Digital Twins instance, you can start with the **src\actions** folder. The files in this folder implement the commands that you'll use in these tutorials:
74+
To explore the sample to understand how it communicates with your Digital Twins instance, you can start with the **src\actions** folder. The files in this folder implement the commands that you'll use in these tutorials:
7575
- The **provisionSample.cs** file shows how to provision your spatial graph.
7676
- The **getSpaces.cs** file gets information about the provisioned spaces.
7777
- The **getAvailableAndFreshSpaces.cs** file gets the results of a custom function called a user-defined function.
@@ -98,7 +98,7 @@ In the extracted sample folder, open the file **digital-twins-samples-csharp\dig
9898
* **Tenant**: Enter the directory ID of your [Azure AD tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant). You also noted this ID in the section where you [set app permissions](#grant-permissions-to-your-app).
9999
* **BaseUrl**: Enter the URL of your Digital Twins instance. To get this URL, replace the placeholders in this URL with values for your instance: `https://yourDigitalTwinsName.yourLocation.azuresmartspaces.net/management/api/v1.0/`. You can also get this URL by modifying the Management API URL from [the deployment section](#deploy-digital-twins). Replace **swagger/** with **api/v1.0/**.
100100
101-
1. Read a list of Digital Twins features that you can explore by using the sample. Run the following command:
101+
1. Review a list of Digital Twins features that you can explore by using the sample. Run the following command:
102102
103103
```cmd/sh
104104
dotnet run

articles/digital-twins/tutorial-facilities-udf.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -230,7 +230,7 @@ In this section, you'll use the project named *device-connectivity* in the sampl
230230

231231
## Get results of the user-defined function
232232

233-
The user-defined function runs every time your instance receives device and sensor data. This section queries your Azure Digital Twins instance to get the results of the user-defined function. You'll read in near real time, when a room is available, that the air is fresh and temperature is right.
233+
The user-defined function runs every time your instance receives device and sensor data. This section queries your Azure Digital Twins instance to get the results of the user-defined function. You'll be notified in near real time, when a room is available, that the air is fresh and temperature is right.
234234

235235
1. Open the command window that you used to provision the sample, or a new command window, and go to the **occupancy-quickstart\src** folder of the sample again.
236236

includes/digital-twins-familiarity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,5 +13,5 @@
1313

1414
This article assumes some familiarity with authenticating to your Azure Digital Twins Management APIs.
1515

16-
* To learn more about authenticating with your Management APIs, see [Authenticating with Azure Digital Twins APIs](../articles/digital-twins/security-authenticating-apis.md).
16+
* To learn more about authenticating with your Management APIs, read [Authenticating with Azure Digital Twins APIs](../articles/digital-twins/security-authenticating-apis.md).
1717
* To authenticate with your Management APIs using the Postman REST client, read [How to configure Postman](../articles/digital-twins/how-to-configure-postman.md).

0 commit comments

Comments
 (0)