From 05ba9d169eea062f700e1468e3beef0545ab535b Mon Sep 17 00:00:00 2001 From: Marcin Kulbicki Date: Thu, 19 Sep 2024 19:01:25 +0200 Subject: [PATCH] =?UTF-8?q?fix(docs):=20correct=20grammar=20in=20part-2-ap?= =?UTF-8?q?p-structure=20tutorial=20regarding=E2=80=A6=20(#4742)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/tutorials/essentials/part-2-app-structure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorials/essentials/part-2-app-structure.md b/docs/tutorials/essentials/part-2-app-structure.md index 5df4d77548..0af585028e 100644 --- a/docs/tutorials/essentials/part-2-app-structure.md +++ b/docs/tutorials/essentials/part-2-app-structure.md @@ -606,7 +606,7 @@ If you're curious _why_ we use thunks for async logic, see this deeper explanati We know that we're not allowed to put any kind of async logic in reducers. But, that logic has to live somewhere. -If we have access to the Redux store, we could write some async code and call `store.dispatch()` when we're done: +If we had access to the Redux store, we could write some async code and call `store.dispatch()` when we're done: ```js const store = configureStore({ reducer: counterReducer })