Removed some typos from drawer-navigator.md

Author: SharjeelSafdar

versioned_docs/version-6.x/drawer-navigator.md

@@ -22,7 +22,7 @@ npm install @react-navigation/drawer
 
 You also need to install [`react-native-gesture-handler`](https://docs.swmansion.com/react-native-gesture-handler/) and [`react-native-reanimated`](https://docs.swmansion.com/react-native-reanimated/).
 
-If you have a Expo managed project, in your project directory, run:
+If you have an Expo managed project, in your project directory, run:
 
 ```sh
 expo install react-native-gesture-handler react-native-reanimated
@@ -73,15 +73,15 @@ The `Drawer.Navigator` component accepts following props:
 
 #### `initialRouteName`
 
-The name of the route to render on first load of the navigator.
+The name of the route to render on the first load of the navigator.
 
 #### `screenOptions`
 
 Default options to use for the screens in the navigator.
 
 #### `backBehavior`
 
-This controls how going back in the navigator is handled. This includes when the back button is pressed/back gesture is performed, or `goBack` is called.
+This controls how going back in the navigator is handled. This includes when the back button is pressed, back gesture is performed, or `goBack` is called.
 
 It supports the following values:
 
@@ -95,7 +95,7 @@ It supports the following values:
 
 The default status of the drawer - whether the drawer should stay `open` or `closed` by default.
 
-When this is set to `open`, the drawer will be open from the initial render. It can be closed normally using gestures or programmatically. However, when going back, drawer will re-open if it was closed. This is essentially the opposite of the default behavior of the drawer where it starts `closed`, and back button closes an open drawer.
+When this is set to `open`, the drawer will be open from the initial render. It can be closed normally using gestures or programmatically. However, when going back, the drawer will re-open if it was closed. This is essentially the opposite of the default behavior of the drawer where it starts `closed`, and the back button closes an open drawer.
 
 #### `detachInactiveScreens`
 
@@ -107,7 +107,7 @@ Whether the screens should render the first time they are accessed. Defaults to
 
 Whether to use the legacy implementation based on Reanimated 1. The new implementation based on Reanimated 2 will perform better, but you need additional configuration and need to use Hermes with Flipper to debug.
 
-This defaults to `true` in following cases:
+This defaults to `true` in the following cases:
 
 - Reanimated 2 is not configured
 - App is connected to Chrome debugger (Reanimated 2 cannot be used with Chrome debugger)
@@ -119,7 +119,7 @@ Otherwise, it defaults to `false`
 
 Function that returns React element to render as the content of the drawer, for example, navigation items
 
-The content component receives following props by default:
+The content component receives the following props by default:
 
 - `state` - The [navigation state](navigation-state.md) of the navigator.
 - `navigation` - The navigation object for the navigator.
@@ -130,7 +130,7 @@ The content component receives following props by default:
 
 The default component for the drawer is scrollable and only contains links for the routes in the RouteConfig. You can easily override the default component to add a header, footer, or other content to the drawer. The default content component is exported as `DrawerContent`. It renders a `DrawerItemList` component inside a `ScrollView`.
 
-By default the drawer is scrollable and supports devices with notches. If you customize the content, you can use `DrawerContentScrollView` to handle this automatically:
+By default, the drawer is scrollable and supports devices with notches. If you customize the content, you can use `DrawerContentScrollView` to handle this automatically:
 
 ```js
 import {
@@ -231,7 +231,7 @@ The following [options](screen-options.md) can be used to configure the screens
 
 #### `title`
 
-Generic title that can be used as a fallback for `headerTitle` and `drawerLabel`.
+A generic title that can be used as a fallback for `headerTitle` and `drawerLabel`.
 
 #### `lazy`
 
@@ -304,7 +304,7 @@ Options are `left` or `right`. Defaults to `left` for LTR languages and `right`
 
 Type of the drawer. It determines how the drawer looks and animates.
 
-- `front`: Traditional drawer which covers the screen with a overlay behind it.
+- `front`: Traditional drawer which covers the screen with an overlay behind it.
 - `back`: The drawer is revealed behind the screen on swipe.
 - `slide`: Both the screen and the drawer slide on swipe to reveal the drawer.
 - `permanent`: A permanent drawer is shown as a sidebar. Useful for having always visible drawer on larger screens.
@@ -513,7 +513,7 @@ navigation.toggleDrawer();
 
 #### `jumpTo`
 
-Navigates to an existing screen in the drawer navigator. The method accepts following arguments:
+Navigates to an existing screen in the drawer navigator. The method accepts the following arguments:
 
 - `name` - _string_ - Name of the route to jump to.
 - `params` - _object_ - Screen params to pass to the destination route.
@@ -578,7 +578,7 @@ import { getDrawerStatusFromState } from '@react-navigation/drawer';
 const isDrawerOpen = getDrawerStatusFromState(navigation.getState()) === 'open';
 ```
 
-For class components, you can listen tp the `state` event to check if drawer was opened or closed:
+For class components, you can listen to the `state` event to check if drawer was opened or closed:
 
 ```js
 class Profile extends React.Component {
@@ -603,4 +603,4 @@ class Profile extends React.Component {
 
 ## Nesting drawer navigators inside others
 
-If a drawer navigator is nested inside of another navigator that provides some UI, for example a tab navigator or stack navigator, then the drawer will be rendered below the UI from those navigators. The drawer will appear below the tab bar and below the header of the stack. You will need to make the drawer navigator the parent of any navigator where the drawer should be rendered on top of its UI.
+If a drawer navigator is nested inside of another navigator that provides some UI, for example, a tab navigator or stack navigator, then the drawer will be rendered below the UI from those navigators. The drawer will appear below the tab bar and below the header of the stack. You will need to make the drawer navigator the parent of any navigator where the drawer should be rendered on top of its UI.