From d3f0bc52d877261f61744cb101ab6065b4ac956a Mon Sep 17 00:00:00 2001
From: Ryan Florence <rpflorence@gmail.com>
Date: Mon, 2 Nov 2015 20:11:12 -0800
Subject: [PATCH] Update Introduction.md

---
 docs/Introduction.md | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/docs/Introduction.md b/docs/Introduction.md
index fbbe8e91c2..33d17994b3 100644
--- a/docs/Introduction.md
+++ b/docs/Introduction.md
@@ -189,7 +189,10 @@ render((
     <Route path="/" component={App}>
       <Route path="about" component={About} />
       <Route path="inbox" component={Inbox}>
-        {/* Add the route, nested where we want the UI to nest */}
+        {/* add some nested routes where we want the UI to nest */}
+        {/* render the stats page when at `/inbox` */}
+        <IndexRoute component={InboxStats}/>
+        {/* render the message component at /inbox/messages/123 */}
         <Route path="messages/:id" component={Message} />
       </Route>
     </Route>
@@ -197,7 +200,7 @@ render((
 ), document.body)
 ```
 
-Now visits to URLs like `inbox/messages/Jkei3c32` will match the new route and build this:
+Now visits to URLs like `inbox/messages/Jkei3c32` will match the new route and build this for you:
 
 ```
 <App>
@@ -207,6 +210,17 @@ Now visits to URLs like `inbox/messages/Jkei3c32` will match the new route and b
 </App>
 ```
 
+And visits to `/inbox` will build this:
+
+```
+<App>
+  <Inbox>
+    <InboxStats />
+  </Inbox>
+</App>
+```
+
+
 ### Getting URL Parameters
 
 We're going to need to know something about the message in order to fetch it from the server. Route components get some useful properties injected into them when you render, particularly the parameters from the dynamic segment of your path. In our case, `:id`.