Fix casing of type definitions

Author: mjfwebb

modules/ROOT/pages/aura-graphql/api-creation.adoc

@@ -32,11 +32,11 @@ Even with just field suggestions enabled, it is possible for a malicious actor t
 . Type definitions
 +
 This is where you describe the graph database in the AuraDB that the GraphQL API will be used with.
-The Type Definitions are the same as those used with Neo4j GraphQL Library with the exception that custom resolvers cannot be used.
+The type definitions are the same as those used with Neo4j GraphQL Library with the exception that custom resolvers cannot be used.
 +
-If you already have data in the AuraDB, a quick way to obtain Type Definitions is to use the https://graphql-toolbox.neo4j.io[Neo4j GraphQL Toolbox]. This facility has the ability to connect to an AuraDB, automatically create Type Definitions and allow GraphQL operations.
+If you already have data in the AuraDB, a quick way to obtain type definitions is to use the https://graphql-toolbox.neo4j.io[Neo4j GraphQL Toolbox]. This facility has the ability to connect to an AuraDB, automatically create type definitions and allow GraphQL operations.
 +
-Alternatively you can write your own Type Definition from first principles by following the guidance provided in xref:index.adoc[Neo4j GraphQL Library] documention
+Alternatively you can write your own type definitions from first principles by following the guidance provided in xref:index.adoc[Neo4j GraphQL Library] documention
 +
 If you are using GraphQL Federation then make sure to select **Enable GraphQL subgraph**.
 +