From 39ad0e37df4d70449cc64c3da59ca09f4fb7d510 Mon Sep 17 00:00:00 2001
From: Aaron Coburn <aaronc@inrupt.com>
Date: Thu, 6 Aug 2026 13:59:26 -0500
Subject: [PATCH] Integrate access request terminology with main terminology
 section

---
 lws10-core/index.html               | 11 +++++++++++
 lws10-core/lws-access-requests.html | 26 --------------------------
 2 files changed, 11 insertions(+), 26 deletions(-)

diff --git a/lws10-core/index.html b/lws10-core/index.html
index 3ba4f6d..42314f9 100644
--- a/lws10-core/index.html
+++ b/lws10-core/index.html
@@ -208,6 +208,17 @@ <h2>Terminology</h2>
         This specification defines the following terms:
       </p>
       <ul>
+        <li><dfn>access grant</dfn> &mdash; a data object created by a <a>storage controller</a>, expressing
+        an ability for an <a>agent</a> to perform specific actions on <a>storage</a> resources within certain
+        defined constraints.</li>
+        <li><dfn data-lt="access profiles">access profile</dfn> &mdash; an access profile describes the
+        requirements for expressing a valid access policy. Every access profile is identified
+        with a URI, and a server indicates support for one or more access profiles by
+        referencing them in the <code>conformsTo</code> property of a service object in its
+        <a>storage description</a> resource.</li>
+        <li><dfn>access request</dfn> &mdash; a data object submitted by an <a>agent</a>, expressing a
+        request to perform specific actions on storage resources, including the desired scope
+        and constraints.</li>
         <li><dfn data-lt="agents">agent</dfn> &mdash; a person, social entity, or software identified by a URI.</li>
         <li><dfn data-lt="authentication credentials">authentication credential</dfn> &mdash; a security token that asserts claims about an <a>agent</a> or end-user. This token is secured with a cryptographic proof.
           Examples of authentication credentials include assertions of identity such as OpenID Connect ID Tokens and SAML-based assertions as well as assertions of
diff --git a/lws10-core/lws-access-requests.html b/lws10-core/lws-access-requests.html
index a44759e..67e12e0 100644
--- a/lws10-core/lws-access-requests.html
+++ b/lws10-core/lws-access-requests.html
@@ -19,32 +19,6 @@
   actions, constraints, and assignees. Other profiles could use a different conceptual framework.
 </p>
 
-<div class="issue" title="Integrate with main terminology section">
-<p>
-  This section defines the following terms:
-</p>
-
-<ul>
-  <li>
-    <dfn>Access Request</dfn> &mdash; a data object submitted by an <a>agent</a>, expressing a
-    request to perform specific actions on storage resources, including the desired scope
-    and constraints.
-  </li>
-  <li>
-    <dfn>Access Grant</dfn> &mdash; a data object created by a <a>storage controller</a>, expressing
-    an ability for an <a>agent</a> to perform specific actions on <a>storage</a> resources within certain
-    defined constraints.
-  </li>
-  <li>
-    <dfn data-lt="access profiles">Access Profile</dfn> &mdash; an access profile describes the
-    requirements for expressing a valid access policy. Every access profile is identified
-    with a URI, and a server indicates support for one or more access profiles by
-    referencing them in the <code>conformsTo</code> property of a service object in its
-    <a>storage description</a> resource.
-  </li>
-</ul>
-</div>
-
 <section id="access-discovery">
   <h3>Discovery</h3>