Tidy

Author: dominicbetts

articles/iot-central/core/howto-manage-data-export-with-rest-api.md

@@ -57,7 +57,7 @@ The request body has some required fields:
 * `connectionString`: The connection string for accessing the destination resource.
 * `containerName`: For a blob storage destination, the name of the container where data should be written.
 
-The response to this request looks like the following example: 
+The response to this request looks like the following example:
 
 ```json
 {
@@ -99,7 +99,7 @@ Use the following request to retrieve a list of destinations from your applicati
 GET https://{your app subdomain}/api/dataExport/destinations?api-version=2022-10-31-preview
 ```
 
-The response to this request looks like the following example: 
+The response to this request looks like the following example:
 
 ```json
 {
@@ -206,7 +206,7 @@ There are some optional fields you can use to add more details to the export.
 * `enrichments`: Extra pieces of information to include with each sent message. Data is represented as a set of key/value pairs, where the key is the name of the enrichment that will appear in the output message and the value identifies the data to send.
 * `filter`: Query defining which events from the source should be exported.
 
-The response to this request looks like the following example: 
+The response to this request looks like the following example:
 
 ```json
 {
@@ -257,7 +257,7 @@ Use the following request to retrieve a list of export definitions from your app
 GET https://{your app subdomain}/api/dataExport/exports?api-version=2022-10-31-preview
 ```
 
-The response to this request looks like the following example: 
+The response to this request looks like the following example:
 
 ```json
 {

articles/iot-central/core/howto-manage-deployment-manifests-with-rest-api.md

@@ -12,7 +12,7 @@ services: iot-central
 
 # How to use the IoT Central REST API to manage deployment manifests
 
-A deployment manifest lets you specify the modules the IoT Edge runtime should download and configure. An IoT Edge device can download a deployment manifest when it first connects to your IoT Central application. This article describes how to manage deployment manifests in your IoT Central application by using the REST API.
+A deployment manifest lets you specify the modules the IoT Edge runtime should download and configure. An IoT Edge device can download a deployment manifest when it first connects to your IoT Central application. This article describes how to manage deployment manifests stored in your IoT Central application by using the REST API.
 
 To learn more about IoT Edge and IoT Central, see [Connect Azure IoT Edge devices to an Azure IoT Central application](concepts-iot-edge.md).
 
@@ -532,6 +532,7 @@ The response to this request looks like the following example:
 
 ## Assign a deployment manifest to a device
 
+To use a deployment manifest that's already stored in your IoT Central application, first use the [Get a deployment manifest](#get-a-deployment-manifest) API to fetch it.
 Use the following request to assign a deployment manifest to an IoT Edge device in your IoT Central application:
 
 ```http

articles/iot-central/core/howto-manage-device-templates-with-rest-api.md

@@ -189,7 +189,7 @@ Each entry in the list of interfaces in the implements section has a:
 * `name`: the programming name of the interface.
 * `schema`: the interface the capability model implements.
 
-The response to this request looks like the following example: 
+The response to this request looks like the following example:
 
 ```json
 {
@@ -737,7 +737,7 @@ Use the following request to retrieve a list of device templates from your appli
 GET https://{your app subdomain}/api/deviceTemplates?api-version=2022-07-31
 ```
 
-The response to this request looks like the following example: 
+The response to this request looks like the following example:
 
 ```json
 {
@@ -1057,7 +1057,6 @@ The response includes a **nextLink** value that you can use to retrieve the next
 
 Use **$filter** to create expressions that filter the list of device templates. The following table shows the comparison operators you can use:
 
-
 | Comparison Operator | Symbol | Example                        |
 | -------------------- | ------ | ------------------------------ |
 | Equals               | eq     | `'@id' eq 'dtmi:example:test;1'` |
@@ -1086,7 +1085,7 @@ Currently, *$filter* works with the following device template fields:
 
 Currently, the only supported filter function for device template lists is the `contains` function:
 
-```
+```txt
 $filter=contains(displayName, 'template1')
 $filter=contains(displayName, 'template1) eq false
 ```
@@ -1176,12 +1175,12 @@ The response to this request looks like the following example:
 
 Use **$orderby** to sort the results. Currently, **$orderby** only lets you sort on **displayName**. By default, **$orderby** sorts in ascending order. Use **desc** to sort in descending order, for example:
 
-```
+```txt
 $orderby=displayName
 $orderby=displayName desc
 ```
 
-The following example shows how to retrieve all the device templates where the result is sorted by `displayName` :
+The following example shows how to retrieve all the device templates where the result is sorted by `displayName`:
 
 ```http
 GET https://{your app subdomain}/api/deviceTemplates?api-version=2022-07-31&$orderby=displayName

articles/iot-central/core/howto-manage-devices-with-rest-api.md

@@ -3,7 +3,7 @@ title: How to use the IoT Central REST API to manage devices
 description: How to use the IoT Central REST API to add devices in an application
 author: dominicbetts
 ms.author: dobett
-ms.date: 06/22/2022
+ms.date: 11/30/2022
 ms.topic: how-to
 ms.service: iot-central
 services: iot-central
@@ -250,7 +250,6 @@ The response includes a **nextLink** value that you can use to retrieve the next
 
 Use **$filter** to create expressions that filter the list of devices. The following table shows the comparison operators you can use:
 
-
 | Comparison Operator | Symbol | Example                                 |
 | -------------------- | ------ | --------------------------------------- |
 | Equals               | eq     | `id eq 'device1' and scopes eq 'redmond'` |
@@ -429,7 +428,7 @@ The request body has some required fields:
 
 The organizations field is only used when an application has an organization hierarchy defined. To learn more about organizations, see [Manage IoT Central organizations](howto-edit-device-template.md)
 
-The response to this request looks like the following example: 
+The response to this request looks like the following example:
 
 ```json
 {
@@ -512,7 +511,7 @@ Use the following request to retrieve a list of device groups from your applicat
 GET https://{your app subdomain}/api/deviceGroups?api-version=2022-07-31
 ```
 
-The response to this request looks like the following example: 
+The response to this request looks like the following example:
 
 ```json
 {

articles/iot-central/core/howto-manage-jobs-with-rest-api.md

@@ -233,7 +233,6 @@ PUT https://{your app subdomain}.azureiotcentral.com/api/jobs/job-006?api-versio
 
 The `group` field in the request body identifies a device group in your IoT Central application. A job uses a device group to identify the set of devices the job operates on.
 
-
 If you don't already have a suitable device group, you can create one with REST API call. The following example creates a device group with `group1` as the group ID:
 
 ```http

articles/iot-central/core/howto-manage-organizations-with-rest-api.md

@@ -197,7 +197,7 @@ The REST API lets you list the roles defined in your IoT Central application. Us
 GET https://{your app subdomain}.azureiotcentral.com/api/roles?api-version=2022-07-31
 ```
 
-The response to this request looks like the following example that includes the application role and organization role IDs. 
+The response to this request looks like the following example that includes the application role and organization role IDs.
 
 ```json
 {
@@ -394,7 +394,7 @@ The request body has some required fields:
 * `description`: Short summary of device group.
 * `organizations` : List of organization IDs that the device is a part of. Currently, you can only associate a device with a single organization.
 
-The response to this request looks like the following example: 
+The response to this request looks like the following example:
 
 ```json
 {
@@ -410,4 +410,4 @@ The response to this request looks like the following example:
 
 ## Next steps
 
-Now that you've learned how to manage organizations with the REST API, a suggested next step is to [How to use the IoT Central REST API to manage data exports.](howto-manage-data-export-with-rest-api.md)
+Now that you've learned how to manage organizations with the REST API, a suggested next step is to [How to use the IoT Central REST API to manage data exports.](howto-manage-data-export-with-rest-api.md)

articles/iot-central/core/howto-upload-file-rest-api.md

@@ -157,7 +157,7 @@ The request body has the following fields:
 }
 ```
 
-The response to this request looks like the following example: 
+The response to this request looks like the following example:
 
 ```json
 {
@@ -235,7 +235,7 @@ DELETE https://{your-app-subdomain}.azureiotcentral.com/api/fileUploads?api-vers
 
 After you [configure file uploads](#add-a-file-upload-storage-account-configuration) in your IoT Central application, you can test it with the sample code. If you haven't already cloned the file upload sample repository, use the following commands to clone it to a suitable location on your local machine and install the dependent packages:
 
-```
+```cmd/sh
 git clone https://github.com/azure-Samples/iot-central-file-upload-device
 cd iotc-file-upload-device
 npm i
@@ -278,7 +278,7 @@ Copy the values for `ID scope`, `Device ID`, and `Primary key`. You'll use these
 
 Open the git repository you downloaded in VS code. Create an ".env" file at the root of your project and add the values you copied above. The file should look like the sample below with the values you made a note of previously.
 
-```
+```cmd/sh
 scopeId=<YOUR_SCOPE_ID>
 deviceId=<YOUR_DEVICE_ID>
 deviceKey=<YOUR_PRIMARY_KEY>
@@ -287,8 +287,7 @@ modelId=dtmi:IoTCentral:IotCentralFileUploadDevice;1
 
 Open the git repository you downloaded in VS code. Press F5 to run/debug the sample. In your terminal window you see that the device is registered and is connected to IoT Central:
 
-```
-
+```cmd/sh
 Starting IoT Central device...
  > Machine: Windows_NT, 8 core, freemem=6674mb, totalmem=16157mb
 Starting device registration...