Typo fixes in docs

docs/accounts.md

@@ -2,7 +2,7 @@
 
 In Apollo your resolver receives `root`, `args` and `context`. Inside `context` we store the current `userId` and `user`:
 
-The data we fetch for user can be customised via config:
+The data we fetch for user can be customized via config:
 
 ```js
 // file: server/

docs/db.md

@@ -3,7 +3,7 @@
 This package is tailored for Mongo database. If you're looking for a bare-bones API implementation, not coupled to mongo, you can look at: https://github.com/apollographql/meteor-integration
 
 This package depends on [`cultofcoders:grapher`](https://github.com/cult-of-coders/grapher), a very awesome tool,
-which allows you too query related MongoDB objects at serious speeds.
+which allows you to query related MongoDB objects at serious speeds.
 
 The difference is that we will never use the exposure mechanisms from Grapher which are used for Meteor's DDP (Methods & Publications),
 but it's not a problem, we have many other nice things we can use.

docs/meteor-connectivity.md

@@ -211,7 +211,7 @@ With this, once, the websocket connection has been established, it will do a htt
 
 Keep in mind that the user infor you get back is not truly reactive like `Meteor.user()`. This just tells you whether you have a valid login token or not. If you want to have your user information to be reactive, you need to set up a users subscription.
 
-With this, you have achieved some level of the Meteor connectivity reactiviy we have all gotten used to. Hopefully, this was useful!
+With this, you have achieved some level of the Meteor connectivity reactivity we have all gotten used to. Hopefully, this was useful!
 
 ---
 

docs/react-native-client.md

@@ -155,7 +155,7 @@ However, we still need address the second issue where the authorization token is
 wsLink.subscriptionClient.close(false, false);
 ```
 
-This needs to be done at an appropraiate place, such when your client receives a new login token. If you are using [meteor-apollo-accounts](https://github.com/cult-of-coders/meteor-apollo-accounts), then the loginToken change will happen in the `setTokenStore()` implementation:
+This needs to be done at an appropriate place, such when your client receives a new login token. If you are using [meteor-apollo-accounts](https://github.com/cult-of-coders/meteor-apollo-accounts), then the loginToken change will happen in the `setTokenStore()` implementation:
 
 ```js
 import {
@@ -233,7 +233,7 @@ wsLink.subscriptionClient.onReconnected(_connected);
 
 ## Polyfills
 
-On react-native, there are some other quirky issues. The meteor-apollo-accounts makes use of the Symbol type which is not supported on Android. A polyfille is required to handle this:
+On react-native, there are some other quirky issues. The meteor-apollo-accounts makes use of the Symbol type which is not supported on Android. A polyfill is required to handle this:
 
 ```js
 // import this since android needs this to resolve

docs/sample.md

@@ -61,7 +61,7 @@ query {
 }
 ```
 
-Ofcourse, when you're dealing with a big project, your data structure is surely going to change, this is just for demo purposes.
+Of course, when you're dealing with a big project, your data structure is surely going to change, this is just for demo purposes.
 Keep in mind, you can separate queries anyway you want, and `load()` them independently, the `load` function smartly merges types and resolvers and works with arrays and GraphQL modules as well.
 
 [Read more about `graphql-load`](https://www.npmjs.com/package/graphql-load?activeTab=readme)