Merge pull request apollographql#160 from apollographql/lorensr-patch-1

Prosper Otemuyiwa · web-flow · commit 9d3eb4976107 · 2018-06-01T06:58:02.000+01:00
Fix typo in access-control.md
diff --git a/docs/source/guides/access-control.md b/docs/source/guides/access-control.md
@@ -101,7 +101,7 @@ This example is a field in our schema named `users` that returns a list of users
 
 One choice to make when building out our resolvers is what an unauthorized field should return. In some use cases, returning `null` here is perfectly valid. Alternatives to this would be to return an empty array, `[]` or to throw an error, telling the client that they’re not allowed to access that field. For the sake of simplicity, we just returned `[]` in this example.
 
-Now let’s expand that example a little further, and only allow users with an `admin` role to look at our user list. After all, we probably don’t just anyone to have access to all our users.
+Now let’s expand that example a little further, and only allow users with an `admin` role to look at our user list. After all, we probably don’t want just anyone to have access to all our users.
 
 ```js
 users: (root, args, context) => {
@@ -225,4 +225,4 @@ export const generateUserModel = ({ req }) => ({
 });
 ```
 
-If your REST endpoint is already backed by some form of authorization, this cuts down a lot of the logic that needs to get built in the GraphQL layer. This can be a great option when building a GraphQL API over an existing REST API that has everything you need already built in.
+If your REST endpoint is already backed by some form of authorization, this cuts down a lot of the logic that needs to get built in the GraphQL layer. This can be a great option when building a GraphQL API over an existing REST API that has everything you need already built in.
