Fixed typos and errors in documentation (react-navigation#556)

Author: michizhou

docs/community-libraries-and-navigators.md

@@ -26,7 +26,7 @@ The library implements a custom navigator called `FluidNavigator` that makes all
 
 react-navigation-collapsible is a library and a `Higher Order Component` that adjusts your screen options and makes your screen header collapsible.
 
-Since react-navigation's header is designed as `Animated` component. You can animate the header by passing `Animated.Value` from your `ScrollView` or `FlatList` to the header.
+Since react-navigation's header is designed as `Animated` component, you can animate the header by passing `Animated.Value` from your `ScrollView` or `FlatList` to the header.
 
 #### Links
 

docs/compatibility.md

@@ -72,7 +72,7 @@ Due to the dynamic API of React Navigation 5, some functionality possible with t
 - It doesn't wrap navigator's props or options. This basically means that the options you're passing to a navigator might be a bit different as per breaking changes in the navigators.
 - 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 aren't merged to all child screens.
-- 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.
+- Some methods such as the legacy `reset` method which take an array of actions aren'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.
 - If you're using advanced APIs like Redux integration, custom routers and actions etc., they aren't supported.
 

docs/connecting-navigation-prop.md

@@ -6,7 +6,7 @@ sidebar_label: Access the navigation prop from any component
 
 [`useNavigation`](use-navigation.md) is a a hook which gives access to the `navigation` object. It's useful when you cannot pass the `navigation` prop into the component directly, or don't want to pass it in case of a deeply nested child.
 
-An ordinary component that is not a screen component will not receive the navigation prop automatically. for example in this `MyBackButton` component:
+An ordinary component that is not a screen component will not receive the navigation prop automatically. For example in this `MyBackButton` component:
 
 ```js
 import * as React from 'react';
@@ -27,7 +27,7 @@ export function MyBackButton({ navigation }) {
 
 To resolve this exception, you could pass the `navigation` prop in to `MyBackButton` when you render it from a screen, like so: `<MyBackButton navigation={props.navigation} />`.
 
-Alternatively, you can use the `useNavigation` to provide the `navigation` automatically automatically (through React context, if you're curious).
+Alternatively, you can use the `useNavigation` to provide the `navigation` prop automatically (through React context, if you're curious).
 
 ```js
 import * as React from 'react';

docs/custom-navigators.md

@@ -43,7 +43,7 @@ The hook returns an object with following properties:
 
 - `state` - The navigation state for the navigator. The component can take this state and decide how to render it.
 - `navigation` - The navigation object containing various helper methods for the navigator to manipulate the navigation state. This isn't the same as the navigation object for the screen and includes some helpers such as `emit` to emit events to the screens.
-- `descriptors` - This is an object containing descriptors for each route with the route keys as it's properties. The descriptor for a route can be accessed by `descriptors[route.key]`. Each descriptor contains the following properties:
+- `descriptors` - This is an object containing descriptors for each route with the route keys as its properties. The descriptor for a route can be accessed by `descriptors[route.key]`. Each descriptor contains the following properties:
 
   - `navigation` - The navigation prop for the screen. You don't need to pass this to the screen manually. But it's useful if we're rendering components outside the screen that need to receive `navigation` prop as well, such as a header component.
   - `options` - A getter which returns the options such as `title` for the screen if they are specified.

docs/deep-linking.md

@@ -133,11 +133,11 @@ This will result in something like:
 }
 ```
 
-If this doesn't satisfy your use case, The hook also accepts a `getStateFromPath` option where you can provide a custom function to convert the URL to a valid state object for more advanced use cases.
+If this doesn't satisfy your use case, the hook also accepts a `getStateFromPath` option where you can provide a custom function to convert the URL to a valid state object for more advanced use cases.
 
 ## Set up with Expo projects
 
-First, you will want to specify a url scheme for your app. This corresponds to the string before `://` in a url, so if your scheme is `mychat` then a link to your app would be `mychat://`. The scheme only applies to standalone apps and you need to re-build the standalone app for the change to take effect. In the Expo client app you can deep link using `exp://ADDRESS:PORT` where `ADDRESS` is often `127.0.0.1` and `PORT` is often `19000` - the URL is printed when you run `expo start`. If you want to test with your custom scheme you will need to run `expo build:ios -t simulator` or `expo build:android` and install the resulting binaries in your emulators. You can register for a scheme in your `app.json` by adding a string under the scheme key:
+First, you will want to specify a URL scheme for your app. This corresponds to the string before `://` in a URL, so if your scheme is `mychat` then a link to your app would be `mychat://`. The scheme only applies to standalone apps and you need to re-build the standalone app for the change to take effect. In the Expo client app you can deep link using `exp://ADDRESS:PORT` where `ADDRESS` is often `127.0.0.1` and `PORT` is often `19000` - the URL is printed when you run `expo start`. If you want to test with your custom scheme you will need to run `expo build:ios -t simulator` or `expo build:android` and install the resulting binaries in your emulators. You can register for a scheme in your `app.json` by adding a string under the scheme key:
 
 ```json
 {
@@ -238,7 +238,7 @@ In `SimpleApp/ios/SimpleApp/AppDelegate.m`:
 }
 ```
 
-In Xcode, open the project at `SimpleApp/ios/SimpleApp.xcodeproj`. Select the project in sidebar and navigate to the info tab. Scroll down to "URL Types" and add one. In the new URL type, set the identifier and the url scheme to your desired url scheme.
+In Xcode, open the project at `SimpleApp/ios/SimpleApp.xcodeproj`. Select the project in sidebar and navigate to the info tab. Scroll down to "URL Types" and add one. In the new URL type, set the identifier and the URL scheme to your desired URL scheme.
 
 ![Xcode project info URL types with mychat added](/docs/assets/deep-linking/xcode-linking.png)
 
@@ -260,7 +260,7 @@ To test the URI on a real device, open Safari and type `mychat://chat/jane`.
 
 To configure the external linking in Android, you can create a new intent in the manifest.
 
-In `SimpleApp/android/app/src/main/AndroidManifest.xml`, do these followings adjustments:
+In `SimpleApp/android/app/src/main/AndroidManifest.xml`, do these following adjustments:
 
 1. Set `launchMode` of `MainActivity` to `singleTask` in order to receive intent on existing `MainActivity`. It is useful if you want to perform navigation using deep link you have been registered - [details](http://developer.android.com/training/app-indexing/deep-linking.html#adding-filters)
 2. Add the new `intent-filter` inside the `MainActivity` entry with a `VIEW` type action:

docs/drawer-navigator.md

@@ -127,7 +127,7 @@ Allows for defining how far from the edge of the content view the swipe gesture
 
 #### `hideStatusBar`
 
-When set to true Drawer component will hide the OS status bar whenever the drawer is pulled or when its in an "open" state.
+When set to true Drawer component will hide the OS status bar whenever the drawer is pulled or when it's in an "open" state.
 
 #### `statusBarAnimation`
 
@@ -264,8 +264,8 @@ The `DrawerItem` component accepts the following props:
 - `onPress` (required): Function to execute on press.
 - `activeTintColor`: Color for the icon and label when the item is active.
 - `inactiveTintColor`: Color for the icon and label when the item is inactive.
-- `activeBackgroundColor`: Background color for item when its active.
-- `inactiveBackgroundColor`: Background color for item when its inactive.
+- `activeBackgroundColor`: Background color for item when it's active.
+- `inactiveBackgroundColor`: Background color for item when it's inactive.
 - `labelStyle`: Style object for the label `Text`.
 - `style`: Style object for the wrapper `View`.
 

website/versioned_docs/version-1.x/deep-linking.md

@@ -116,7 +116,7 @@ In `SimpleApp/ios/SimpleApp/AppDelegate.m`:
 }
 ```
 
-In Xcode, open the project at `SimpleApp/ios/SimpleApp.xcodeproj`. Select the project in sidebar and navigate to the info tab. Scroll down to "URL Types" and add one. In the new URL type, set the identifier and the url scheme to your desired url scheme.
+In Xcode, open the project at `SimpleApp/ios/SimpleApp.xcodeproj`. Select the project in sidebar and navigate to the info tab. Scroll down to "URL Types" and add one. In the new URL type, set the identifier and the URL scheme to your desired URL scheme.
 
 ![Xcode project info URL types with mychat added](/docs/assets/deep-linking/xcode-linking.png)
 

website/versioned_docs/version-2.x/community-libraries-and-navigators.md

@@ -25,7 +25,7 @@ The library implements a custom navigator called `FluidNavigator` that makes all
 
 react-navigation-collapsible is a library and a `Higher Order Component` that adjusts your navigationOptions and makes your screen header collapsible.
 
-Since react-navigation's header is designed as `Animated` component. You can animate the header by passing `Animated.Value` from your `ScrollView` or `FlatList` to the header.
+Since react-navigation's header is designed as `Animated` component, you can animate the header by passing `Animated.Value` from your `ScrollView` or `FlatList` to the header.
 
 #### Links
 

website/versioned_docs/version-2.x/deep-linking.md

@@ -116,7 +116,7 @@ In `SimpleApp/ios/SimpleApp/AppDelegate.m`:
 }
 ```
 
-In Xcode, open the project at `SimpleApp/ios/SimpleApp.xcodeproj`. Select the project in sidebar and navigate to the info tab. Scroll down to "URL Types" and add one. In the new URL type, set the identifier and the url scheme to your desired url scheme.
+In Xcode, open the project at `SimpleApp/ios/SimpleApp.xcodeproj`. Select the project in sidebar and navigate to the info tab. Scroll down to "URL Types" and add one. In the new URL type, set the identifier and the URL scheme to your desired URL scheme.
 
 ![Xcode project info URL types with mychat added](/docs/assets/deep-linking/xcode-linking.png)
 

website/versioned_docs/version-3.x/deep-linking.md

@@ -145,7 +145,7 @@ In `SimpleApp/ios/SimpleApp/AppDelegate.m`:
 }
 ```
 
-In Xcode, open the project at `SimpleApp/ios/SimpleApp.xcodeproj`. Select the project in sidebar and navigate to the info tab. Scroll down to "URL Types" and add one. In the new URL type, set the identifier and the url scheme to your desired url scheme.
+In Xcode, open the project at `SimpleApp/ios/SimpleApp.xcodeproj`. Select the project in sidebar and navigate to the info tab. Scroll down to "URL Types" and add one. In the new URL type, set the identifier and the URL scheme to your desired URL scheme.
 
 ![Xcode project info URL types with mychat added](/docs/assets/deep-linking/xcode-linking.png)