add missing determiner

Author: Daniel Martinez

docs/basics/Actions.md

@@ -21,7 +21,7 @@ import { ADD_TODO, REMOVE_TODO } from '../actionTypes';
 
 >##### Note on Boilerplate
 
->You don’t have to define action type constants in a separate file, or even to define them at all. For a small project, it might be easier to just use string literals for action types. However, there are some benefits to explicitly declaring constants in larger codebases. Read [Reducing Boilerplate](../recipes/ReducingBoilerplate.md) for more practical tips on keeping your codebase clean. 
+>You don’t have to define action type constants in a separate file, or even to define them at all. For a small project, it might be easier to just use string literals for action types. However, there are some benefits to explicitly declaring constants in larger codebases. Read [Reducing Boilerplate](../recipes/ReducingBoilerplate.md) for more practical tips on keeping your codebase clean.
 
 Other than `type`, the structure of an action object is really up to you. If you’re interested, check out [Flux Standard Action](https://github.com/acdlite/flux-standard-action) for recommendations on how actions could be constructed.
 
@@ -34,7 +34,7 @@ We’ll add one more action type to describe a user ticking off a todo as comple
 }
 ```
 
-It’s a good idea to pass as little data in action as possible. For example, it’s better to pass `index` than the whole todo object.
+It’s a good idea to pass as little data in each action as possible. For example, it’s better to pass `index` than the whole todo object.
 
 Finally, we’ll add one more action type for changing the currently visible todos.