Merge pull request #158 from neo4j/minor-adjustments

minor adjustments

Author: rsill-neo4j

modules/ROOT/pages/directives/autogeneration.adoc

@@ -12,7 +12,7 @@ This page describes directives used for autogeneration:
 This directive marks a field as an identifier for an object type.
 This enables autogeneration of IDs for the field.
 
-The format of each generated ID is a UUID generated by https://neo4j.com/docs/cypher-manual/current/functions/scalar/#functions-randomuuid[randomUUID() function].
+The format of each generated ID is a UUID generated by the link:https://neo4j.com/docs/cypher-manual/current/functions/scalar/#functions-randomuuid[`randomUUID()` function].
 The field will not be present in input types for mutations.
 
 It is recommended to use xref::/directives/indexes-and-constraints.adoc#type-definitions-constraints-unique[`@unique`] in conjunction with this to add a unique node property constraint.

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

@@ -268,7 +268,7 @@ For more information, see link:https://neo4j.com/developer/kb/understanding-non-
 
 This directive helps querying against non-existent properties in a database. 
 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.
+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
 

modules/ROOT/pages/directives/index.adoc

@@ -23,8 +23,8 @@ a| Required to differentiate interfaces that are used for relationship propertie
 | xref::/directives/database-mapping.adoc#type-definitions-alias[`@alias`]
 | Maps a GraphQL schema field to a Neo4j property on a node or relationship.
 
-| `@declareRelationship`
-| Configure xref::/types/relationships.adoc[relationships] to be implemented on object types.
+| xref::/types/relationships.adoc#_declarerelationship[`@declareRelationship`]
+| Configure relationships to be implemented on object types.
 
 |===
 

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

@@ -35,7 +35,7 @@ extend schema @query(read: true, aggregate: false)
 
 **Invalid schema usage**
 
-The same schema configuration directive cannot be applied to both Schema and Object.
+The same schema configuration directive cannot be applied to both schema and object.
 Take the following type definitions as example:
 
 [source, graphql, indent=0]

modules/ROOT/pages/types/relationships.adoc

@@ -88,6 +88,8 @@ type ActedIn @relationshipProperties {
 }
 ----
 
+=== `@declareRelationship`
+
 If you need a relationship to be available on interfaces, you need to use the new `@declareRelationship` directive instead, as well as define the relationships in the concrete type:
 
 [source, graphql, indent=0]