From 9c12dfce4f166dae3181510783a16d6f00689873 Mon Sep 17 00:00:00 2001 From: Kien Nguyen Date: Sat, 19 Jan 2019 07:23:46 +0700 Subject: [PATCH] Fix typos for redux thunk (#27622) --- guide/english/redux/redux-thunk/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/english/redux/redux-thunk/index.md b/guide/english/redux/redux-thunk/index.md index d3d9afde5a..fc691f3f77 100644 --- a/guide/english/redux/redux-thunk/index.md +++ b/guide/english/redux/redux-thunk/index.md @@ -5,7 +5,7 @@ title: Redux Thunk Redux Thunk is middleware that allows you to return functions, rather than just actions, within Redux1. This allows for delayed actions, including working with promises. -The reason we use this middleware is for the reason that not all the actions we perform will be synchronus and some are bound to be non synchronous, like using axios to send a get request. This will take a bit of time and simple redux does not take into to account this behavious. So, Redux-thunk comes to the rescue by allowing us to dispatch actions asynchronously, so that we can allow these promises to get resolved. +The reason we use this middleware is for the reason that not all the actions we perform will be synchronus and some are bound to be non synchronous, like using axios to send a GET request. This will take a bit of time and simple redux does not take into to account this behaviour. So, Redux Thunk comes to the rescue by allowing us to dispatch actions asynchronously, so that we can allow these promises to get resolved. Example 1: