Merge pull request react-navigation#23 from kendaganio/some-typos

Fix some typos

Author: brentvatne

docs/hello-react-navigation.md

@@ -4,7 +4,7 @@ title: Hello React Navigation
 sidebar_label: Hello React Navigation
 ---
 
-In a web browser, you can link to different pages using an anchor (`<a>`) tag. When the user clicks on a link, the URL is pushed to the browser history stack. When the user presses the back button, the browser pops the item from the top of the history stack, so the active page is now the previously visited page. React Native doesn't have a built-in idea of a global history stack like a web browser does -- this is where React Naviation enters the story.
+In a web browser, you can link to different pages using an anchor (`<a>`) tag. When the user clicks on a link, the URL is pushed to the browser history stack. When the user presses the back button, the browser pops the item from the top of the history stack, so the active page is now the previously visited page. React Native doesn't have a built-in idea of a global history stack like a web browser does -- this is where React Navigation enters the story.
 
 React Navigation's `StackNavigator` provides a way for your app to transition between screens and manage navigation history. If your app uses only one `StackNavigator` then it is conceptually similar to how a  web browser handles navigation state - your app pushes and pops items from the navigation stack as users interact with the it, and this results in the user seeing different screens. A key difference between how this works in a web browser and in React Navigation is that React Navigation's `StackNavigator` provides the gestures and animations that you would expect on Android and iOS when navigating between routes in the stack.
 
@@ -103,4 +103,4 @@ Now our stack has two *routes*, a `Home` route and a `Details` route. The `Home`
 - `StackNavigator` is a function that takes a route configuration object and an options object and returns a React component.
 - The keys in the route configuration object are the route names and the values are the configuration for that route. The only required property on the configuration is the `screen` (the component to use for the route).
 - To specify what the initial route in a stack is, provide an `initialRouteName` on the stack options object.
-- [Full source of what we have built so far](https://snack.expo.io/@react-navigation/hello-react-navigation).
+- [Full source of what we have built so far](https://snack.expo.io/@react-navigation/hello-react-navigation).

docs/navigating.md

@@ -4,7 +4,7 @@ title: Moving between screens
 sidebar_label: Moving between screens
 ---
 
-In the previous section, ["Hello React Navigation"](hello-react-navigation.html), we defined a `StackNavigator` with two routes (`Home` and `Details`), but we didn't learn how to let a user navigate from from `Home` to `Details` (although we did learn how to change the _initial_ route in our code, but forcing our users to clone our repository and change the route in our code in order to see another screen is arguably among the worst user experiences one could imagine).
+In the previous section, ["Hello React Navigation"](hello-react-navigation.html), we defined a `StackNavigator` with two routes (`Home` and `Details`), but we didn't learn how to let a user navigate from `Home` to `Details` (although we did learn how to change the _initial_ route in our code, but forcing our users to clone our repository and change the route in our code in order to see another screen is arguably among the worst user experiences one could imagine).
 
 If this was a web browser, we'd be able to write something like this:
 
@@ -114,4 +114,4 @@ Another common requirement is to be able to go back *multiple* screens -- for ex
 - `this.props.navigation.navigate('RouteName')` pushes a new route to the `StackNavigator`. We can call it as many times as we like and it will continue pushing routes.
 - The header bar will automatically show a back button, but you can programmatically go back by calling `this.props.navigation.goBack()`. On Android, the hardware back button just works as expected.
 - The `navigation` prop is available to all screen components (components defined as screens in route configuration and rendered by React Navigation as a route).
-- [Full source of what we have built so far](https://snack.expo.io/@react-navigation/going-back).
+- [Full source of what we have built so far](https://snack.expo.io/@react-navigation/going-back).