chore: edit auth-flow.md

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({
@@ -345,8 +345,6 @@ return (
 </TabItem>
 </Tabs>
 
-In the above snippet, `isLoading` means that we're still checking if we have a token. This can usually be done by checking if we have a token in `SecureStore` and validating the token. After we get the token and if it's valid, we need to set the `userToken`. We also have another state called `isSignout` to have a different animation on sign out.
-
 The main thing to notice is that we're conditionally defining screens based on these state variables:
 
 - `SignIn` screen is only defined if `userToken` is `null` (user is not signed in)