README.md in graphiti_graphql-0.1.2 vs README.md in graphiti_graphql-0.1.3

@@ -2,16 +2,18 @@
 
 GraphQL (and Apollo Federation) support for Graphiti. Serve traditional Rails JSON, JSON:API or GraphQL with the same codebase.
 
 Currently read-only, but you can add your own Mutations [manually](#blending-with-graphql-ruby).
 
+Pre-alpha. Stay tuned.
+
 ## Setup
 
 Add to your `Gemfile`:
 
 ```rb
-gem 'graphiti', ">= 1.2.32"
+gem 'graphiti', ">= 1.2.33"
 gem "graphiti_graphql"
 ```
 
 Mount the engine:
 
@@ -57,10 +59,10 @@
 ```ruby
 # config/initializers/graphiti.rb
 GraphitiGraphQL.schema_class = MySchema
 ```
 
-Any pre-existing GraphQL endpoint will continue working as normal. But the GQL endpoint you mounted in `config/routes.rb` will now serve BOTH your low-level `graphql-ruby` schema AND your Graphiti-specific schema. Note these cannot (currently) be served side-by-side on under `query` within the *same request*.
+Any pre-existing GraphQL endpoint will continue working as normal. But the GQL endpoint you mounted in `config/routes.rb` will now serve BOTH your low-level `graphql-ruby` schema AND your Graphiti-specific schema. Note these cannot (currently) be served side-by-side under `query` within the *same request*.
 
 By default the GraphQL context will be `Graphiti.context[:object]`, which is the controller being called. You might want to customize this so your existing graphql-ruby code continues to expect the same context:
 
 ```ruby
 GraphitiGraphQL.define_context do |controller|