From 40f2867199c6ae3a95cefd90a9128e4f9c9cfe26 Mon Sep 17 00:00:00 2001 From: Mirko Quaglia Date: Wed, 11 Dec 2024 21:32:54 +0100 Subject: [PATCH] fix: grammatical issue in auth-flow --- versioned_docs/version-7.x/auth-flow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-7.x/auth-flow.md b/versioned_docs/version-7.x/auth-flow.md index 427e0390a2..c127c2ca63 100755 --- a/versioned_docs/version-7.x/auth-flow.md +++ b/versioned_docs/version-7.x/auth-flow.md @@ -278,7 +278,7 @@ In the above snippet, `isLoading` means that we're still checking if we have a t Next, we're exposing the sign in status via the `SignInContext` so that it's available to the `useIsSignedIn` and `useIsSignedOut` hooks. -In the above example, we're have one screen for each case. But you could also define multiple screens. For example, you probably want to define password reset, signup, etc screens as well when the user isn't signed in. Similarly for the screens accessible after sign in, you probably have more than one screen. We can use [`groups`](static-configuration.md#groups) to define multiple screens: +In the above example, we have one screen for each case. But you could also define multiple screens. For example, you probably want to define password reset, signup, etc screens as well when the user isn't signed in. Similarly for the screens accessible after sign in, you probably have more than one screen. We can use [`groups`](static-configuration.md#groups) to define multiple screens: ```js const RootStack = createNativeStackNavigator({