Merge pull request #1136 from szepeviktor/fix-typos

Fix typos

Author: mcg-web

UPGRADE.md

@@ -1,7 +1,7 @@
 UPGRADE FROM 0.14 to 1.0
 =========================
 
-* Removed `use_experimental_executor` configuraton option.
+* Removed `use_experimental_executor` configuration option.
 * Signature of TypeInterface changed from `string $name = null, string $resolveType` to `string $resolveType, ?string $name = null`
 * Removed deprecated `targetType` from `Query`
 * Removed deprecated `fieldBuilder` from `Field`

docs/annotations/annotations-reference.md

@@ -241,7 +241,7 @@ Optional attributes:
 Deprecated attributes:
 - **values** : An array of `@EnumValue`to define description or deprecated reason of enum values
 
-The class will also be used by the `Arguments Transformer` service when an `Enum` is encoutered in a Mutation or Query Input. A property accessor will try to populate a property name `value`.
+The class will also be used by the `Arguments Transformer` service when an `Enum` is encountered in a Mutation or Query Input. A property accessor will try to populate a property name `value`.
 
 Example:
 
@@ -266,7 +266,7 @@ class Planet
 ```
 
 In the example above, if a query or mutation has this Enum as an argument, the value will be an instance of the class with the enum value as the `value` property. (see [The Arguments Transformer documentation](arguments-transformer.md)). 
-As the class can be instanciated from the `Arguments Transformer` service, it cannot have a constructor with required arguments.
+As the class can be instantiated from the `Arguments Transformer` service, it cannot have a constructor with required arguments.
 
 ## @EnumValue
 
@@ -427,7 +427,7 @@ The corresponding class will also be used by the `Arguments Transformer` service
 
 ## @IsPublic
 
-Added on a _class_ in conjunction with `@Type` or `@TypeInterface`, this annotation will define the defaut to set if fields are public or not.
+Added on a _class_ in conjunction with `@Type` or `@TypeInterface`, this annotation will define the default to set if fields are public or not.
 Added on a _property_ or _method_ in conjunction with `@Field`, it'll define an expression to set if the field is public or not.
 
 Example:
@@ -646,7 +646,7 @@ This annotation is used on a _class_ to define an union.
 
 Required attributes:
 
-- **types** : An array of GraphQL Type as string (can be auto-guessed. See union documenation).
+- **types** : An array of GraphQL Type as string (can be auto-guessed. See union documentation).
 
 Optional attributes:
 

docs/annotations/arguments-transformer.md

@@ -1,8 +1,8 @@
 # The Arguments Transformer service
 
 When using annotation, as we use classes to describe our GraphQL objects, it is also possible to create and populate classes instances using GraphQL data. 
-If a class is used to describe a GraphQL Input, this same class can be instanciated to hold the corresponding GraphQL Input data. 
-This is where the `Arguments Transformer` comes into play. Knowing the matching between GraphQL types and PHP classes, the service is able to instanciate a PHP classes and populate it with data based on the corresponding GraphQL type.
+If a class is used to describe a GraphQL Input, this same class can be instantiated to hold the corresponding GraphQL Input data. 
+This is where the `Arguments Transformer` comes into play. Knowing the matching between GraphQL types and PHP classes, the service is able to instantiate a PHP classes and populate it with data based on the corresponding GraphQL type.
 To invoke the Arguments Transformer, we use the `input` expression function in our resolvers. 
 
 ## the `arguments` function in expression language

docs/annotations/index.md

@@ -155,7 +155,7 @@ class RootQuery {
 }
 ```
 
-In order for this to work, the `RootQuery` class must be instanciated at some point if you want to be able to call methods on it. 
+In order for this to work, the `RootQuery` class must be instantiated at some point if you want to be able to call methods on it. 
 To do so, the `RootQuery` class must be defined as a service with its FQCN as id. 
 In the previous example, we need a service name `App\GraphQL\Query\RootQuery`. It works the same way for mutations.
 In the previous example, the generated `resolve` config of the `something` field will be `@=service('App\GraphQL\Query\RootQuery').getSomething()`.
