From 41ac826daaa76a80d44ae576a41450a406c6bc1b Mon Sep 17 00:00:00 2001
From: Ranj Rashid <107559176+Ranj101@users.noreply.github.com>
Date: Wed, 15 Nov 2023 12:00:47 +0300
Subject: [PATCH 1/2] Update logout_context.md

---
 IdentityServer/v5/docs/content/ui/logout/logout_context.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/IdentityServer/v5/docs/content/ui/logout/logout_context.md b/IdentityServer/v5/docs/content/ui/logout/logout_context.md
index 0577192d..3c5099e5 100644
--- 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.
 

From d47198077bb2ccbc93db7c0056c6c732a562cdea Mon Sep 17 00:00:00 2001
From: Joe DeCock <josephdecock@gmail.com>
Date: Tue, 28 Nov 2023 12:39:13 -0600
Subject: [PATCH 2/2] Make same fixes in v6, v7

---
 IdentityServer/v6/docs/content/ui/logout/logout_context.md | 2 +-
 IdentityServer/v7/docs/content/ui/logout/logout_context.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/IdentityServer/v6/docs/content/ui/logout/logout_context.md b/IdentityServer/v6/docs/content/ui/logout/logout_context.md
index abd85876..034d859e 100644
--- 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
index abd85876..034d859e 100644
--- 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.