From 35b4d8385e93daae2119b45b6ff99ae393d3ef9c Mon Sep 17 00:00:00 2001 From: David Klempfner Date: Mon, 2 Oct 2023 20:57:05 +1100 Subject: [PATCH] Update logout_context.md Fixed typos. --- IdentityServer/v6/docs/content/ui/logout/logout_context.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/IdentityServer/v6/docs/content/ui/logout/logout_context.md b/IdentityServer/v6/docs/content/ui/logout/logout_context.md index 0577192d..abd85876 100644 --- a/IdentityServer/v6/docs/content/ui/logout/logout_context.md +++ b/IdentityServer/v6/docs/content/ui/logout/logout_context.md @@ -15,7 +15,7 @@ The logout page can be triggered in different ways: If the login page is being triggered by a protocol workflow, then this means Duende IdentityServer has redirected the user's browser to the logout page. In these scenarios, a *logoutId* parameter will be passed that represents the logout context. -The *logoutId* value can be exchanged with the *GetLogoutContextAsync* API on the [interaction service]({{}}) obtain a *LogoutRequest* object. +The *logoutId* value can be exchanged with the *GetLogoutContextAsync* API on the [interaction service]({{}}) to obtain a *LogoutRequest* object. If the page is directly accessed by the user then there will be no *logoutId* parameter, but the context can still be accessed by calling *GetLogoutContextAsync* just without passing any parameters.