yanick/updux
1
0
Fork 0
Code Issues 6 Pull Requests Projects Releases 10 Wiki Activity

a few more grammar typos

Browse Source
This commit is contained in:
Trey Bianchini 2020-06-03 12:04:59 -05:00 committed by Yanick Champoux
parent 26bf0c962a
commit 84a9c4f77f
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/README.md
View File

@ -5,7 +5,7 @@ So, I'm a fan of [Redux](https://redux.js.org).
As I was looking into tools to help cut on its boilerplate,
I came across [rematch](https://rematch.github.io/rematch).
It has a few pretty darn good ideas.
It has some pretty darn good ideas.
Keeping mutations and asynchronous effects close to the
reducer definition? Nice. Automatically infering the
actions from the said mutations and effects? Genius!
@ -19,7 +19,7 @@ to work with `updeep` and to fit my peculiar needs. It offers features such as
* Mimic the way VueX has mutations (reducer reactions to specific actions) and
effects (middleware reacting to actions that can be asynchronous and/or
have side-effects), so everything pertaining to a store are all defined
have side-effects), so all things pertaining to a store are defined
in the space place.
* Automatically gather all actions used by the updux's effects and mutations,
and makes then accessible as attributes to the `dispatch` object of the

2
docs/recipes.md
View File

@ -3,7 +3,7 @@
## Mapping a mutation to all values of a state
Say you have a `todos` state that is an array of `todo` sub-states. It's easy
enough to have the main reducer maps away all items to the sub-reducer:
enough to have the main reducer map away all items to the sub-reducer:
```
const todo = new Updux({