From b733b5ce212ce5a1c8501df556e8c4133d8880ca Mon Sep 17 00:00:00 2001
From: Michael McCool <michael.mccool@intel.com>
Date: Thu, 23 Jun 2022 09:29:57 -0300
Subject: [PATCH 1/3] Define Trusted Environment

---
 index.html | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 33f9ef79..9e4ceb65 100644
--- a/index.html
+++ b/index.html
@@ -809,6 +809,13 @@ <h1>Terminology</h1>
         constraints on options or subprotocol mechanisms.
         Examples are HTTP, CoAP, or MQTT.
       </dd>
+      <dt>
+        <dfn>Trusted Environment</dfn>
+      </dt>
+      <dd>Set of devices that assume each other's claims of
+        identity are authentic without proof and allow relatively unrestricted
+        access to one another over a common isolated network.
+      </dd>
       <dt>
         <dfn>Virtual Thing</dfn>
       </dt>
@@ -1253,7 +1260,7 @@ <h1>Common Deployment Patterns</h1>
       that are defined in later sections of this specification.
     </p>
     <p>
-    This section also makes use of the concept of a Trusted Environment,
+    This section also makes use of the concept of a <a>Trusted Environment</a>,
     which is a set of devices that allow relatively unrestricted
     access to one another.  This is a common approach but carries some
     risks, which are discussed in section

From 7543cf909ab58a3a51103bd30080a74c56fee80e Mon Sep 17 00:00:00 2001
From: Michael McCool <michael.mccool@intel.com>
Date: Thu, 23 Jun 2022 11:12:11 -0300
Subject: [PATCH 2/3] trusted environment -> Trusted Environment

---
 index.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.html b/index.html
index 9e4ceb65..b48c7b2e 100644
--- a/index.html
+++ b/index.html
@@ -4276,8 +4276,8 @@ <h2>Trusted Environment Risks</h2>
       In section
       <a href="#sec-common-deployment-patterns"></a>
       several usage scenarios are presented
-      that include the concept of a trusted environment and a security 
-      boundary. Entities that are members of a trusted environment
+      that include the concept of a <a>Trusted Environment</a> and a security 
+      boundary. Entities that are members of a <a>Trusted Environment</a>
       all share access to a common set of resources (such as a local
       network) and are implictly granted certain access rights to
       each other.  A common example would be a WiFi LAN in the home
@@ -4285,7 +4285,7 @@ <h2>Trusted Environment Risks</h2>
       with each other without any further access controls.
       Allowing implicit access rights like this and using a single
       shared secret for a large number of entities means that a single
-      malicious actor with access to the trusted environment can
+      malicious actor with access to the <a>Trusted Environment</a> can
       cause significant damage.
       </p>
       <p>

From a27f9aac0a3e82e71eb1ef9cdf0304658b3b2de8 Mon Sep 17 00:00:00 2001
From: Michael McCool <michael.mccool@intel.com>
Date: Mon, 27 Jun 2022 09:28:38 -0300
Subject: [PATCH 3/3] Update index.html

---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index b48c7b2e..3fd0cf40 100644
--- a/index.html
+++ b/index.html
@@ -814,7 +814,7 @@ <h1>Terminology</h1>
       </dt>
       <dd>Set of devices that assume each other's claims of
         identity are authentic without proof and allow relatively unrestricted
-        access to one another over a common isolated network.
+        access to one another over a common protected network.
       </dd>
       <dt>
         <dfn>Virtual Thing</dfn>