Minor grammar fixes in docs, recipes (prescottprue#243)

* docs(readme): Grammar fixes

* docs(api,recipes): Grammar fixes

* chore(gitignore): Ignore Jetbrains' project configuration files

Author: sublimeye

.gitignore

@@ -9,4 +9,5 @@ _book
 # Logs
 *.log
 .DS_Store
+.idea
 examples/complete/react-native/ios/build

README.md

@@ -45,18 +45,18 @@ npm install --save react-redux-firebase
 
 The above install command will install the `@latest` tag. You may also use the following tags when installing to get different versions:
 
-* `@next` - Next upcoming release. Currently points to active progress with `v1.5.0-*` pre-releases
-* `@canary` - Most possible up to date code. Currently points to active progress with `v2.0.0-*` pre-releases. *Warning:* Syntax is different than current stable version.
+* `@next` - Next upcoming release. Currently, points to active progress with `v1.5.0-*` pre-releases
+* `@canary` - Most possible up to date code. Currently, points to active progress with `v2.0.0-*` pre-releases. *Warning:* Syntax is different than current stable version.
 
 Other versions docs are available using the dropdown on the above docs link. For quick access:
 * [Version `1.5.0` Docs](http://docs.react-redux-firebase.com/history/v1.5.0/)
 * [Version `2.0.0` Docs](http://docs.react-redux-firebase.com/history/v2.0.0/)
 
-Be aware of changes when using version that are tagged `@latest`. Please report any issues you encounter, and try to keep an eye on the [releases page](https://github.com/prescottprue/react-redux-firebase/releases) for updates.
+Be aware of changes when using a version that is tagged `@latest`. Please report any issues you encounter, and try to keep an eye on the [releases page](https://github.com/prescottprue/react-redux-firebase/releases) for updates.
 
 ## Use
 
-**Note:** If you are just starting a new project, you may want to use [`v2.0.0`](http://docs.react-redux-firebase.com/history/v2.0.0/#use) since it is has an even easier syntax. For clarity on the transition, view the [`v1` -> `v2` migration guide](http://docs.react-redux-firebase.com/history/v2.0.0/docs/v2-migration-guide.html)
+**Note:** If you are just starting a new project, you may want to use [`v2.0.0`](http://docs.react-redux-firebase.com/history/v2.0.0/#use) since it has an even easier syntax. For clarity on the transition, view the [`v1` -> `v2` migration guide](http://docs.react-redux-firebase.com/history/v2.0.0/docs/v2-migration-guide.html)
 
 Include `reactReduxFirebase` in your store compose function and  `firebaseStateReducer` in your reducers:
 
@@ -204,7 +204,7 @@ export default class SomeComponent extends Component {
 }
 ```
 
-In order to enable this functionality, you will most likely need to install a plugin (depending on your build setup). For Webpack and Babel, you will need to make sure you have installed and enabled  [babel-plugin-transform-decorators-legacy](https://github.com/loganfsmyth/babel-plugin-transform-decorators-legacy) by doing the following:
+To enable this functionality, you will most likely need to install a plugin (depending on your build setup). For Webpack and Babel, you will need to make sure you have installed and enabled  [babel-plugin-transform-decorators-legacy](https://github.com/loganfsmyth/babel-plugin-transform-decorators-legacy) by doing the following:
 
 1. run `npm i --save-dev babel-plugin-transform-decorators-legacy`
 2. Add the following line to your `.babelrc`:

docs/api/compose.md

@@ -48,7 +48,7 @@ Middleware that handles configuration (placed in redux's
         profileParamsToPopulate config. (default: `true`)
     -   `config.setProfilePopulateResults` **[Boolean](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Boolean)** Whether or not to
         call SET actions for data that results from populating profile to redux under
-        the data path. For example: role paramter on profile populated from 'roles'
+        the data path. For example role parameter on profile populated from 'roles'
         root. True will call SET_PROFILE as well as a SET action with the role that
         is loaded (places it in data/roles). (default: `false`)
 

docs/api/constants.md

@@ -71,7 +71,7 @@ Default configuration options
     profileParamsToPopulate config.
 -   `setProfilePopulateResults` **[Boolean](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Boolean)** `true` Whether or not to
     call SET actions for data that results from populating profile to redux under
-    the data path. For example: role paramter on profile populated from 'roles'
+    the data path. For example role parameter on profile populated from 'roles'
     root. True will call SET_PROFILE as well as a SET action with the role that
     is loaded (places it in data/roles).
 -   `distpatchOnUnsetListener` **[Boolean](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Boolean)** `false` Whether or not to

docs/api/helpers.md

@@ -17,7 +17,7 @@ Detect whether items are loaded yet or not
 
 **Parameters**
 
--   `item` **[Object](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object)** Item to check loaded status of. A comma seperated list is also acceptable.
+-   `item` **[Object](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object)** Item to check loaded status of. A comma separated list is also acceptable.
 
 **Examples**
 
@@ -122,7 +122,7 @@ Returns **[Object](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refer
 ## orderedToJS
 
 Convert parameter under "ordered" path of Immutable Map to a
-Javascript array. This preserves order set by query.
+Javascript array. This preserves order set by a query.
 
 **Parameters**
 

docs/api/props-firebase.md

@@ -124,7 +124,7 @@ Returns **[Promise](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe
 ## uniqueSet
 
 Sets data to Firebase only if the path does not already
-exist, otherwise it rejects.
+exist. Otherwise, it rejects.
 
 **Parameters**
 

docs/recipes/epics.md

@@ -2,7 +2,7 @@
 Epics are particularly useful for responding to actions (often described as a "sidecar").
 
 ## Setup
-Examples below assume that you have setup `redux-observable` middleware so that firebase is available within your epics. Here is an example `combineEpics` function that adds `getFirebase` as third argument along with an epic that uses it:
+Examples below assume that you have setup `redux-observable` middleware so that firebase is available within your epics. Here is an example `combineEpics` function that adds `getFirebase` as the third argument along with an epic that uses it:
 
 ```javascript
 import { getFirebase } from 'react-redux-firebase'
@@ -20,7 +20,7 @@ const somethingEpic = (action$, store, getFirebase) =>
 ```
 
 ### Debounced Notifications
-Debounce writing to a ref on Firebase such as `/notifications` (useful so that tons of similar notifications aren't created).
+Debounce is writing to a ref on Firebase such as `/notifications` (useful so that tons of similar notifications aren't created).
 
 ```js
 const SEND_NOTIFICATION = 'SEND_NOTIFICATION';

docs/recipes/profile.md

@@ -35,7 +35,7 @@ connect(({ firebase }) => ({
 
 **NOTE:** This feature is only available in [`v1.5.*`](http://docs.react-redux-firebase.com/history/v1.5.0/docs/recipes/profile.html)
 
-The current users profile can be updated by using the `updateProfile` method, which is [only available in `v1.5.*`](http://docs.react-redux-firebase.com/history/v1.5.0/docs/recipes/profile.html).
+Profile of the current user can be updated by using the `updateProfile` method, which is [only available in `v1.5.*`](http://docs.react-redux-firebase.com/history/v1.5.0/docs/recipes/profile.html).
 
 ## Change How Profiles Are Stored
 The way user profiles are written to the database can be modified by passing the `profileFactory` parameter.
@@ -60,7 +60,7 @@ const config = {
 To list online users and/or track sessions, view the [presence recipe](http://docs.react-redux-firebase.com/history/v2.0.0/docs/recipes/auth.html#list-of-online-users-presence)
 
 ## Populate Parameters
-If profile object contains an key or a list of keys as parameters, you can populate those parameters with the matching value from another location on firebase.
+If profile object contains a key or a list of keys as parameters, you can populate those parameters with the matching value from another location on firebase.
 
 #### List
 profile.contacts contains a list of user UIDs that should be populated from the users list like so:

docs/recipes/roles.md

@@ -6,13 +6,13 @@ Though there are many patterns, we are going to use the following terminology:
 
 **Role** - job function or title which defines authority level (i.e. admin or manager). A user has a role, a role as permissions.
 
-**Permissions** - approval of a mode of access (i.e. todos) . Multiple permissions can assigned to a single role.
+**Permissions** - approval of a mode of access (i.e. todos) . Multiple permissions can be assigned to a single role.
 
 ## Data Setup
 
 Add the Roles collection in Firebase. It should be a sibling of the `users` collection. For example:
 
-_Tip: you can import below JSON directly into Firebase. Alternatively you can populate it in the start of your application or when you deploy to Firebase._
+_Tip: you can import below JSON directly into Firebase. Alternatively, you can populate it in the start of your application or when you deploy to Firebase._
 
 ```js
 {
@@ -48,7 +48,7 @@ Each user should have a role parameter that correlates to a role. For example:
 
 ## Config
 
-In order for us to check our role for permissions, we will want to populate the role on profile. This will turn the role string (i.e. admin) into the object representing that role from the roles collection.
+In order for us to check our role for permissions, we will want to populate the role on a profile. This will turn the role string (i.e. admin) into the object representing that role from the roles collection.
 
 Make sure you have the following config when creating your store:
 
@@ -78,7 +78,7 @@ reactReduxFirebase(
 )
 ```
 
-**Note:** beware that the `role` parameter on each user will remain a string, and won't actually be "converted" into a object. Something that may be apparant to some developers, but not to others ;-)
+**Note:** beware that the `role` parameter on each user will remain a string, and won't be "converted" into an object. Something that may be apparent to some developers, but not to others ;-)
 
 ## Automatically assign role when user signs up
 

docs/recipes/routing.md

@@ -1,6 +1,6 @@
 # Routing Recipes
 
-These recipes assume that you are using [`react-router`](https://github.com/ReactTraining/react-router), but the principles should be applicable to any routing solution.
+These recipes assume that you are using [`react-router`](https://github.com/ReactTraining/react-router), but the principles should apply to any routing solution.
 
 #### React Router 4
 
@@ -10,7 +10,7 @@ Progress on supporting react-router 4 [is tracked within this issue](https://git
 
 ## Basic
 
-Routing can be changed based on data by using react lifecycle hooks such as `componentWillMount`, and `componentWillReceiveProps` to route users. This can be particularly useful when doing things such as route protection (only allowing user to view a route if they are logged in):
+Routing can be changed based on data by using react lifecycle hooks such as `componentWillMount`, and `componentWillReceiveProps` to route users. This can be particularly useful when doing things such as route protection (only allowing a user to view a route if they are logged in):
 
 ```javascript
 import React, { Component, PropTypes } from 'react'