Apply suggestions from code review

Co-authored-by: Lidia Zuin <[email protected]>

Author: rsill-neo4j

modules/ROOT/pages/type-definitions/directives/custom-logic.adoc

@@ -9,14 +9,14 @@ This directive can be used both for properties in a type or as top level queries
 
 === Global variables
 
-Global variables are available for use within the Cypher statement and can be applied to the `@cypher` directive.
+Global variables are available for use within the Cypher statement, and can be applied to the `@cypher` directive.
 
 [cols="1,2,2"]
 |===
 | Variable | Description | Example
 
 | `this`
-| This value is a reference to the currently resolved node, and it can be used to traverse the graph.
+| Refers to the currently resolved node, and can be used to traverse the graph.
 a| 
 [source, graphql, indent=0]
 ----
@@ -99,7 +99,7 @@ type Query {
 The return value of Cypher statements must always be of the same type to which the directive is applied.
 
 The variable must also be aliased with a name that is the same as the one passed to `columnName`.
-This can be the name of a node, relationship query or an alias in the `RETURN` statement of the Cypher statement.
+This can be the name of a node, relationship query, or an alias in the `RETURN` statement of the Cypher statement.
 
 ==== Scalar values
 
@@ -158,7 +158,8 @@ The downside of the latter approach is that you need to adjust the return object
 
 === Input arguments
 
-The `@cypher` statement can access the query parameters by prepending `$` to the parameter name. For example:
+The `@cypher` statement can access the query parameters by prepending `$` to the parameter name. 
+For example:
 
 [source, graphql, indent=0]
 ----
@@ -184,7 +185,7 @@ The `@cypher` directive can be used in different contexts, such as the ones desc
 [[type-definitions-cypher-object-usage]]
 ==== On an object type field
 
-In the example below, a field `similarMovies` is bound to the `Movie` type, to find other movies with an overlap of actors:
+In the following example, the field `similarMovies` is bound to the `Movie` type for finding other movies with an overlap of actors:
 
 [source, graphql, indent=0]
 ----
@@ -265,7 +266,8 @@ type Mutation {
 When translating from GraphQL to Cypher, any instances of fields to which this directive is applied will be wrapped in a `coalesce()` function in the WHERE clause (see https://neo4j.com/developer/kb/understanding-non-existent-properties-and-null-values/#_use_coalesce_to_use_a_default_for_a_null_value).
 
 This directive helps querying against non-existent properties in a database. 
-However, it is encouraged to populate these properties with meaningful values if this is becoming the norm. The `@coalesce`directive is a primitive implementation of the function which only takes a static default value as opposed to using another property in a node or a Cypher expression.
+However, it is encouraged to populate these properties with meaningful values if it becomes the norm. 
+The `@coalesce`directive is a primitive implementation of the function which only takes a static default value as opposed to using another property in a node or a Cypher expression.
 
 === Definition
 
@@ -337,9 +339,8 @@ If no `default` value is set, `max` is used for queries without limit.
 
 The Neo4j GraphQL Library generates query and mutation resolvers, so you don't need to implement them yourself.
 However, if you need additional behaviors besides the autogenerated CRUD operations, you can specify custom resolvers for these scenarios.
-This page describes how to set them up.
 
-To add a field to an object type which is resolved from existing values in the type, rather than storing new values, you should mark it with the `@customResolver` directive and define a custom resolver for it.
+To add a field to an object type which is resolved from existing values in the type, rather than storing new values, you should mark it with the `@customResolver` directive, and define a custom resolver for it.
 
 Take, for instance, this schema:
 
@@ -386,11 +387,11 @@ directive @customResolver(
 
 === The `requires` argument
 
-This is how the `requires` argument can be used on your schema:
+The `requires` argument can be used:
 
-* Accepts a selection set string.
-* Can be used in any field, as long as it is not another `@customResolver` field.
-* Should be used in case the custom resolver depends on any fields.
+* For a selection set string.
+* In any field, as long as it is not another `@customResolver` field.
+* In case the custom resolver depends on any fields.
 This ensures that, during the Cypher generation process, these properties are selected from the database.
 
 Using a selection set string makes it possible to select fields from related types, as shown in the following example:
@@ -428,7 +429,7 @@ const neoSchema = new Neo4jGraphQL({
 });
 ----
 
-Here the `firstName`, `lastName`, `address.street`, and `address.city` fields are always selected from the database if the `fullName` field is selected and is available to the custom resolver.
+Here the `firstName`, `lastName`, `address.street`, and `address.city` fields are always selected from the database if the `fullName` field is selected, and is available to the custom resolver.
 
 It is also possible to inline fragments to conditionally select fields from interface/union types:
 
@@ -461,7 +462,7 @@ type Journal implements Publication {
 ----
 
 However, it is **not** possible to require extra fields generated by the library such as aggregations and connections.
-For example, the type definitions below would throw an error as they attempt to require the `publicationsAggregate`:
+For example, the following type definitions would throw an error since they attempt to require the `publicationsAggregate`:
 
 [source, graphql, indent=0]
 ----
@@ -495,7 +496,7 @@ type Journal implements Publication {
 
 == `@populatedBy`
 
-This directive is used to specify a callback function that gets executed during GraphQL query parsing,
+This directive is used to specify a callback function, which is executed during GraphQL query parsing,
 to populate fields which have not been provided within the input.
 
 For non-required values, callbacks may return `undefined` (meaning that nothing is changed or added to the property) or `null` (meaning that the property will be removed).
@@ -566,7 +567,7 @@ type Record {
 }
 ----
 
-If the username is located in `context.username`, you could define a callback such as:
+And if the username is located in `context.username`, you could define a callback such as:
 
 [source, javascript, indent=0]
 ----