fix broken anchors

JPryce-Aklundh · JPryce-Aklundh · commit 0038cb3b61a1 · 2025-05-30T15:30:21.000+02:00
diff --git a/modules/ROOT/pages/clauses/call-subquery.adoc b/modules/ROOT/pages/clauses/call-subquery.adoc
@@ -312,7 +312,7 @@ As the size of the CSV file in this example is small, only a single separate tra
 
 [NOTE]
 ====
-`CALL { ... } IN TRANSACTIONS` is only allowed in xref::introduction/index.adoc#explicit-implicit-transactions[implicit transactions].
+`CALL { ... } IN TRANSACTIONS` is only allowed in xref::introduction/cypher-neo4j.adoc#explicit-implicit-transactions[implicit transactions].
 ====
 
 
diff --git a/modules/ROOT/pages/clauses/delete.adoc b/modules/ROOT/pages/clauses/delete.adoc
@@ -125,5 +125,5 @@ Deleted 3 nodes, deleted 1 relationship
 [NOTE]
 ====
 This query is not for deleting large amounts of data, but is useful when experimenting with small example datasets.
-When deleting large amounts of data, instead use xref::clauses/call-subquery.adoc#delete-with-call-in-transactions[CALL { ... } IN TRANSACTIONS].
+When deleting large amounts of data, instead use xref::clauses/call-subquery.adoc#_batching[CALL { ... } IN TRANSACTIONS].
 ====
diff --git a/modules/ROOT/pages/clauses/order-by.adoc b/modules/ROOT/pages/clauses/order-by.adoc
@@ -40,7 +40,6 @@ CREATE
 [NOTE]
 ====
 Strings that contain special characters can have inconsistent or non-deterministic ordering in Neo4j.
-For details, see xref::values-and-types/property-structural-composite.adoc#property-types-sip-note[Sorting of special characters].
 ====
 
 [[order-nodes-by-property]]
diff --git a/modules/ROOT/pages/clauses/transaction-clauses.adoc b/modules/ROOT/pages/clauses/transaction-clauses.adoc
@@ -85,11 +85,11 @@ a|A map containing all the parameters used by the query currently executing in t
 m|MAP
 
 m|planner
-a|The name of the Cypher planner used to plan the query currently executing in this transaction, or an empty string if no query is currently executing. For details, see xref::query-tuning/index.adoc#cypher-planner[Cypher planner].
+a|The name of the Cypher planner used to plan the query currently executing in this transaction, or an empty string if no query is currently executing. For details, see xref:query-tuning/query-options.adoc#cypher-planner[Cypher planner].
 m|STRING
 
 m|runtime
-a|The name of the Cypher runtime used by the query currently executing in this transaction, or an empty string if no query is currently executing. For details, see xref::query-tuning/index.adoc#cypher-runtime[Cypher runtime].
+a|The name of the Cypher runtime used by the query currently executing in this transaction, or an empty string if no query is currently executing. For details, see xref::query-tuning/query-options.adoc#cypher-runtime[Cypher runtime].
 m|STRING
 
 m|indexes
diff --git a/modules/ROOT/pages/execution-plans/operators.adoc b/modules/ROOT/pages/execution-plans/operators.adoc
@@ -8,7 +8,7 @@
 All executin plan operators are listed here, grouped by the similarity of their characteristics.
 --
 
-Certain operators are only used by a subset of the xref::query-tuning/index.adoc#cypher-runtime[runtimes] that Cypher can choose from.
+Certain operators are only used by a subset of the xref::query-tuning/query-options.adoc#cypher-runtime[runtimes] that Cypher can choose from.
 If that is the case, the example queries will be prefixed with an option to choose one of these runtimes.
 
 
diff --git a/modules/ROOT/pages/introduction/cypher-neo4j.adoc b/modules/ROOT/pages/introduction/cypher-neo4j.adoc
@@ -30,12 +30,12 @@ All users have full access rights.
 | Constraints
 a|
 All constraints:
-xref::constraints/examples.adoc#constraints-examples-node-property-existence[node existence constraints],
+xref::constraints/examples.adoc#administration-constraints-create-a-node-property-existence-constraint[node existence constraints],
 xref::constraints/examples.adoc#constraints-examples-relationship-property-existence[relationship existence constraints],
-xref::constraints/examples.adoc#constraints-examples-node-uniqueness[node property uniqueness constraints],
-xref::constraints/examples.adoc#constraints-examples-node-key[node key constraints].
+xref::constraints/examples.adoc#administration-constraints-unique-nodes[node property uniqueness constraints],
+xref::constraints/examples.adoc#administration-constraints-node-key[node key constraints].
 a|
-Only xref::constraints/examples.adoc#constraints-examples-node-uniqueness[node] property uniqueness constraints.
+Only xref::constraints/examples.adoc#administration-constraints-unique-nodes[node] property uniqueness constraints.
 
 |===
 
