anchor.diff:  }
   ----
   
  -By using this mutation we have created a hero entity in our service.
  +By using this mutation we have created a `Hero` entity in our service.
   
   Notice how in the response we have retrieved the `name` and `surname`
   of the created Hero. This is because we selected to retrieve
   these fields in the response within the `{ }` in the mutation query.
   This can easily be a server side generated field that the client may require.
   
  -Lets now try deleting an entry
  +Let's now try deleting an entry:
   
   ----
   mutation DeleteHero {
  
positive.code: <3> Documentation of the queryable method
  
  TIP:  The value of the `@Query` annotation is optional and would implicitly
  be defaulted to the method name if excluded.
  
  This way we have created our first queryable API which we will later expand.
  
  
negative.code: 
  == Conclusion
  
  MicroProfile GraphQL enables clients to retrieve the exact data that is
  required preventing `Over-fetching` and `Under-fetching`.
  
  The GraphQL API can be expanded without breaking previous queries enabling easy
  API `evolution`.
  
  [[configuration-reference]]
  == Configuration Reference
  
  include::{generated-dir}/config/quarkus-smallrye-graphql.adoc[leveloffset=+1, opts=optional]
  