Skip to content

nother tiny s/its/it's change #802

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 9, 2015
Merged

nother tiny s/its/it's change #802

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/guides/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,7 +134,7 @@ With React Router
Here's how it works:

1. You declare your view hierarchy with nested `<Route/>`s and provide
them with a React element to handle the route when its active.
them with a React element to handle the route when it's active.

2. React Router will match the deepest route against the URL, and then
activate the entire tree of routes on that branch, nesting all the
Expand Down Expand Up @@ -189,7 +189,7 @@ When the user lands at `/inbox`, the route named `inbox` gets matched so
its parent route, `app`, is also matched. The `run` callback receives
`Handler`, that has all of this match information wrapped up in it.

Rendering `Handler` is really just rendering `App` since its the highest
Rendering `Handler` is really just rendering `App` since it's the highest
matched route handler. Since `inbox` is the active child route,
rendering `<RouteHandler/>` in `App` renders the `Inbox` element.
`<RouteHandler/>` is nearly identical to `{{outlet}}` from Ember or
Expand Down