Merge pull request #377 from Ranj101/patch-1

Fixes wording error
DuendeSoftware · Nov 28, 2023 · 3e3f6fd · 3e3f6fd
2 parents c31aaf6 + d471980
commit 3e3f6fd
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/IdentityServer/v5/docs/content/ui/logout/logout_context.md b/IdentityServer/v5/docs/content/ui/logout/logout_context.md
@@ -13,7 +13,7 @@ The logout page can be triggered in different ways:
 * External Provider Logout Notification (protocol)
 * Direct User Access (non-protocol)
 
-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.
+If the logout 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]({{<ref "/reference/services/interaction_service">}}) obtain a *LogoutRequest* object.
 

diff --git a/IdentityServer/v6/docs/content/ui/logout/logout_context.md b/IdentityServer/v6/docs/content/ui/logout/logout_context.md
@@ -13,7 +13,7 @@ The logout page can be triggered in different ways:
 * External Provider Logout Notification (protocol)
 * Direct User Access (non-protocol)
 
-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.
+If the logout 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]({{<ref "/reference/services/interaction_service">}}) to obtain a *LogoutRequest* object.
 

diff --git a/IdentityServer/v7/docs/content/ui/logout/logout_context.md b/IdentityServer/v7/docs/content/ui/logout/logout_context.md
@@ -13,7 +13,7 @@ The logout page can be triggered in different ways:
 * External Provider Logout Notification (protocol)
 * Direct User Access (non-protocol)
 
-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.
+If the logout 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]({{<ref "/reference/services/interaction_service">}}) to obtain a *LogoutRequest* object.