Fix arrows in Tools index

Author: vojtapol

content/tools/_index.md

@@ -23,6 +23,6 @@ GraphQL Java Tools aims for seamless integration with Java, but works for any JV
 A few libraries exist to ease the boilerplate pain, including [GraphQL-Java's built-in schema-first wiring](http://graphql-java.readthedocs.io/en/latest/schema.html), but none (so far) do type and datafetcher discovery.
 * **Stateful Data Fetchers**: If you're using an IOC container (like Spring), it's hard to wire up datafetchers that make use of beans you've already defined without a bunch of fragile configuration. GraphQL Java Tools allows you to register "Resolvers" for any type that can bring state along and use that to resolve fields.
 * **Generated DataFetchers**: GraphQL Java Tools automatically creates data fetchers for your fields that call the appropriate method on your java class. This means all you have to do to create a new field is add the field definition to your schema and add a corresponding method on your class.
-* **Type->Class Discovery**: GraphQL Java Tools starts from your root objects (Query, Mutation) and, as it's generating data fetchers for you, starts to learn about the classes you use for a certain GraphQL type.
-* **Class Validation**: Since there aren't any compile-time checks of the type->class relationship, GraphQL Java Tools will warn you if you provide classes/types that you don't need to, as well as erroring if you use the wrong Java class for a certain GraphQL type when it builds the schema.
+* **Type → Class Discovery**: GraphQL Java Tools starts from your root objects (Query, Mutation) and, as it's generating data fetchers for you, starts to learn about the classes you use for a certain GraphQL type.
+* **Class Validation**: Since there aren't any compile-time checks of the type → class relationship, GraphQL Java Tools will warn you if you provide classes/types that you don't need to, as well as throwing errors if you use the wrong Java class for a certain GraphQL type when it builds the schema.
 * **Unit Testing**: Since your GraphQL schema is independent of your data model, this makes your classes simple and extremely testable.