From 2767bdef3bd5eaf9c8fc37556af664c8d3f03c4c Mon Sep 17 00:00:00 2001 From: Fulei Li Date: Mon, 15 Feb 2016 23:17:23 +0800 Subject: [PATCH 1/2] Not need this route in lesson 06 In Lesson 06, we did not need this route, it should be added in lesson 08. The lesson 08 have added it as below snippet. ``` {/* add it here, as a child of `/` */} ``` --- lessons/06-params.md | 1 - 1 file changed, 1 deletion(-) diff --git a/lessons/06-params.md b/lessons/06-params.md index 1554f465..929dcc09 100644 --- a/lessons/06-params.md +++ b/lessons/06-params.md @@ -49,7 +49,6 @@ import Repo from './modules/Repo' render(( - {/* add the new route */} From ecfa2daf2d3aa857c720746f4b14c353932fe325 Mon Sep 17 00:00:00 2001 From: Fulei Li Date: Wed, 17 Feb 2016 09:07:30 +0800 Subject: [PATCH 2/2] 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`: