Merge pull request #235 from nimaa77/feature/error-pages-fixes

Feature/error pages - fix 1

README.md

@@ -33,7 +33,7 @@ Next.js is awesome. However, its routing system isn't for me. IMHO React Router
 	- [Routing](#routing)
 		- [Parameterized Routing](#parameterized-routing)
 		- [Client Only Data and Routing](#client-only-data-and-routing)
-		- [Dynamic 404 and Redirects](#dynamic-404-and-redirects)
+		- [404 Page](#404-page)
 		- [Dynamic 404](#dynamic-404)
 		- [Redirect](#redirect)
 	- [Code Splitting](#code-splitting)
@@ -189,7 +189,7 @@ In some parts of your application, you may not need server data fetching at all
 would in client land: You can fetch data (in componentDidMount) and do routing
 the same exact way.
 
-### Dynamic 404 and Redirects
+### 404 Page
 
 React Router 4 can detect No Match (404) Routes and show a fallback component, you can define your custom fallback component in `routes.js` file.
 

src/NotFoundComponent.tsx

@@ -11,7 +11,7 @@ class NotFound extends React.Component {
 			<Route
 				render={({ staticContext }) => {
 					if (staticContext) staticContext.statusCode = 404;
-					return <div>The Page You Were Looking For Was Not Found</div>;
+					return NotFound.data;
 				}}
 			/>
 		)