Fix typos (react-navigation#544)

Author: lex111

docs/compatibility.md

@@ -71,7 +71,7 @@ Due to the dynamic API of React Navigation 5, some functionality possible with t
 
 - It only wraps the core API, not navigator's API. This basically means that the options you're passing to a navigator might be a bit different.
 - Legacy deep link support by defining `path` in route configuration is not supported.
-- Navigating to a navigator doesn't work the same, i.e. we can't navigate to a screen in a navigator that's not rendered already, and params are't merged.
+- Navigating to a navigator doesn't work the same, i.e. we can't navigate to a screen in a navigator that's not rendered already, and params aren't merged.
 - Some methods such as the legacy `reset` method which take an array of actions isn't supported anymore. Unsupported methods will throw errors when using them as well as give type errors if we're using TypeScript.
 - It doesn't export `createAppContainer`, so you'll need to use the v5 API for the container (`NavigationNativeContainer`). This also means any features supported by the container need to be migrated to the new API.
 

docs/contributing.md

@@ -154,4 +154,4 @@ It's useful to run tests in watch mode when working on the project. To do it, ru
 yarn test --watch
 ```
 
-These commands will be run by our CI and are required to pass before any contributtions are merged.
+These commands will be run by our CI and are required to pass before any contributions are merged.

docs/custom-android-back-button-handling.md

@@ -6,7 +6,7 @@ sidebar_label: Custom Android back button behavior
 
 By default, when user presses the Android hardware back button, react-navigation will pop a screen or exit the app if there are no screens to pop. This is a sensible default behavior, but there are situations when you might want to implement custom handling.
 
-As an example, consider a screen where user is selecting items in a list, and a "selection mode" is active. On a back button press, you would first want the "selection mode" to be deactivated, and the screen should be popped only on the second back button press. The following code snippet demostrates the situation. We make use of [`BackHandler`](https://facebook.github.io/react-native/docs/backhandler.html) which comes with react-native along with the `useFocusEffect` hook to add our custom `hardwareBackPress` listener.
+As an example, consider a screen where user is selecting items in a list, and a "selection mode" is active. On a back button press, you would first want the "selection mode" to be deactivated, and the screen should be popped only on the second back button press. The following code snippet demonstrates the situation. We make use of [`BackHandler`](https://facebook.github.io/react-native/docs/backhandler.html) which comes with react-native along with the `useFocusEffect` hook to add our custom `hardwareBackPress` listener.
 
 Returning `true` from `onBackPress` denotes that we have handled the event, and react-navigation's listener will not get called, thus not popping the screen. Returning `false` will cause the event to bubble up and react-navigation's listener will pop the screen.
 

docs/custom-navigators.md

@@ -12,11 +12,11 @@ Under the hood, navigators are plain React components.
 
 We include some commonly needed navigators such as:
 
-- [createStackNavigator](stack-navigator.html) - Renders one screen at a time and provides transitions between screens. When a new screen is opened it is placed on top of the stack.
-- [createDrawerNavigator](drawer-navigator.html) - Provides a drawer that slides in from the left of the screen.
-- [createBottomTabNavigator](bottom-tab-navigator.html) - Renders a tab bar that lets the user switch between several screens.
-- [createMaterialTopTabNavigator](material-top-tab-navigator.html) - Renders tab view which lets the user switch between several screens using swipe gesture or the tab bar.
-- [createMaterialBottomTabNavigator](material-bottom-tab-navigator.html) - Renders tab view which lets the user switch between several screens using swipe gesture or the tab bar.
+- [`createStackNavigator`](stack-navigator.html) - Renders one screen at a time and provides transitions between screens. When a new screen is opened it is placed on top of the stack.
+- [`createDrawerNavigator`](drawer-navigator.html) - Provides a drawer that slides in from the left of the screen.
+- [`createBottomTabNavigator`](bottom-tab-navigator.html) - Renders a tab bar that lets the user switch between several screens.
+- [`createMaterialTopTabNavigator`](material-top-tab-navigator.html) - Renders tab view which lets the user switch between several screens using swipe gesture or the tab bar.
+- [`createMaterialBottomTabNavigator`](material-bottom-tab-navigator.html) - Renders tab view which lets the user switch between several screens using swipe gesture or the tab bar.
 
 ## Extending Navigators
 

docs/drawer-based-navigation.md

@@ -36,7 +36,7 @@ function MyNotificationsScreen({ navigation }) {
   );
 }
 
-exprt default function App() {
+export default function App() {
   return (
     <NavigationNativeContainer>
       <Drawer.Navigator initialRouteName="Feed">

docs/getting-started.md

@@ -20,8 +20,12 @@ Install the required packages in your React Native project.
 
 ```bash
 yarn add @react-navigation/core@next @react-navigation/native@next
-# or with npm
-# npm install @react-navigation/core@next @react-navigation/native@next
+```
+
+Or with npm
+
+```sh
+npm install @react-navigation/core@next @react-navigation/native@next
 ```
 
 When you use a navigator, you'll need to follow the installation instructions of that navigator for any additional configuration.

docs/glossary-of-terms.md

@@ -17,7 +17,7 @@ A screen component is a component that we use in our route configuration.
 ```js
 const Stack = createStackNavigator();
 
-const StactNavigator = (
+const StackNavigator = (
   <Stack.Navigator>
     <Stack.Screen
       name="Home"

docs/headers.md

@@ -163,7 +163,7 @@ function StackScreen() {
 
 ## Additional configuration
 
-You can read the full list of available `options` for screens inside of a stack navigator in the [createStackNavigator reference](stack-navigator.html#navigationoptions-used-by-stacknavigator).
+You can read the full list of available `options` for screens inside of a stack navigator in the [`createStackNavigator` reference](stack-navigator.html#navigationoptions-used-by-stacknavigator).
 
 ## Summary
 

docs/stack-actions.md

@@ -4,7 +4,7 @@ title: StackActions reference
 sidebar_label: StackActions
 ---
 
-`StackActions` is an object containing methods for generating actions specific to stack-based navigators. Its methods expand upon the actions available in [NavigationActions](navigation-actions.html).
+`StackActions` is an object containing methods for generating actions specific to stack-based navigators. Its methods expand upon the actions available in [`NavigationActions`](navigation-actions.html).
 
 The following actions are supported:
 

docs/tab-actions.md

@@ -4,7 +4,7 @@ title: TabActions reference
 sidebar_label: TabActions
 ---
 
-`TabActions` is an object containing methods for generating actions specific to tab-based navigators. Its methods expand upon the actions available in [NavigationActions](navigation-actions.html).
+`TabActions` is an object containing methods for generating actions specific to tab-based navigators. Its methods expand upon the actions available in [`NavigationActions`](navigation-actions.html).
 
 The following actions are supported:
 

docs/tab-based-navigation.md

@@ -6,7 +6,7 @@ sidebar_label: Tab navigation
 
 Possibly the most common style of navigation in mobile apps is tab-based navigation. This can be tabs on the bottom of the screen or on the top below the header (or even instead of a header).
 
-This guide covers [createBottomTabNavigator](bottom-tab-navigator.html). You may also use [createMaterialBottomTabNavigator](material-bottom-tab-navigator.html) and [createMaterialTopTabNavigator](material-top-tab-navigator.html) to add tabs to your application.
+This guide covers [`createBottomTabNavigator`](bottom-tab-navigator.html). You may also use [`createMaterialBottomTabNavigator`](material-bottom-tab-navigator.html) and [`createMaterialTopTabNavigator`](material-top-tab-navigator.html) to add tabs to your application.
 
 ## Minimal example of tab-based navigation
 
@@ -115,7 +115,7 @@ export default function IconWithBadge({
       {badgeCount > 0 && (
         <View
           style={{
-            // On react-native < 0.57 overflow outside of parent will not work on Android, see https://git.io/fhLJ8
+            // On React Native < 0.57 overflow outside of parent will not work on Android, see https://git.io/fhLJ8
             position: 'absolute',
             right: -6,
             top: -3,
@@ -137,11 +137,11 @@ export default function IconWithBadge({
 }
 ```
 
-From UI perspective this component is ready to use, but you still need to find some way to pass down the badge count properly from somewhere else, like using [React Context](https://reactjs.org/docs/context.html), [redux](https://redux.js.org/), [mobx](https://mobx.js.org/) or [event emitters](https://github.com/facebook/react-native/blob/master/Libraries/vendor/emitter/EventEmitter.js).
+From UI perspective this component is ready to use, but you still need to find some way to pass down the badge count properly from somewhere else, like using [React Context](https://reactjs.org/docs/context.html), [Redux](https://redux.js.org/), [MobX](https://mobx.js.org/) or [event emitters](https://github.com/facebook/react-native/blob/master/Libraries/vendor/emitter/EventEmitter.js).
 
 ```js
 export default function HomeIconWithBadge(props) {
-  // You should pass down the badgeCount in some other ways like react context api, redux, mobx or event emitters.
+  // You should pass down the badgeCount in some other ways like React Context API, Redux, MobX or event emitters.
   return <IconWithBadge {...props} badgeCount={3} />;
 }
 ```

docs/use-scroll-to-top.md

@@ -6,8 +6,9 @@ sidebar_label: useScrollToTop
 
 The expected native behavior of scrollable components is to to respond to events from navigation that will scroll to top when tapping on the active tab as you would expect from native tab bars.
 
-In order to achieve it we export `useScrollToTop` which accept ref to scrollable component (e,g. `ScrollView` or `FlatList`)
-Example
+In order to achieve it we export `useScrollToTop` which accept ref to scrollable component (e,g. `ScrollView` or `FlatList`).
+
+Example:
 
 ```js
 import * as React from 'react';

website/versioned_docs/version-1.x/contributing.md

@@ -178,4 +178,4 @@ React Navigation has tests implemented in [Jest](https://facebook.github.io/jest
 yarn run jest
 ```
 
-These commands will be run by our CI and are required to pass before any contributtions are merged.
+These commands will be run by our CI and are required to pass before any contributions are merged.

website/versioned_docs/version-1.x/custom-android-back-button-handling.md

@@ -7,7 +7,7 @@ original_id: custom-android-back-button-handling
 
 By default, when user presses the Android hardware back button, react-navigation will pop a screen or exit the app if there are no screens to pop. This is a sensible default behavior, but there are situations when you might want to implement custom handling.
 
-Take, for example, a screen where user is selecting items in a list, and a "selection mode" is active. On a back button press, you would first want the "selection mode" to be deactivated, and the screen should be popped only on the second back button press. The following code snippet demostrates the situation. We make use of [`BackHandler`](https://facebook.github.io/react-native/docs/backhandler.html) which comes with react-native to add our custom `hardwareBackPress` listener.
+Take, for example, a screen where user is selecting items in a list, and a "selection mode" is active. On a back button press, you would first want the "selection mode" to be deactivated, and the screen should be popped only on the second back button press. The following code snippet demonstrates the situation. We make use of [`BackHandler`](https://facebook.github.io/react-native/docs/backhandler.html) which comes with react-native to add our custom `hardwareBackPress` listener.
 
 Returning `true` from `onBackButtonPressAndroid` denotes that we have handled the event, and react-navigation's lister will not get called, thus not popping the screen. Returning `false` will cause the event to bubble up and react-navigation's listener will pop the screen.
 

website/versioned_docs/version-2.x/contributing.md

@@ -174,4 +174,4 @@ React Navigation has tests implemented in [Jest](https://facebook.github.io/jest
 yarn run jest
 ```
 
-These commands will be run by our CI and are required to pass before any contributtions are merged.
+These commands will be run by our CI and are required to pass before any contributions are merged.

website/versioned_docs/version-2.x/custom-android-back-button-handling.md

@@ -9,7 +9,7 @@ By default, when user presses the Android hardware back button, react-navigation
 
 > If you're looking for an easy-to-use solution, you can check out a community-developed package [react-navigation-backhandler](https://github.com/vonovak/react-navigation-backhandler). The following text shows what the package does under the cover.
 
-As an example, consider a screen where user is selecting items in a list, and a "selection mode" is active. On a back button press, you would first want the "selection mode" to be deactivated, and the screen should be popped only on the second back button press. The following code snippet demostrates the situation. We make use of [`BackHandler`](https://facebook.github.io/react-native/docs/backhandler.html) which comes with react-native and we [subscribe to navigation lifecycle updates](navigation-prop.html#addlistener-subscribe-to-updates-to-navigation-lifecycle) to add our custom `hardwareBackPress` listener.
+As an example, consider a screen where user is selecting items in a list, and a "selection mode" is active. On a back button press, you would first want the "selection mode" to be deactivated, and the screen should be popped only on the second back button press. The following code snippet demonstrates the situation. We make use of [`BackHandler`](https://facebook.github.io/react-native/docs/backhandler.html) which comes with react-native and we [subscribe to navigation lifecycle updates](navigation-prop.html#addlistener-subscribe-to-updates-to-navigation-lifecycle) to add our custom `hardwareBackPress` listener.
 
 Returning `true` from `onBackButtonPressAndroid` denotes that we have handled the event, and react-navigation's listener will not get called, thus not popping the screen. Returning `false` will cause the event to bubble up and react-navigation's listener will pop the screen.
 

website/versioned_docs/version-2.x/custom-navigator-overview.md

@@ -14,7 +14,7 @@ Under the hood, navigators are plain React components.
 `react-navigation` includes some commonly needed navigators such as:
 
 - [createStackNavigator](stack-navigator.html) - Renders one screen at a time and provides transitions between screens. When a new screen is opened it is placed on top of the stack.
-- [createBottomTabNavigator](bottom-tab-navigator.html) - Renders a tab bar that lets the user switch between several screens.
+- [`createBottomTabNavigator`](bottom-tab-navigator.html) - Renders a tab bar that lets the user switch between several screens.
 - [createSwitchNavigator](switch-navigator.html) - Switch between one screen and another with no UI on top of it, unmount screens when they become inactive.
 - [createDrawerNavigator](drawer-navigator.html) - Provides a drawer that slides in from the left of the screen.
 

website/versioned_docs/version-2.x/drawer-actions.md

@@ -5,7 +5,7 @@ sidebar_label: DrawerActions
 original_id: drawer-actions
 ---
 
-`DrawerActions` is an object containing methods for generating actions specific to drawer-based navigators. Its methods expand upon the actions available in [NavigationActions](navigation-actions.html).
+`DrawerActions` is an object containing methods for generating actions specific to drawer-based navigators. Its methods expand upon the actions available in [`NavigationActions`](navigation-actions.html).
 
 The following actions are supported:
 * [openDrawer](#openDrawer) - open the drawer

website/versioned_docs/version-2.x/headers.md

@@ -198,7 +198,7 @@ class HomeScreen extends React.Component {
 
 ## Additional configuration
 
-You can read the full list of available `navigationOptions` for screens inside of a stack navigator in the [createStackNavigator reference](stack-navigator.html#navigationoptions-used-by-stacknavigator).
+You can read the full list of available `navigationOptions` for screens inside of a stack navigator in the [`createStackNavigator` reference](stack-navigator.html#navigationoptions-used-by-stacknavigator).
 
 ## Summary
 

website/versioned_docs/version-2.x/stack-actions.md

@@ -5,7 +5,7 @@ sidebar_label: StackActions
 original_id: stack-actions
 ---
 
-`StackActions` is an object containing methods for generating actions specific to stack-based navigators. Its methods expand upon the actions available in [NavigationActions](navigation-actions.html).
+`StackActions` is an object containing methods for generating actions specific to stack-based navigators. Its methods expand upon the actions available in [`NavigationActions`](navigation-actions.html).
 
 The following actions are supported:
 * [Reset](#reset) - Replace current state with a new state

website/versioned_docs/version-2.x/tab-based-navigation.md

@@ -7,7 +7,7 @@ original_id: tab-based-navigation
 
 Possibly the most common style of navigation in mobile apps is tab-based navigation. This can be tabs on the bottom of the screen or on the top below the header (or even instead of a header).
 
-This guide covers [createBottomTabNavigator](bottom-tab-navigator.html). You may also use [createMaterialBottomTabNavigator](material-bottom-tab-navigator.html) and [createMaterialTopTabNavigator](material-top-tab-navigator.html) to add tabs to your application.
+This guide covers [`createBottomTabNavigator`](bottom-tab-navigator.html). You may also use [`createMaterialBottomTabNavigator`](material-bottom-tab-navigator.html) and [`createMaterialTopTabNavigator`](material-top-tab-navigator.html) to add tabs to your application.
 
 ## Minimal example of tab-based navigation
 

website/versioned_docs/version-3.x/contributing.md

@@ -158,4 +158,4 @@ React Navigation has tests implemented in [Jest](https://facebook.github.io/jest
 yarn run jest
 ```
 
-These commands will be run by our CI and are required to pass before any contributtions are merged.
+These commands will be run by our CI and are required to pass before any contributions are merged.

website/versioned_docs/version-3.x/custom-navigator-overview.md

@@ -14,7 +14,7 @@ Under the hood, navigators are plain React components.
 `react-navigation` includes some commonly needed navigators such as:
 
 - [createStackNavigator](stack-navigator.html) - Renders one screen at a time and provides transitions between screens. When a new screen is opened it is placed on top of the stack.
-- [createBottomTabNavigator](bottom-tab-navigator.html) - Renders a tab bar that lets the user switch between several screens.
+- [`createBottomTabNavigator`](bottom-tab-navigator.html) - Renders a tab bar that lets the user switch between several screens.
 - [createSwitchNavigator](switch-navigator.html) - Switch between one screen and another with no UI on top of it, unmount screens when they become inactive.
 - [createDrawerNavigator](drawer-navigator.html) - Provides a drawer that slides in from the left of the screen.
 

website/versioned_docs/version-3.x/headers.md

@@ -224,7 +224,7 @@ class HomeScreen extends React.Component {
 
 ## Additional configuration
 
-You can read the full list of available `navigationOptions` for screens inside of a stack navigator in the [createStackNavigator reference](stack-navigator.html#navigationoptions-used-by-stacknavigator).
+You can read the full list of available `navigationOptions` for screens inside of a stack navigator in the [`createStackNavigator` reference](stack-navigator.html#navigationoptions-used-by-stacknavigator).
 
 ## Summary
 

website/versioned_docs/version-3.x/switch-actions.md

@@ -5,7 +5,7 @@ sidebar_label: SwitchActions
 original_id: switch-actions
 ---
 
-`SwitchActions` is an object containing methods for generating actions specific to switch-based navigators. Its methods expand upon the actions available in [NavigationActions](navigation-actions.html).
+`SwitchActions` is an object containing methods for generating actions specific to switch-based navigators. Its methods expand upon the actions available in [`NavigationActions`](navigation-actions.html).
 
 The following actions are supported: