facebook · gaearon · Oct 18, 2016 · Oct 18, 2016
diff --git a/docs/contributing/design-principles.md b/docs/contributing/design-principles.md
@@ -3,7 +3,7 @@ id: design-principles
 title: Design Principles
 layout: contributing
 permalink: contributing/design-principles.html
-prev: codebase-overview.html
+prev: implementation-notes.html
 ---
 
 We wrote this document so that you have a better idea of how we decide what React does and what React doesn't do, and what our development philosophy is like. While we are excited to see community contributions, we are not likely to choose a path that violates one or more of these principles.

diff --git a/docs/contributing/implementation-notes.md b/docs/contributing/implementation-notes.md
@@ -406,7 +406,7 @@ The host internal instances need to store:
 
 If you're struggling to imagine how an internal instance tree is structured in more complex applications, [React DevTools](https://github.com/facebook/react-devtools) can give you a close approximation, as it highlights host instances with grey, and composite instances with purple:
 
- <img src="/react/img/docs/implementation-notes-tree.png" width="500" alt="React DevTools tree" />
+ <img src="/react/img/docs/implementation-notes-tree.png" width="500" style="max-width: 100%" alt="React DevTools tree" />
 
 To complete this refactoring, we will introduce a function that mounts a complete tree into a container node, just like `ReactDOM.render()`. It returns a public instance, also like `ReactDOM.render()`:
 

diff --git a/docs/docs/composition-vs-inheritance.md b/docs/docs/composition-vs-inheritance.md
@@ -3,6 +3,7 @@ id: composition-vs-inheritance
 title: Composition vs Inheritance
 permalink: docs/composition-vs-inheritance.html
 prev: lifting-state-up.html
+next: thinking-in-react.html
 ---
 
 React has a powerful composition model, and we recommend using composition instead of inheritance to reuse code between components.

diff --git a/docs/docs/handling-events.md b/docs/docs/handling-events.md
@@ -2,6 +2,8 @@
 id: handling-events
 title: Handling Events
 permalink: docs/handling-events.html
+prev: state-and-lifecycle.html
+next: lifting-state-up.html
 ---
 
 Handling events with React elements is very similar to handling events on DOM elements. There are some syntactic differences:

diff --git a/docs/docs/state-and-lifecycle.md b/docs/docs/state-and-lifecycle.md
@@ -3,6 +3,7 @@ id: state-and-lifecycle
 title: State and Lifecycle
 permalink: docs/state-and-lifecycle.html
 prev: components-and-props.html
+next: handling-events.html
 ---
 
 Consider the ticking clock example from the [one of the previous sections](/react/docs/rendering-elements.html#updating-the-rendered-element).

diff --git a/docs/docs/thinking-in-react.md b/docs/docs/thinking-in-react.md
@@ -3,6 +3,7 @@ id: thinking-in-react
 title: Thinking in React
 permalink: docs/thinking-in-react.html
 redirect_from: 'blog/2013/11/05/thinking-in-react.html'
+prev: composition-vs-inheritance.html
 ---
 
 React is, in our opinion, the premier way to build big, fast Web apps with JavaScript. It has scaled very well for us at Facebook and Instagram.