Add documentation for the static API

Author: satya164

versioned_docs/version-6.x/screen.md

@@ -147,3 +147,7 @@ This can be useful when we have some screens which we want to be removed or rese
   component={ProfileScreen}
 />
 ```
+
+### `listeners`
+
+Event listeners to subscribe to. See [`listeners` prop on `Screen`](navigation-events.md#listeners-prop-on-screen) for more details.

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

@@ -57,8 +57,8 @@ It's important to note that when using such a setup, you **don't manually naviga
 In our navigator, we can conditionally define appropriate screens. For our case, let's say we have 3 screens:
 
 - `SplashScreen` - This will show a splash or loading screen when we're restoring the token.
-- `SignInScreen` - This is the screen we show if the user isn't signed in already (we couldn't find a token).
-- `HomeScreen` - This is the screen we show if the user is already signed in.
+- `SignIn` - This is the screen we show if the user isn't signed in already (we couldn't find a token).
+- `Home` - This is the screen we show if the user is already signed in.
 
 So our navigator will look like:
 
@@ -141,6 +141,12 @@ import * as React from 'react';
 const AuthContext = React.createContext();
 ```
 
+In our component, we will:
+
+- Store the token and loading state in `useReducer`
+- Persist it to `SecureStore` and read it from there on app launch
+- Expose the methods for sign in and sign out to child components using `AuthContext`
+
 So our component will look like this:
 
 <samp id="auth-flow" />
@@ -192,6 +198,7 @@ export default function App({ navigation }) {
       }
 
       // After restoring token, we may need to validate it in production apps
+      // ...
 
       // This will switch to the App screen or Auth screen and this loading
       // screen will be unmounted and thrown away.
@@ -224,6 +231,10 @@ export default function App({ navigation }) {
     []
   );
 
+  if (state.isLoading) {
+    return <SplashScreen />;
+  }
+
   return (
     <AuthContext.Provider value={authContext}>
       <Stack.Navigator>
@@ -268,6 +279,8 @@ function SignInScreen() {
 }
 ```
 
+You can similarly fill in the other screens according to your requirements.
+
 ## Removing shared screens when auth state changes
 
 Consider the following example:

versioned_docs/version-7.x/migration-guides.md

@@ -6,7 +6,7 @@ sidebar_label: Migration Guides
 
 This page contains links to pages that will guide you through the process of upgrading React Navigation:
 
-- [Upgrading from 6.x to 7.x](../version-6.x/upgrading-from-6.x.md)
+- [Upgrading from 6.x to 7.x](../version-7.x/upgrading-from-6.x.md)
 - [Upgrading from 5.x to 6.x](../version-6.x/upgrading-from-5.x.md)
 - [Upgrading from 4.x to 5.x](../version-5.x/upgrading-from-4.x.md)
 - [Upgrading from 3.x to 4.x](../version-4.x/upgrading-from-3.x.md)

versioned_docs/version-7.x/screen.md

@@ -147,3 +147,7 @@ This can be useful when we have some screens which we want to be removed or rese
   component={ProfileScreen}
 />
 ```
+
+### `listeners`
+
+Event listeners to subscribe to. See [`listeners` prop on `Screen`](navigation-events.md#listeners-prop-on-screen) for more details.