From 19fbaf2edebd787e9739fb3cf0f0941d330aaafe Mon Sep 17 00:00:00 2001
From: Ash Beitz <8304894+ashbeitz@users.noreply.github.com>
Date: Tue, 5 Mar 2024 16:43:38 -0800
Subject: [PATCH] Fix relationship detail in DTDL README (#104)

---
 digital-twin-model/README.md | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/digital-twin-model/README.md b/digital-twin-model/README.md
index 78b03205..f642f95e 100644
--- a/digital-twin-model/README.md
+++ b/digital-twin-model/README.md
@@ -59,13 +59,17 @@ Here's an example of how a relationship might be represented in a DTDL instance:
   "@id": "dtmi:com:example:Building:building1;1",  // Unique identifier for the instance
   "@type": "dtmi:com:example:Building;1",  // The DTDL model that the instance is based on
   "hasFloor": [
-    "dtmi:com:example:Floor:floor1;1",
-    "dtmi:com:example:Floor:floor2;1"
+    {
+      "@id": "dtmi:com:example:Floor:floor1;1"
+    },
+    {
+      "@id": "dtmi:com:example:Floor:floor2;1"
+    }
   ]
 }
 ```
 
-In this example, the `hasFloor` field is an array of identifiers for `Floor` instances that are related to the `Building` instance.
+In this example, the `hasFloor` field is an array of objects that contain identifiers for `Floor` instances that are related to the `Building` instance.
 
 ## Using the Digital Twin Model in the Code