Apply suggestions from code review

Co-authored-by: Darrell Warde <8117355+darrellwarde@users.noreply.github.com>
Co-authored-by: Richard Sill <156673635+rsill-neo4j@users.noreply.github.com>

Author: 3 people

modules/ROOT/pages/directives/schema-configuration/field-configuration.adoc

@@ -96,7 +96,7 @@ directive @relationship(
 
 *Configure aggregation*
 
-From the previous type definitions, the type related to `Actor` produced are:
+From the previous type definitions, the types related to `Actor` produced are:
 
 [source, graphql, indent=0]
 ----
@@ -307,9 +307,9 @@ type ActorActedInConnection {
 }
 ----
 
-Note how the `actedInConnection` field is generated but `aggregate` is still present on the `ActorActedInConnection` type, and not affected by the argument `onAggregate`. 
+Note how the `aggregate` field is still present on the `ActorActedInConnection` type, and not affected by the argument `onAggregate`. 
 
-To disable the generation of the `aggregate` field on , see the `aggregate` argument of the directive xref::/schema-configuration/field-configuration.adoc#_relationship[`@relationship`].
+To disable the generation of the `aggregate` field, see the `aggregate` argument of the xref::/schema-configuration/field-configuration.adoc#_relationship[`@relationship` directive].
 
 == `@settable`
 

modules/ROOT/pages/directives/schema-configuration/type-configuration.adoc

@@ -55,7 +55,7 @@ directive @query(read: Boolean! = true, aggregate: Boolean! = false) on OBJECT |
 
 === Usage
 
-.Disable Query _movies_ and _moviesConnection_ edges field
+.Disable query _movies_ and _moviesConnection_ edges field
 [source, graphql, indent=0]
 ----
 type Movie @node @query(read: false, aggregate: true) { 
@@ -139,7 +139,7 @@ type Movie @node @subscription(events: [CREATED]) {
 }
 ----
 
-.Enable subscriptions for all types but disable subscriptions for _Movie_
+.Enable subscriptions for all types except for _Movie_
 [source, graphql, indent=0]
 ----
 type Movie @node @subscription(events: [])  { 

modules/ROOT/pages/types/relationships.adoc

@@ -52,15 +52,16 @@ type Movie @node {
 Note that, in this query:
 
 * A `Person` can _act in_ or _direct_ multiple movies, and a `Movie` can have multiple actors. 
-  While it is rare for a `Movie` to have more than one director, Neo4j GraphQL Library requires all relationships to be modeled as "many" relationships (using Lists).
-* Even conceptually one-to-one relationships like a movie having a single director must be represented as arrays (e.g., `directors: [Person!]!`) because Neo4j cannot reliably enforce 1:1 cardinality between nodes.
+  While it is rare for a `Movie` to have more than one director, the Neo4j GraphQL Library requires all relationships to be modeled as "many" relationships (using lists).
+* Even conceptually one-to-one relationships, such as a movie having a single director, must be represented as arrays (e.g., `directors: [Person!]!`) because Neo4j cannot reliably enforce one-to-one cardinality between nodes.
 * To figure out whether the `direction` argument of the `@relationship` directive should be `IN` or `OUT`, visualize your relationships like in the diagram above, then model out the direction of the arrows.
 * The `@relationship` directive is a reference to Neo4j relationships, whereas in the schema, the phrase `edge(s)` is used to be consistent with the general API language used by Relay.
 
-=== Neo4j GraphQL Cardinality Limitation
+=== Neo4j GraphQL cardinality limitation
 
-It's important to understand that Neo4j cannot reliably enforce 1:1 cardinality between nodes in a graph database. Therefore, all relationships in Neo4j GraphQL are modeled as "many" relationships (using Lists) even when conceptually they represent one-to-one relationships.
-As alternative you can define your relationship with the `@cypher` directive, however some of the functionality provided by the Neo4j GraphQL Library will not be available.
+It's important to understand that Neo4j cannot reliably enforce one-to-one cardinality between nodes in a graph database.
+Therefore, all relationships in Neo4j GraphQL are modeled as "many" relationships (using lists) even if they represent one-to-one relationships conceptually.
+As an alternative you can define your relationship with the `@cypher` directive, however some of the functionality provided by the Neo4j GraphQL Library will not be available.
 
 === Relationship properties
 

modules/ROOT/pages/types/spatial.adoc

@@ -43,7 +43,7 @@ type Point {
 ==== Queries and mutations
 
 Due to the fact that `Point` is an object type, it has an additional type for input in queries and mutations. 
-However, this input types  the same shape as the object type:
+However, these input types have the same shape as the object type:
 
 [source, graphql, indent=0]
 ----