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: