Update notification.md

Fixed typos.
DuendeSoftware · Oct 2, 2023 · 7dd9757 · 7dd9757
1 parent a75c1de
commit 7dd9757
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/IdentityServer/v6/docs/content/ui/logout/notification.md b/IdentityServer/v6/docs/content/ui/logout/notification.md
@@ -7,7 +7,7 @@ weight: 50
 ## Notifying clients that the user has signed-out
 As part of the logout process you will want to ensure client applications are informed that the user has signed out.
 
-This is done by sending a notification to and endpoint provided by the each client application. Depending on your architecture, there are three supported techniques to call these endpoints:
+This is done by sending a notification to an endpoint provided by the each client application. Depending on your architecture, there are three supported techniques to call these endpoints:
 
 * front-channel notifications via the browser
 * back-channel notifications via server-side call
@@ -16,12 +16,12 @@ This is done by sending a notification to and endpoint provided by the each clie
 Regardless which technique you are using, Duende IdentityServer keeps track of the client applications involved with the current user session and provides helpers and automated ways of invoking the notification mechanisms.
 
 {{% notice note %}}
-Both the front-channel and JS-based notifications make use of cookies in iframes. If your architecture spans multiple sites, this will not work reliable. We recommend using back-channel notifications in this case. See the supported [specifications]({{< ref "/overview/specs" >}}) page for links to the relevant documents.
+Both the front-channel and JS-based notifications make use of cookies in iframes. If your architecture spans multiple sites, this will not work reliably. We recommend using back-channel notifications in this case. See the supported [specifications]({{< ref "/overview/specs" >}}) page for links to the relevant documents.
 {{% /notice %}}
 
 
 ### Front-channel server-side clients
-To signout the user from the server-side client applications via the front-channel spec, the "logged out" page in IdentityServer must render an *\<iframe>* for each client that points to the corresponding notification endpoint at the client.
+To sign the user out of the server-side client applications via the front-channel spec, the "logged out" page in IdentityServer must render an *\<iframe>* for each client that points to the corresponding notification endpoint at the client.
 
 Clients that wish to be notified must have the *FrontChannelLogoutUri* configuration value set.
 IdentityServer tracks which clients the user has signed into, and provides an API called *GetLogoutContextAsync* on the [IIdentityServerInteractionService]({{< ref "/reference/services/interaction_service#iidentityserverinteractionservice-apis" >}}). 
@@ -30,7 +30,7 @@ This API returns a *LogoutRequest* object with a *SignOutIFrameUrl* property tha
 See the [Quickstart UI](https://github.com/DuendeSoftware/IdentityServer.Quickstart.UI) account controller and signout view for an example.
 
 ### Back-channel server-side clients
-To signout the user from the server-side client applications via the back-channel the *IBackChannelLogoutService* service can be used. 
+To sign the user out of the server-side client applications via the back-channel the *IBackChannelLogoutService* service can be used. 
 IdentityServer will automatically use this service when your logout page removes the user's authentication cookie via a call to *HttpContext.SignOutAsync*.
 
 Clients that wish to be notified must have the [BackChannelLogoutUri]({{<ref "/reference/models/client#authentication--session-management">}}) configuration value set.