values variables per convention

KingdomOfEnds · KingdomOfEnds · commit 49fa72e6565d · 2018-11-13T15:52:37.000-08:00
diff --git a/articles/digital-twins/concepts-device-ingress.md b/articles/digital-twins/concepts-device-ingress.md
@@ -6,7 +6,7 @@ manager: bertvanhoof
 ms.service: digital-twins
 services: digital-twins
 ms.topic: conceptual
-ms.date: 10/26/2018
+ms.date: 11/13/2018
 ms.author: alinast
 ---
 
@@ -37,20 +37,20 @@ In the following sections, you learn how to get the IoT Hub device connection st
 Do a GET call on the Device API with an `includes=ConnectionString` parameter to get the IoT Hub device connection string. Filter by the device GUID or the hardware ID to find the given device.
 
 ```plaintext
-yourManagementApiUrl/devices/yourDeviceGuid?includes=ConnectionString
+YOUR_MANAGEMENT_API_URL/devices/YOUR_DEVICE_GUID?includes=ConnectionString
 ```
 
 | Parameters | Replace with |
 | --- | --- |
-| *yourDeviceGuid* | The device ID |
+| *YOUR_DEVICE_GUID* | The device ID |
 
 ```plaintext
-yourManagementApiUrl/devices?hardwareIds=yourDeviceHardwareId&includes=ConnectionString
+YOUR_MANAGEMENT_API_URL/devices?hardwareIds=YOUR_DEVICE_HARDWARE_ID&includes=ConnectionString
 ```
 
 | Your parameter values | Replace with |
 | --- | --- |
-| *yourDeviceHardwareId* | The device hardware ID |
+| *YOUR_DEVICE_HARDWARE_ID* | The device hardware ID |
 
 In the response payload, copy the device's **connectionString** property. You use it when you call the Azure IoT device SDK to send data to Digital Twins.
 
diff --git a/articles/digital-twins/concepts-objectmodel-spatialgraph.md b/articles/digital-twins/concepts-objectmodel-spatialgraph.md
@@ -6,7 +6,7 @@ manager: bertvanhoof
 ms.service: digital-twins
 services: digital-twins
 ms.topic: conceptual
-ms.date: 10/26/2018
+ms.date: 11/13/2018
 ms.author: alinast
 ---
 
