From d2b877fb280479b8c04b28181e2cc0b9c8747995 Mon Sep 17 00:00:00 2001
From: Steve Burtenshaw <53346+stphnnnn@users.noreply.github.com>
Date: Wed, 14 Sep 2022 16:26:02 +0100
Subject: [PATCH] docs(client): `onUnauthenticated` reference (#5340)

---
 docs/docs/getting-started/client.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/getting-started/client.md b/docs/docs/getting-started/client.md
index 6ede0b9c2f..f2939a449f 100644
--- a/docs/docs/getting-started/client.md
+++ b/docs/docs/getting-started/client.md
@@ -67,7 +67,7 @@ export default function Component() {
 
 Due to the way how Next.js handles `getServerSideProps` and `getInitialProps`, every protected page load has to make a server-side request to check if the session is valid and then generate the requested page (SSR). This increases server load, and if you are good with making the requests from the client, there is an alternative. You can use `useSession` in a way that makes sure you always have a valid session. If after the initial loading state there was no session found, you can define the appropriate action to respond.
 
-The default behavior is to redirect the user to the sign-in page, from where - after a successful login - they will be sent back to the page they started on. You can also define an `onFail()` callback, if you would like to do something else:
+The default behavior is to redirect the user to the sign-in page, from where - after a successful login - they will be sent back to the page they started on. You can also define an `onUnauthenticated()` callback, if you would like to do something else:
 
 #### Example