From 1b683f945bcbc37408b9ee681793c7cf25d35138 Mon Sep 17 00:00:00 2001 From: Anand Singh Date: Mon, 29 Oct 2018 15:35:56 +0530 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5785e03..e5a18b3 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,7 @@ For example, a "welcome user" label or a "login button" on a header. Or using th ### Before `react-check-auth` 1. On load, your app must make a request to some kind of a `/verifyUser` or a `/fetchUser` endpoint to check if the existing persisted token/cookie is available and valid. -2. You need to store that information in app state and pass it as a prop all through your component tree just so that that child components can access it or use `redux` to store the state and `connect()` the consuming component. +2. You need to store that information in app state and pass it as a prop all through your component tree just so that, that child components can access it or use `redux` to store the state and `connect()` the consuming component. ### After `react-check-auth`