From 39fb87f0cf230cb0612ca151a0b32053bee789a4 Mon Sep 17 00:00:00 2001
From: Fulei Li <flli@thoughtworks.com>
Date: Wed, 17 Feb 2016 09:15:18 +0800
Subject: [PATCH] Fixed the typo in Lesson 09

---
 lessons/09-index-links.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lessons/09-index-links.md b/lessons/09-index-links.md
index aa98fd5b..1a9d997b 100644
--- a/lessons/09-index-links.md
+++ b/lessons/09-index-links.md
@@ -44,7 +44,7 @@ We can use `Link` as well by passing it the `onlyActiveOnIndex` prop
 That's fine, but we already abstracted away having to know what the
 `activeClassName` is with `Nav`.
 
-Remember, in `Nav` we're passing along all of our props to `Link` with
+Remember, in `NavLink` we're passing along all of our props to `Link` with
 the `{...spread}` syntax, so we can actually add the prop when we render
 a `NavLink` and it will make its way down to the `Link`: