README.md in rspec-graphql_matchers-0.4.0 vs README.md in rspec-graphql_matchers-0.5

@@ -9,13 +9,16 @@
 ```
 
 ## Usage
 
 The matchers currently supported are:
-   - `expect(graphql_type).to have_a_field(field_name).that_returns(valid_type)`
-   - `expect(graphql_field).to be_of_type(valid_type)`
-   - `expect(graphql_field).to accept_arguments(hash_of_arg_names_and_valid_types)`
+   - `expect(a_graphql_object).to have_a_field(field_name).that_returns(valid_type)`
+   - `expect(a_mutation_type).to have_a_return_field(field_name).returning(valid_type)`
+   - `expect(a_mutation_type).to have_an_input_field(field_name).of_type(valid_type)`
+   - `expect(a_field).to be_of_type(valid_type)`
+   - `expect(an_input).to accept_arguments(hash_of_arg_names_and_valid_types)`
+   - `expect(an_input).to accept_arguments(hash_of_arg_names_and_valid_types)`
 
 Where a valid type for the expectation is either:
    - A `GraphQL::ObjectType` object (ex: `types.String`, `!types.Int`, `types[types.Int]`, or your own)
    - A String representation of a type: `"String!"`, `"Int!"`, `"[String]!"`
    (note the exclamation mark at the end, as required by the [GraphQL specs](http://graphql.org/).
@@ -135,11 +138,9 @@
 For better fluency, `accept_arguments` is also available in singular form, as
 `accept_argument`.
 
 ## TODO
 
-  - Setup CI and integrate w/codeclimate
-  - Setup codeclimate / CI badges
   - New matchers!
 
 ## Contributing
 
   - Send Bug reports, suggestions or any general