docs: use native-stack in auth-flow

Author: kacperkapusciak

static/examples/6.x/auth-flow.js

@@ -1,7 +1,7 @@
 import * as React from 'react';
 import { Button, Text, TextInput, View } from 'react-native';
 import { NavigationContainer } from '@react-navigation/native';
-import { createStackNavigator } from '@react-navigation/stack';
+import { createNativeStackNavigator } from '@react-navigation/native-stack';
 
 const AuthContext = React.createContext();
 
@@ -48,7 +48,7 @@ function SignInScreen() {
   );
 }
 
-const Stack = createStackNavigator();
+const Stack = createNativeStackNavigator();
 
 export default function App({ navigation }) {
   const [state, dispatch] = React.useReducer(

versioned_docs/version-6.x/auth-flow.md

@@ -44,7 +44,7 @@ This pattern has been in use by other routing libraries such as React Router for
 
 The magic happens when the value of the `isSignedIn` variable changes. Let's say, initially `isSignedIn` is `false`. This means, either `SignIn` or `SignUp` screens are shown. After the user signs in, the value of `isSignedIn` will change to `true`. React Navigation will see that the `SignIn` and `SignUp` screens are no longer defined and so it will remove them. Then it'll show the `Home` screen automatically because that's the first screen defined when `isSignedIn` is `true`.
 
-The example shows stack navigator, but you can use the same approach with any navigator.
+The example shows a native stack navigator, but you can use the same approach with any navigator.
 
 By conditionally defining different screens based on a variable, we can implement auth flow in a simple way that doesn't require additional logic to make sure that the correct screen is shown.
 
@@ -114,7 +114,7 @@ state.userToken == null ? (
 );
 ```
 
-> If you have both your login-related screens and rest of the screens in Stack navigators, we recommend to use a single Stack navigator and place the conditional inside instead of using 2 different navigators. This makes it possible to have a proper transition animation during login/logout.
+> If you have both your login-related screens and rest of the screens in native stack navigators, we recommend to use a single native stack navigator and place the conditional inside instead of using 2 different navigators. This makes it possible to have a proper transition animation during login/logout.
 
 ## Implement the logic for restoring the token