@@ -74,13 +74,13 @@ If you deploy a Digital Twins service in your subscription, you become the globa
 After you deploy Digital Twins from the [Azure portal](https://portal.azure.com), the [Swagger](https://swagger.io/tools/swagger-ui/) URL of the Management APIs is automatically generated. It's displayed in the Azure portal in the **Overview** section with the following format.
 
 ```plaintext
-https://yourInstanceName.yourLocation.azuresmartspaces.net/management/swagger
+https://YOUR_INSTANCE_NAME.YOUR_LOCATION.azuresmartspaces.net/management/swagger
 ```
 
 | Custom name | Replace with |
 | --- | --- |
-| yourInstanceName | The name of your Digital Twins instance |
-| yourLocation | Which server region your instance is hosted on |
+| YOUR_INSTANCE_NAME | The name of your Digital Twins instance |
+| YOUR_LOCATION | Which server region your instance is hosted on |
 
  The full URL format appears in this image.
 
diff --git a/articles/digital-twins/how-to-diagnose-user-defined-functions.md b/articles/digital-twins/how-to-diagnose-user-defined-functions.md
@@ -64,12 +64,12 @@ Without a role assignment created within Management API, the user-defined functi
 Check if a role assignment exists for your user-defined function through your Management API:
 
 ```plaintext
-GET yourManagementApiUrl/roleassignments?path=/&traverse=Down&objectId=yourUserDefinedFunctionId
+GET YOUR_MANAGEMENT_API_URL/roleassignments?path=/&traverse=Down&objectId=YOUR_USER_DEFINED_FUNCTION_ID
 ```
 
 | Parameters | Replace with |
 | --- | --- |
-| *yourUserDefinedFunctionId* | The ID of the user-defined function to retrieve role assignments for|
+| *YOUR_USER_DEFINED_FUNCTION_ID* | The ID of the user-defined function to retrieve role assignments for|
 
 If no role assignment is retrieved, follow this article on [How to create a role assignment for your user-defined function](./how-to-user-defined-functions.md).
 
@@ -78,13 +78,13 @@ If no role assignment is retrieved, follow this article on [How to create a role
 With the following call against your Azure Digital Twins instances' Management API, you will be able to determine if a given matcher applies for the given sensor.
 
 ```plaintext
-GET yourManagementApiUrl/matchers/yourMatcherIdentifier/evaluate/yourSensorIdentifier?enableLogging=true
+GET YOUR_MANAGEMENT_API_URL/matchers/YOUR_MATCHER_IDENTIFIER/evaluate/YOUR_SENSOR_IDENTIFIER?enableLogging=true
 ```
 
 | Parameters | Replace with |
 | --- | --- |
-| *yourMatcherIdentifier* | The ID of the matcher you wish to evaluate |
-| *yourSensorIdentifier* | The ID of the sensor you wish to evaluate |
+| *YOUR_MATCHER_IDENTIFIER* | The ID of the matcher you wish to evaluate |
+| *YOUR_SENSOR_IDENTIFIER* | The ID of the sensor you wish to evaluate |
 
 Response:
 
@@ -102,12 +102,12 @@ Response:
 With the following call against your Azure Digital Twins instances' Management API, you will be able to determine the identifiers of your user-defined functions that will be triggered by the given sensor's incoming telemetry:
 
 ```plaintext
-GET yourManagementApiUrl/sensors/yourSensorIdentifier/matchers?includes=UserDefinedFunctions
+GET YOUR_MANAGEMENT_API_URL/sensors/YOUR_SENSOR_IDENTIFIER/matchers?includes=UserDefinedFunctions
 ```
 
 | Parameters | Replace with |
 | --- | --- |
-| *yourSensorIdentifier* | The ID of the sensor that will be sending telemetry |
+| *YOUR_SENSOR_IDENTIFIER* | The ID of the sensor that will be sending telemetry |
 
 Response:
 
diff --git a/articles/digital-twins/how-to-user-defined-functions.md b/articles/digital-twins/how-to-user-defined-functions.md
@@ -39,7 +39,7 @@ Matchers are graph objects that determine what user-defined functions run for a
 The following example matcher evaluates to true on any sensor telemetry event with `"Temperature"` as its data type value. You can create multiple matchers on a user-defined function:
 
 ```plaintext
-POST yourManagementApiUrl/matchers
+POST YOUR_MANAGEMENT_API_URL/matchers
 {
   "Name": "Temperature Matcher",
   "Conditions": [
@@ -67,20 +67,20 @@ After the matchers are created, upload the function snippet with the following *
 > - The body is multipart:
 >   - The first part is about metadata needed for the UDF.
 >   - The second part is the JavaScript compute logic.
-> - In the **userDefinedBoundary** section, replace the **SpaceId** and **Machers** values.
+> - In the **USER_DEFINED_BOUNDARY** section, replace the **SpaceId** and **Machers** values.
 
 ```plaintext
-POST yourManagementApiUrl/userdefinedfunctions with Content-Type: multipart/form-data; boundary="userDefinedBoundary"
+POST YOUR_MANAGEMENT_API_URL/userdefinedfunctions with Content-Type: multipart/form-data; boundary="USER_DEFINED_BOUNDARY"
 ```
 
 | Parameter value | Replace with |
 | --- | --- |
-| *userDefinedBoundary* | A multipart content boundary name |
+| *USER_DEFINED_BOUNDARY* | A multipart content boundary name |
 
 ### Body
 
 ```plaintext
---userDefinedBoundary
+--USER_DEFINED_BOUNDARY
 Content-Type: application/json; charset=utf-8
 Content-Disposition: form-data; name="metadata"
 
@@ -90,15 +90,15 @@ Content-Disposition: form-data; name="metadata"
   "Description": "The contents of this udf will be executed when matched against incoming telemetry.",
   "Matchers": ["YOUR_MATCHER_IDENTIFIER"]
 }
---userDefinedBoundary
+--USER_DEFINED_BOUNDARY
 Content-Disposition: form-data; name="contents"; filename="userDefinedFunction.js"
 Content-Type: text/javascript
 
 function process(telemetry, executionContext) {
   // Code goes here.
 }
 
---userDefinedBoundary--
+--USER_DEFINED_BOUNDARY--
 ```
 
 | Your value | Replace with |
@@ -184,25 +184,25 @@ We need to create a role assignment for the user-defined function to run under.
 1. Query for roles and get the ID of the role you want to assign to the UDF. Pass it to **RoleId**:
 
     ```plaintext
-    GET yourManagementApiUrl/system/roles
+    GET YOUR_MANAGEMENT_API_URL/system/roles
     ```
 
 1. **ObjectId** will be the UDF ID that was created earlier.
 1. Find the value of **Path** by querying your spaces with `fullpath`.
 1. Copy the returned `spacePaths` value. You'll use that in the following code:
 
     ```plaintext
-    GET yourManagementApiUrl/spaces?name=yourSpaceName&includes=fullpath
+    GET YOUR_MANAGEMENT_API_URL/spaces?name=YOUR_SPACE_NAME&includes=fullpath
     ```
 
     | Parameter value | Replace with |
     | --- | --- |
-    | *yourSpaceName* | The name of the space you wish to use |
+    | *YOUR_SPACE_NAME* | The name of the space you wish to use |
 
 1. Paste the returned `spacePaths` value into **Path** to create a UDF role assignment:
 
     ```plaintext
-    POST yourManagementApiUrl/roleassignments
+    POST YOUR_MANAGEMENT_API_URL/roleassignments
     {
       "RoleId": "YOUR_DESIRED_ROLE_IDENTIFIER",
       "ObjectId": "YOUR_USER_DEFINED_FUNCTION_ID",
diff --git a/articles/digital-twins/security-create-manage-role-assignments.md b/articles/digital-twins/security-create-manage-role-assignments.md
@@ -6,7 +6,7 @@ manager: alinast
 ms.service: digital-twins
 services: digital-twins
 ms.topic: conceptual
-ms.date: 10/10/2018
+ms.date: 11/13/2018
 ms.author: lyrana
 ---
 
@@ -54,7 +54,7 @@ The supported `ObjectIdTypes`:
 ## Create a role assignment
 
 ```plaintext
-HTTP POST yourManagementApiUrl/roleassignments
+HTTP POST YOUR_MANAGEMENT_API_URL/roleassignments
 ```
 
 | **Name** | **Required** | **Type** | **Description** |
@@ -105,22 +105,22 @@ All users who are part of a domain receive read access for spaces, sensors, and
 Use GET to get a role assignment.
 
 ```plaintext
-HTTP GET yourManagementApiUrl/roleassignments?path={path}
+HTTP GET YOUR_MANAGEMENT_API_URL/roleassignments?path=YOUR_PATH
 ```
 
 | **Name** | **In** | **Required** |	**Type** |	**Description** |
 | --- | --- | --- | --- | --- |
-| path | Path | True | String |	The full path to the space |
+| YOUR_PATH | Path | True | String |	The full path to the space |
 
 Use DELETE to delete a role assignment.
 
 ```plaintext
-HTTP DELETE yourManagementApiUrl/roleassignments/{id}
+HTTP DELETE YOUR_MANAGEMENT_API_URL/roleassignments/YOUR_ROLE_ID
 ```
 
 | **Name** | **In** | **Required** | **Type** | **Description** |
 | --- | --- | --- | --- | --- |
-| id | Path | True | String |	Role Assignment ID |
+| YOUR_ROLE_ID | Path | True | String |	Role Assignment ID |
 
 ## Next steps
 
diff --git a/includes/digital-twins-management-api.md b/includes/digital-twins-management-api.md
@@ -10,13 +10,13 @@
  ms.custom: include file
 ---
 
-In the examples below, `yourManagementApiUrl` refers to the URI of the Digital Twins APIs:
+In the examples below, `YOUR_MANAGEMENT_API_URL` refers to the URI of the Digital Twins APIs:
 
 ```plaintext
-https://yourInstanceName.yourLocation.azuresmartspaces.net/management/api/v1.0/
+https://YOUR_INSTANCE_NAME.YOUR_LOCATION.azuresmartspaces.net/management/api/v1.0/
 ```
 
 | Custom name | Replace with |
 | --- | --- |
-| yourInstanceName | The name of your Azure Digital Twins instance |
-| yourLocation | Which server region your instance is hosted on |
+| YOUR_INSTANCE_NAME | The name of your Azure Digital Twins instance |
+| YOUR_LOCATION | Which server region your instance is hosted on |
diff --git a/includes/digital-twins-swagger.md b/includes/digital-twins-swagger.md
@@ -17,10 +17,10 @@
 You can access your own generated Management API Swagger documentation at:
 
 ```plaintext
-https://yourInstanceName.yourLocation.azuresmartspaces.net/management/swagger
+https://YOUR_INSTANCE_NAME.YOUR_LOCATION.azuresmartspaces.net/management/swagger
 ```
 
 | Custom name | Replace with |
 | --- | --- |
-| yourInstanceName | The name of your Azure Digital Twins instance |
-| yourLocation | Which server region your instance is hosted on |
+| YOUR_INSTANCE_NAME | The name of your Azure Digital Twins instance |
+| YOUR_LOCATION | Which server region your instance is hosted on |
