From 57a356a1bd73d35a531dfdc94e62e8db20bc7ee8 Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sat, 16 Nov 2024 14:08:44 -0500
Subject: [PATCH] Clarify what happens after authentication.

---
 index.html | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)

diff --git a/index.html b/index.html
index cb57eae..e7ff2a4 100644
--- a/index.html
+++ b/index.html
@@ -1714,10 +1714,10 @@ <h2>Verification Relationships</h2>
             <h2>Authentication</h2>
 
             <p>
-The `authentication` [=verification relationship=] is used to
-specify how the [=controller=] is expected to be [=authenticated=], for
-purposes such as logging into a website or engaging in any sort of
-challenge-response protocol.
+The `authentication` [=verification relationship=] is used to specify how the
+[=controller=] is expected to be [=authenticated=], for purposes such as logging
+into a website or engaging in any sort of challenge-response protocol. The
+processing performed following authentication is application-specific.
             </p>
 
             <dl>
@@ -1767,10 +1767,6 @@ <h2>Authentication</h2>
     }
             </pre>
 
-            <p>
-If authentication is established, it is up to the application to decide what to
-do with that information.
-            </p>
             <p>
 This is useful to any entity verifying authentication that needs to check
 whether an entity that is attempting to [=authenticate=] is presenting a valid