Skip to content

Commit abba695

Browse files
committed
Merge pull request #802 from landonwilkins/patch-2
nother tiny s/its/it's change
2 parents f240f47 + 072cba0 commit abba695

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/guides/overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ With React Router
134134
Here's how it works:
135135

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

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

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

0 commit comments

Comments
 (0)