Merge pull request #169 from neo4j/nitpicking

Fix xrefs throughout the docs

Author: rsill-neo4j

modules/ROOT/pages/directives/autogeneration.adoc

@@ -15,7 +15,7 @@ This enables autogeneration of IDs for the field.
 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.
+It is recommended to use xref::/directives/indexes-and-constraints.adoc#_unique_node_property_constraints[`@unique`] in conjunction with this to add a unique node property constraint.
 
 === Definition
 

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

@@ -300,7 +300,6 @@ type Movie {
 }
 ----
 
-[[type-definitions-default-values-limit]]
 == `@limit`
 
 Available on nodes, this directive injects values into a query such as the `limit`.

modules/ROOT/pages/directives/index.adoc

@@ -14,7 +14,7 @@ The Neo4j GraphQL Library provides the following directives to be used whilst de
 | xref::/directives/database-mapping.adoc#_relationship[`@relationship`]
 | Configures xref::/types/relationships.adoc[relationships] between object types.
 
-| xref::/directives/database-mapping.adoc#_relationship_properties[`@relationshipProperties`]
+| xref::/directives/database-mapping.adoc#_relationshipproperties[`@relationshipProperties`]
 a| Required to differentiate interfaces that are used for relationship properties, and otherwise.
 
 | xref::/directives/database-mapping.adoc#type-definitions-node[`@node`]

modules/ROOT/pages/index.adoc

@@ -26,7 +26,7 @@ For every query and mutation that is executed against this generated schema, the
 - Automatic generation of xref::queries-aggregations/queries.adoc[Queries] and xref::mutations/index.adoc[Mutations] for CRUD interactions.
 - xref::/types/index.adoc[Types], including temporal and spatial.
 - Support for both node and relationship properties.
-- Extensibility through the xref::/directives/custom-logic.adoc#_cypher[`@cypher` directive] and/or xref::/directives/custom-logic.adoc#_custom-resolvers[Custom Resolvers].
+- Extensibility through the xref::/directives/custom-logic.adoc#_cypher[`@cypher` directive] and/or xref::/directives/custom-logic.adoc#_customresolver[Custom Resolvers].
 - Extensive xref::queries-aggregations/filtering.adoc[Filtering] and xref::queries-aggregations/sorting.adoc[Sorting] options.
 - Options for xref::/directives/database-mapping.adoc[Database mapping] and value xref::/directives/autogeneration.adoc[Autogeneration].
 - xref::/queries-aggregations/pagination/index.adoc[Pagination] options.

modules/ROOT/pages/ogm/reference.adoc

@@ -190,7 +190,7 @@ Accepts the argument:
 [[ogm-api-reference-model-aggregate]]
 === `aggregate`
 
-This method can be used to aggregate nodes, and maps to the underlying schema xref::queries-aggregations/queries.adoc#queries-aggregate[Aggregate].
+This method can be used to aggregate nodes, and maps to the underlying schema xref::queries-aggregations/aggregations.adoc#_aggregate_related_nodes[Aggregate].
 
 ==== Arguments
 

modules/ROOT/pages/ogm/subscriptions.adoc

@@ -54,7 +54,7 @@ await ogm.init();
 
 === Adding a custom resolver
 
-xref:custom-resolvers/[Custom resolvers] can be used for multiple reasons such as performing data manipulation and checks, or interact with third party systems. 
+Custom resolvers can be used for multiple reasons such as performing data manipulation and checks, or interact with third party systems. 
 In this case, you only need to create a `User` node with the `password` field set.
 You can do that by adding a sign-up mutation:
 

modules/ROOT/pages/queries-aggregations/filtering.adoc

@@ -8,7 +8,7 @@ When querying for data, a number of operators are available for different types
 == Equality operators
 
 All types can be tested for either equality.
-For non-equality, you *must* use the xref:/queries-aggregations/filtering.adoc#_combining_operators[`NOT`] logical operator.
+For non-equality, you *must* use the xref:/queries-aggregations/filtering.adoc#_logical_operators[`NOT`] logical operator.
 For example:
 
 .Filtering all users named John
@@ -50,7 +50,7 @@ query {
 ----
 
 Spatial types use numerical filtering differently and they also have additional options. 
-See xref:filtering.adoc#_spatial_types[Spatial types] for more information.
+See xref:filtering.adoc#_filtering_spatial_types[Filtering spatial types] for more information.
 
 == Logical operators
 

modules/ROOT/pages/subscriptions/events.adoc

@@ -51,7 +51,6 @@ subscription {
 }
 ----
 
-[[update]]
 == `UPDATE`
 
 Subscriptions to `UPDATE` events listen *only* to node properties changes, not updates to other fields.
@@ -161,7 +160,7 @@ Only top-level properties, without relationships, are available and they are the
 [NOTE]
 ====
 Irrespective of the relationship direction in the database, the `CREATE_RELATIONSHIP` event is bound to the type targeted for the subscription.
-Consequently, if types A and B have xref:subscriptions/events.adoc#create-non-reciprocal-relationships[non-reciprocal relationships] and a GraphQL operation creates a relationship between them (despite being already previously connected in the database), the `CREATE_RELATIONSHIP` event should only return the subscription to the type A.
+Consequently, if types A and B have xref:subscriptions/events.adoc#_non_reciprocal_relationships[non-reciprocal relationships] and a GraphQL operation creates a relationship between them (despite being already previously connected in the database), the `CREATE_RELATIONSHIP` event should only return the subscription to the type A.
 ====
 
 As an example, consider the following type definitions:

modules/ROOT/pages/troubleshooting.adoc

@@ -137,8 +137,6 @@ RETURN m
 
 If you use a causal cluster or an Aura Professional instance, there is a chance that the created data is not yet present on the server which gets connected to on the next GraphQL query.
 
-You can ensure that the data is available to query by passing a bookmark into your request - see xref::driver-configuration.adoc#driver-configuration-bookmarks[Specifying Neo4j Bookmarks] for more information.
-
 === What is `_emptyInput` in my update and create inputs?
 
 `_emptyInput` will appear in your update and create inputs if you define a type with only auto-generated and/or relationship properties. It is a placeholder property and therefore giving it a value in neither update nor create will give it a value on the node. `_emptyInput` will be removed if you add a user-provided property.

modules/ROOT/pages/types/scalar.adoc

@@ -24,7 +24,7 @@ type Person {
 
 .2+| `BigInt`
 | Supports up to 64 bit integers, serialized as strings in variables and in data responses. 
-Shares the same xref::queries-aggregations/filtering.adoc#filtering-numerical-operators[Numerical operators] as the other numeric types.
+Shares the same xref::queries-aggregations/filtering.adoc#_numerical_operators[Numerical operators] as the other numeric types.
 a| 
 [source, graphql, indent=0]
 ----