Merge pull request #38 from simenbrekken/patch-1

Correct a few typos and grammatical issues.

Author: leebyron

Section 2 -- Language.md

@@ -278,7 +278,7 @@ query getZuckProfile($devicePicSize: Int) {
 
 Values for those variables are provided along with a GraphQL query, so they may be
 substituted during execution. If providing JSON for the variables values, we
-could run this query and request profilePic of size 60 with:
+could run this query and request profilePic of size 60 width:
 
 ```js
 {
@@ -418,7 +418,7 @@ will be present and `friends` will not.
 Query variables can be used within fragments. Query variables have global scope
 with a given operation, so a variable used within a fragment must be declared
 in any top-level operation that transitively consumes that fragment. If
-variable is referenced in a fragment and is included by an operation that does
+a variable is referenced in a fragment and is included by an operation that does
 not define that variable, the operation cannot be executed.
 
 ### Inline fragments

Section 5 -- Validation.md

@@ -5,7 +5,7 @@ GraphQL does not just verify if a request is syntactically correct.
 Prior to execution, it can also verify that a request is valid
 within the context of a given GraphQL schema. Validation is primarily
 targeted at development-time tooling. Any client-side tooling
-should returns errors and not allow the formulation of queries
+should return errors and not allow the formulation of queries
 known to violate the type system at a given point in time.
 
 Total request validation on the server-side during execution is optional. As