From 2276b450a4bb26b62d69391edad96cbbdf05d37b Mon Sep 17 00:00:00 2001
From: sebbader-sap <107036549+sebbader-sap@users.noreply.github.com>
Date: Tue, 13 Feb 2024 11:46:09 +0100
Subject: [PATCH] extend explanation on dspace-trust child resources (#222)

---
 catalog/catalog.binding.https.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/catalog/catalog.binding.https.md b/catalog/catalog.binding.https.md
index b154171d..f6e26fc5 100644
--- a/catalog/catalog.binding.https.md
+++ b/catalog/catalog.binding.https.md
@@ -149,4 +149,4 @@ When an implementation supports protected [Datasets](../model/terminology.md#dat
 
 The contents of the response is a JSON object defined by individual trust specifications and not defined here.
 
-Note that if multiple [Connectors](../model/terminology.md#connector--data-service-) are hosted under the same base URL, a path segment appended to the base well-known URL can be used, for example, `https://example.com/.well-known/dspace-trust/connector1.`
+Note that if multiple [Connectors](../model/terminology.md#connector--data-service-) are hosted under the same base URL, an arbitrary path segment appended to the base well-known URL can be used, for example, `https://example.com/.well-known/dspace-trust/connector1.` In this case, the document retrievable at the `dspace-trust` path segment must contain all the child paths.