From bc45b6d47f92649b8f0057de71f1a04bfaf3579a Mon Sep 17 00:00:00 2001
From: Ben Alpert <spicyjalapeno@gmail.com>
Date: Tue, 24 Jun 2014 19:08:59 -0700
Subject: [PATCH] Explain how route nesting works with an example

Not being familiar with Ember, I wasn't clear on how nested routes work. This example would definitely have helped me understand (assuming it's correct).
---
 README.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/README.md b/README.md
index 306d9c929a..8b6c46fc21 100644
--- a/README.md
+++ b/README.md
@@ -65,6 +65,18 @@ way down the view hierarchy. This allows you to create nested layouts
 without having to wire it all up yourself. `Link` components create
 accessible anchor tags to route you around the application.
 
+As an example, if the current path is `/user/17`, the following
+component will be rendered:
+
+```js
+<App activeRoute={
+  <Users activeRoute={<User params={{userId: 17}} />} />
+} />
+```
+
+Each component will also receive a `query` prop equal to a dictionary
+of the current query params.
+
 Here's the rest of the application:
 
 ```js