Fix typos

CHANGELOG.md

@@ -64,7 +64,7 @@ Nothing here yet
 
 ## [0.15.0] 2018-12-02 Hex.pm release
 
-### Compatiblity
+### Compatibility
 
 * The default errors use `code` in its errors: `#{ path => .., message
   => .., extensions => #{ code => .. }}`, which follows the
@@ -338,7 +338,7 @@ is a smaller one:
 * Feature: Support 3-tuple responses in GraphQL resolvers. Tuples of the form
   `{ok, Result, [Terms]}` are now allowed, and the given Terms will
   be collected in the final response in an unspecified order. This
-  allows resolvers to send back auxilliary data through the graph
+  allows resolvers to send back auxiliary data through the graph
   system and handle these at the top level later on. This
   functionality is currently *experimental* until we figure out if
   there is a simpler solution to the problem of getting side-channel

README.md

@@ -403,7 +403,7 @@ run(Doc, OpName, Vars, Req, State) ->
 
 In this GraphQL implementation, the default value for keys are type
 `binary()`. This choice is deliberate, since it makes the code more
-resistent to `atom()` overflow and also avoids some conversions
+resistant to `atom()` overflow and also avoids some conversions
 between `binary()` and `atom()` values in the system. A later version
 of the library might redesign this aspect, but we are somewhat stuck
 with it for now.

src/graphql_builtins.erl

@@ -38,7 +38,7 @@ standard_directives_inject() ->
         args => #{ <<"if">> => #{
             type => 'Bool',
             default => false,
-            description => <<"Wether or not the item should be skipped">> }}
+            description => <<"Whether or not the item should be skipped">> }}
         }},
     IncludeDirective = {directive, #{
         id => <<"include">>,
@@ -48,7 +48,7 @@ standard_directives_inject() ->
         args => #{ <<"if">> => #{
             type => 'Bool',
             default => false,
-            description => <<"Wether or not the item should be included">> }}
+            description => <<"Whether or not the item should be included">> }}
         }},
     DeprecatedDirective = {directive, #{
         id => <<"deprecated">>,

src/graphql_err.erl

@@ -256,7 +256,7 @@ type_check_err_msg({excess_args, Args}) ->
     io_lib:format("The argument list contains unknown arguments ~p", [Args]);
 type_check_err_msg({type_mismatch, #{ document := Doc, schema := Sch }}) ->
     ["Type mismatch. The query document has a value/variable of type (",
-     graphql_err:format_ty(Doc), ") but the schema expectes type (", graphql_err:format_ty(Sch), ")"];
+     graphql_err:format_ty(Doc), ") but the schema expects type (", graphql_err:format_ty(Sch), ")"];
 type_check_err_msg({type_mismatch, #{ id := ID, document := Doc, schema := Sch }}) ->
     ["Type mismatch on (", ID, "). The query document has a value/variable of type (",
       graphql_err:format_ty(Doc), ") but the schema expects type (", graphql_err:format_ty(Sch), ")"];
@@ -296,7 +296,7 @@ type_check_err_msg({not_union_member, SpreadTy, UnionTy}) ->
 type_check_err_msg({not_interface_embedder, SpreadTy, ScopeTy}) ->
     io_lib:format(
       "The spread type ~ts is an interface. "
-      "Yet the scope type ~ts does not impelement this interface.",
+      "Yet the scope type ~ts does not implement this interface.",
       [SpreadTy, ScopeTy]);
 type_check_err_msg({not_union_embedder, SpreadTy, ScopeTy}) ->
     io_lib:format(

src/graphql_scalar_binary_coerce.erl

@@ -5,7 +5,7 @@
 input(_, X) -> {ok, X}.
 
 %% According to the specification, Jun2018, we should
-%% accept coercion as long as we are not "loosing information"
+%% accept coercion as long as we are not "losing information"
 %% in the process
 output(_,B) when is_binary(B) ->
     %% Standard case where the code provided a String value

test/dungeon_mutation.erl

@@ -45,7 +45,7 @@ execute(_Ctx, _, <<"introduceItem">>, #{ <<"input">> := Input }) ->
     #{ <<"clientMutationId">> := MID,
        <<"name">> := N,
        <<"description">> := D,
-       <<"weigth">> := W } = Input,
+       <<"weight">> := W } = Input,
     {atomic, Item} = dungeon:insert(
                        #item { name = N,
                                description = D,

test/schema_star_wars.erl

@@ -38,7 +38,7 @@ inject() ->
 
     Root = {root, #{
               query => 'Query',
-              interaces => []
+              interfaces => []
              }},
     ok = graphql:insert_schema_definition(Root),
     ok.