Improved seat massager sample

digital-twin-model/README.md

@@ -1,6 +1,7 @@
 # Digital Twin Model
 
 ## Specifying the Digital Twin Model
+
 The digital twin model is specified using [DTDL V3](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v3/DTDL.v3.md). The DTDL is stored under the `digital-twin-model/dtdl` folder and each file defines a DTDL interface.
 
 DTDL's behavior is defined by several metamodel classes. Initially, we will only use some of these metamodel classes, namely, Interface, Property, Command and Relationship.
@@ -66,10 +67,10 @@ And here's an example of how a relationship might be represented in a DTDL insta
 
 In this example, the `hasFloor` field is an array of identifiers for `Floor` instances that are related to the `Building` instance.
 
-
 ## Using the Digital Twin Model in the Code
 
 The digital twin providers and consumers need to use the Digital Twin Model to perform digital twin interactions:
+
 - They need to use the model identifiers (denoted by "@id" in the DTDL) to identify the part of the model that they want or use.
 - They need and the model names (denoted by "name" in the DTDL model) to identify the member of a model part that they want or use.
 - They need property definitions to exchange the associated values.
@@ -85,5 +86,6 @@ The sdv_v1.rs file will setup namespaces based on the DTMIs used in the DTDL fil
 qualified names that look similar to the DTMIs (minus the 'dtmi:sdv:' prefix).
 
 For each namespace, we will define:
+
 - Constants for model ids (“ID”), model descriptions (“DESCRIPTION”), and model member names (“NAME”).
 - Structs named “TYPE” to define property values, command request payloads, command response payloads, and schema types.