@@ -195,7 +195,7 @@ class MyType {
 ### @Field type auto-guessing when defined on a property with a type hint
 
 The type of the `@Field` annotation can be auto-guessed if it's defined on a property with a type hint.
-If the property has a usable type hint this is used and no futher guessing is done.
+If the property has a usable type hint this is used and no further guessing is done.
 
 For example:
 

docs/definitions/expression-language.md

@@ -43,7 +43,7 @@ Examples:
 ```yaml
 @=service('my_service').customMethod()
 
-# Using the 'ser' alias
+# Using the 'serv' alias
 @=serv('my_service').customMethod()
 
 # Using the FQCN for the service name (only works for public services).

docs/definitions/relay/builders.md

@@ -19,7 +19,7 @@ FriendsConnection:
  edgeType: FriendsConnectionEdge
 ```
 
-See the class definition for additionnal configuration
+See the class definition for additional configuration
 
 
 ## The Relay Edge Fields Builder
@@ -36,4 +36,4 @@ FriendsConnectionEdge:
  nodeType: Character
 ```
 
-See the class definition for additionnal configuration
+See the class definition for additional configuration

docs/definitions/resolver.md

@@ -15,8 +15,8 @@ Resolvers can be defined in 2 different ways:
 You can declare a resolver (any class that implements `Overblog\GraphQLBundle\Definition\Resolver\QueryInterface` or `Overblog\GraphQLBundle\Definition\Resolver\MutationInterface`) in `src/*Bundle/GraphQL` or `app/GraphQL` and they will be auto discovered.
 Auto map classes method are accessible by:
 * double-colon (::) to separate service id (class name) and the method names
-(example: `AppBunble\GraphQL\CustomResolver::myMethod`)
-* for callable classes you can use the service id (example: `AppBunble\GraphQL\InvokeResolver` for a resolver implementing the `__invoke` method) you can also alias a type by implementing `Overblog\GraphQLBundle\Definition\Resolver\AliasedInterface` which returns a map of method/alias. The service created will autowire the `__construct` and `Symfony\Component\DependencyInjection\ContainerAwareInterface::setContainer` methods.
+(example: `AppBundle\GraphQL\CustomResolver::myMethod`)
+* for callable classes you can use the service id (example: `AppBundle\GraphQL\InvokeResolver` for a resolver implementing the `__invoke` method) you can also alias a type by implementing `Overblog\GraphQLBundle\Definition\Resolver\AliasedInterface` which returns a map of method/alias. The service created will autowire the `__construct` and `Symfony\Component\DependencyInjection\ContainerAwareInterface::setContainer` methods.
 
 **Note:**
 * When using service id as FQCN in yaml or annotation definition, backslashes must be correctly escaped, here an example:

docs/definitions/type-system/index.md

@@ -41,7 +41,7 @@ Types can be define 3 different ways:
  You can also declare PHP types (any subclass of `GraphQL\Type\Definition\Type`) 
  in `src/*Bundle/GraphQL` or `app/GraphQL`
  they will be auto discover (thanks to auto mapping). Auto map classes are accessible by service id
- (example: `AppBunble\GraphQL\Type\DateTimeType`), you can also alias a type by
+ (example: `AppBundle\GraphQL\Type\DateTimeType`), you can also alias a type by
  implementing `Overblog\GraphQLBundle\Definition\Resolver\AliasedInterface`
  that returns an array of aliases.
 

docs/definitions/type-system/interface.md

@@ -132,7 +132,7 @@ RootQuery:
  type: object
  config:
  fields:
- allCaracters:
+ allCharacters:
  type: "[Character]" # interface as the return type
  resolve: "@=res('all_characters')"
 ```

docs/error-handling/index.md

@@ -140,7 +140,7 @@ You can custom the default errors handler using configuration:
 overblog_graphql:
  errors_handler:
  enabled: true # false will totally disabled errors handling
- internal_error_message: 'Internal error occured' # custom generic error message
+ internal_error_message: 'Internal error occurred' # custom generic error message
  rethrow_internal_exceptions: false # re-throw internal exception
  debug: false # will add trace stack and debugMessage to error
  log: true # false will disabled the default logging behavior