diff --git a/modules/ROOT/pages/introduction/cypher-overview.adoc b/modules/ROOT/pages/introduction/cypher-overview.adoc
@@ -36,7 +36,7 @@ However, there are some important differences between the two:
 *Cypher is schema-flexible*::
 
 While it is both possible and advised to enforce partial schemas using xref:constraints/index.adoc[indexes and constraints], Cypher and Neo4j offers a greater degree of schema-flexibility than SQL and a relational database.
-More specifically, nodes and relationships in a Neo4j database do not have to have a specific property set to them because other nodes or relationships in the same graph have that property (unless there is an xref:constraints/examples.adoc#constraints-examples-node-property-existence[existence constraint created on that specific property]).
+More specifically, nodes and relationships in a Neo4j database do not have to have a specific property set to them because other nodes or relationships in the same graph have that property (unless there is an xref:constraints/examples.adoc#administration-constraints-create-a-node-property-existence-constraint[existence constraint created on that specific property]).
 This means that users are not required to use a fixed schema to represent data and that they can add new attributes and relationships as their graphs evolve.
 
 *Query order*::
diff --git a/modules/ROOT/pages/query-tuning/query-options.adoc b/modules/ROOT/pages/query-tuning/query-options.adoc
@@ -46,7 +46,7 @@ As this is the default version, it is not necessary to use this option explicitl
 In Neo4j {neo4j-version}, the support for Cypher 3.5 and Cypher 4.3 is provided only at the parser level.
 The consequence is that some underlying features available in Neo4j 3.5 are no longer available and will result in runtime errors.
 
-Please refer to the discussion in xref::deprecations-additions-removals-compatibility.adoc#cypher-compatibility[Cypher Compatibility] for more information on which features are affected.
+Please refer to the discussion in xref::deprecations-additions-removals-compatibility.adoc[] for more information on which features are affected.
 ====
 
 
diff --git a/modules/ROOT/pages/syntax/parameters.adoc b/modules/ROOT/pages/syntax/parameters.adoc
@@ -42,14 +42,6 @@ For example:
 We provide below a comprehensive list of examples of parameter usage.
 In these examples, parameters are given in JSON; the exact manner in which they are to be submitted depends upon the driver being used.
 
-[NOTE]
-====
-The old parameter syntax `+{param}+` was deprecated in Neo4j 3.0 and removed entirely in Neo4j 4.0.
-Using it will result in a syntax error.
-However, it is still possible to use it, with warnings, if you prefix the query with `CYPHER 3.5`.
-See xref::deprecations-additions-removals-compatibility.adoc#cypher-compatibility[Cypher Compatibility] for further information.
-====
-
 
 [[cypher-parameters-auto-parameterization]]
 == Auto-parameterization
diff --git a/modules/ROOT/pages/values-and-types/maps.adoc b/modules/ROOT/pages/values-and-types/maps.adoc
@@ -117,7 +117,7 @@ RETURN keanu{.name, movies: movies}
 |===
 
 The below query finds all `Person` nodes in the graph that have one or more relationships with the type `ACTED_IN` connected to `Movie` nodes. 
-It uses the xref::functions/aggregating.adoc#unctions-count[count()] function to count how many `Movie` nodes are connected to each `Person` node in this way, and uses a variable selector to project the value of the count. 
+It uses the xref::functions/aggregating.adoc#functions-count[count()] function to count how many `Movie` nodes are connected to each `Person` node in this way, and uses a variable selector to project the value of the count. 
 
 .Query
 [source, cypher]
diff --git a/modules/ROOT/pages/values-and-types/property-structural-composite.adoc b/modules/ROOT/pages/values-and-types/property-structural-composite.adoc
@@ -8,6 +8,7 @@ Cypher provides first class support for a number of data value types.
 These fall into the following three categories: *property*, *structural*, and *composite*. 
 This section will first provide a brief overview of each type, and then go into more detail about the property data type. 
 
+[[property-types]]
 == Property types
 
 A property type value is one that can be stored as a node or relationship property.
diff --git a/modules/ROOT/pages/values-and-types/spatial.adoc b/modules/ROOT/pages/values-and-types/spatial.adoc
@@ -28,9 +28,6 @@ Values with the `Point` type have the following characteristics:
 This means it contains either 2 or 3 64-bit floating point values, which together are called the _Coordinate_.
 * Each point will also be associated with a specific xref::values-and-types/spatial.adoc#spatial-values-crs[Coordinate Reference System] (CRS) that determines the meaning of the values in the _Coordinate_.
 * Instances of `Point` and lists of `Point` can be assigned to node and relationship properties.
-* Nodes and relationships with `Point` or `List(Point)` properties can be indexed using a xref::indexes-for-search-performance.adoc#indexes-create-a-node-point-index
-[point index]. 
-This is true for all CRSs (and for both 2D and 3D).
 * The xref::functions/spatial.adoc#functions-distance[distance function] will work on points in all CRS and in both 2D and 3D, but only if the two points have the same CRS (and therefore also same dimension).
 
 
