Fix links

modules/ROOT/pages/appendix/gql-conformance/index.adoc

@@ -43,7 +43,7 @@ Following the GQL Standard subclause 24.2, _Minimum conformance_, Cypher’s sup
 * The Unicode Standard version used by Cypher depends on the running JVM version.
 Neo4j 5 added support for JavaSE 17 and version 13 of The Unicode Standard.
 Neo4j 5.14 added support for JavaSE 21 and version 15 of the Unicode Standard.
-For more information, see xref:syntax/parsing.adoc##_using_unicodes_in_cypher[Parsing -> Using Unicode in Cypher].
+For more information, see xref:syntax/parsing.adoc#_using_unicodes_in_cypher[Parsing -> Using Unicode in Cypher].
 * Cypher supports the following mandatory GQL property types: `BOOLEAN` (`BOOL`), `FLOAT` footnote:[The `FLOAT` type in Cypher always represents a 64-bit double-precision floating point number.], `INTEGER` (`SIGNED INTEGER`, or `INT`)footnote:[The `INTEGER` type in Cypher always represents a 64-bit `INTEGER`.], and `STRING` (`VARCHAR`).
 +
 Cypher also supports the following optional GQL property types: `DATE`, `DURATION`, `LIST<INNER_TYPE NOT NULL>` (`ARRAY<INNER_TYPE NOT NULL>`, `INNER_TYPE LIST`, or `INNER_TYPE ARRAY`)footnote:[The `INNER_TYPE` cannot be a `LIST` type.], `LOCAL DATETIME` (`TIMESTAMP WITHOUT TIME ZONE`), `LOCAL TIME` (`TIME WITHOUT TIME ZONE`), `POINT`, `ZONED DATETIME` (`TIME WITH TIME ZONE`), and `ZONED TIME` (`TIMESTAMP WITH TIME ZONE`).

modules/ROOT/pages/appendix/gql-conformance/supported-mandatory.adoc

@@ -212,7 +212,7 @@ For example: `MATCH (n) RETURN n."a prop"` is allowed in GQL but not Cypher.
 
 | 22.15
 | Grouping operations
-| xref:functions/aggregating.adoc##counting_with_and_without_duplicates[Counting with and without duplicates]
+| xref:functions/aggregating.adoc#counting_with_and_without_duplicates[Counting with and without duplicates]
 |
 
 |===

modules/ROOT/pages/appendix/gql-conformance/supported-optional.adoc

@@ -15,7 +15,7 @@ These codes order the features in the table below.
 
 | G002
 | Different-edges match mode
-| xref:patterns/reference.adoc#/#graph-patterns-rules-relationship-uniqueness[Relationship uniqueness in Cypher]
+| xref:patterns/reference.adoc#graph-patterns-rules-relationship-uniqueness[Relationship uniqueness in Cypher]
 | The semantic for this feature is the default Cypher semantic.
 
 | G004

modules/ROOT/pages/clauses/call.adoc

@@ -12,9 +12,9 @@ For information about how to list procedures, see xref:clauses/listing-procedure
 
 [NOTE]
 Neo4j comes with a number of built-in procedures.
-For a list of these, see link:{neo4j-docs-base-uri}/operations-manual/current/reference/procedures[Operations Manual -> Procedures].
+For a list of these, see link:{neo4j-docs-base-uri}/operations-manual/current/procedures[Operations Manual -> Procedures].
 Users can also develop custom procedures and deploy to the database.
-See link:{neo4j-docs-base-uri}/java-reference/current/extending-neo4j/procedures#extending-neo4j-procedures[Java Reference -> User-defined procedures] for details.
+See link:{neo4j-docs-base-uri}/java-reference/current/extending-neo4j/procedures/[Java Reference -> User-defined procedures] for details.
 
 [[example-graph]]
 == Example graph
@@ -42,7 +42,7 @@ CREATE (andy:Developer {name: 'Andy', born: 1991}),
 .`CALL` a procedure without arguments
 ====
 
-This example calls the built-in procedure link:{neo4j-docs-base-uri}/operations-manual/current/reference/procedures/#procedure_db_labels[`db.labels()`], which lists all labels used in the database.
+This example calls the built-in procedure link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_labels[`db.labels()`], which lists all labels used in the database.
 
 .Query
 [source, cypher]
@@ -72,7 +72,7 @@ Omission of parentheses is available only in a so-called standalone procedure ca
 ====
 
 
-This example calls the procedure link:{neo4j-docs-base-uri}/operations-manual/current/reference/procedures/#procedure_dbms_checkconfigvalue[`dbms.checkConfigValue()`], which checks the validity of a configuration setting value, using literal arguments.
+This example calls the procedure link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_dbms_checkconfigvalue[`dbms.checkConfigValue()`], which checks the validity of a configuration setting value, using literal arguments.
 
 .Query
 [source, cypher]
@@ -206,7 +206,7 @@ RETURN count(*) AS results
 ====
 
 `YIELD` can be used to filter for specific results.
-This requires knowing the names of the arguments within a procedure's signature, which can either be found in the link:{neo4j-docs-base-uri}/operations-manual/current/reference/procedures/[Operations Manual -> Procedures] or in the `signature` column returned by a `SHOW PROCEDURES` command (see example below).
+This requires knowing the names of the arguments within a procedure's signature, which can either be found in the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/[Operations Manual -> Procedures] or in the `signature` column returned by a `SHOW PROCEDURES` command (see example below).
 
 .Find the argument names of `db.propertyKeys`
 [source, cypher]

modules/ROOT/pages/clauses/listing-procedures.adoc

@@ -246,7 +246,7 @@ SHOW PROCEDURES
 |===
 
 The above table only displays the first 15 results of the query.
-For a full list of all built-in procedures in Neo4j, visit the link:{neo4j-docs-base-uri}/operations-manual/current/reference/procedures#/#_list_of_procedures[Operations Manual -> List of procedures].
+For a full list of all built-in procedures in Neo4j, visit the link:{neo4j-docs-base-uri}/operations-manual/current/procedures[Operations Manual -> Procedures].
 
 == Listing procedures with filtering on output columns
 
@@ -285,7 +285,7 @@ WHERE admin
 |===
 
 The above table only displays the first 15 results of the query.
-For a full list of all procedures which require `admin` privileges in Neo4j, visit the link:{neo4j-docs-base-uri}/operations-manual/current/reference/procedures#/#_list_of_procedures[Operations Manual -> List of procedures].
+For a full list of all procedures which require `admin` privileges in Neo4j, visit the link:{neo4j-docs-base-uri}/operations-manual/current/procedures[Operations Manual -> Procedures].
 
 == Listing procedures with other filtering
 

modules/ROOT/pages/clauses/load-csv.adoc

@@ -95,9 +95,9 @@ It also follows redirects, except those changing the protocol (for security reas
 [IMPORTANT]
 ====
 It is strongly recommended to permit resource loading only over secure protocols such as HTTPS instead of insecure protocols like HTTP. 
-This can be done by limiting the link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/load-privileges/#access-control-load-cidr/[load privileges] to only trusted sources that use secure protocols. 
+This can be done by limiting the link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/load-privileges/#access-control-load-cidr[load privileges] to only trusted sources that use secure protocols. 
 If allowing an insecure protocol is absolutely unavoidable, Neo4j takes measures internally to enhance the security of these requests within their limitations. 
-However, this means that insecure URLs on virtual hosts will not function unless you add the JVM argument `-Dsun.net.http.allowRestrictedHeaders=true` to the configuration setting link:{neo4j-docs-base-uri}/operations-manual/current/configuration/configuration-settings/#config_server.jvm.additional/[`server.jvm.additional`].
+However, this means that insecure URLs on virtual hosts will not function unless you add the JVM argument `-Dsun.net.http.allowRestrictedHeaders=true` to the configuration setting link:{neo4j-docs-base-uri}/operations-manual/current/configuration/configuration-settings/#config_server.jvm.additional[`server.jvm.additional`].
 ====
 
 

modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc

@@ -222,7 +222,8 @@ CREATE DATABASE db OPTIONS { seedCredentials: ...,  seedConfig: ... }
 ----
 | The `CREATE DATABASE` option `seedCredentials` has been deprecated.
 For seeding from cloud storage, it is recommended to use `CloudSeedProvider` which will read cloud credentials and configuration from standard locations.
-For further information, see link:{neo4j-docs-base-uri}/operations-manual/current/clustering/databases/#cloud-seed-provider[Managing databases in a cluster -> CloudSeedProvider].
+For further information, see link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/standard-databases/seed-from-uri/#cloud-seed-provider[Create a database from a URI -> CloudSeedProvider].
+
 
 a|
 label:functionality[]

modules/ROOT/pages/functions/index.adoc

@@ -752,12 +752,12 @@ There are two main types of functions that can be developed and used:
 | Scalar
 | For each row the function takes parameters and returns a result.
 | xref::functions/user-defined.adoc#query-functions-udf[Using UDF]
-| link:{neo4j-docs-base-uri}/java-reference/current/extending-neo4j/functions#extending-neo4j-functions[Extending Neo4j (UDF)]
+| link:{neo4j-docs-base-uri}/java-reference/current/extending-neo4j/functions/[Extending Neo4j (UDF)]
 
 | Aggregating
 | Consumes many rows and produces an aggregated result.
 | xref::functions/user-defined.adoc#query-functions-user-defined-aggregation[Using aggregating UDF]
-| link:{neo4j-docs-base-uri}/java-reference/current/extending-neo4j/aggregation-functions#extending-neo4j-aggregation-functions[Extending Neo4j (Aggregating UDF)]
+| link:{neo4j-docs-base-uri}/java-reference/current/extending-neo4j/aggregation-functions[Extending Neo4j (Aggregating UDF)]
 
 |===
 

modules/ROOT/pages/functions/user-defined.adoc

@@ -15,12 +15,12 @@ There are two main types of functions that can be developed and used:
 | Scalar
 | For each row the function takes parameters and returns a result.
 | xref::functions/user-defined.adoc#query-functions-udf[Using UDF]
-| link:{neo4j-docs-base-uri}/java-reference/current/extending-neo4j/functions#extending-neo4j-functions[Extending Neo4j (UDF)]
+| link:{neo4j-docs-base-uri}/java-reference/current/extending-neo4j/functions/[Extending Neo4j (UDF)]
 
 | Aggregating
 | Consumes many rows and produces an aggregated result.
 | xref::functions/user-defined.adoc#query-functions-user-defined-aggregation[Using aggregating UDF]
-| link:{neo4j-docs-base-uri}/java-reference/current/extending-neo4j/aggregation-functions#extending-neo4j-aggregation-functions[Extending Neo4j (Aggregating UDF)]
+| link:{neo4j-docs-base-uri}/java-reference/current/extending-neo4j/aggregation-functions/[Extending Neo4j (Aggregating UDF)]
 
 |===
 
@@ -30,7 +30,7 @@ There are two main types of functions that can be developed and used:
 
 For each incoming row the function takes parameters and returns a single result.
 
-For developing and deploying user-defined functions in Neo4j, see link:{neo4j-docs-base-uri}/java-reference/current/extending-neo4j/functions#extending-neo4j-functions[Extending Neo4j -> User-defined functions].
+For developing and deploying user-defined functions in Neo4j, see link:{neo4j-docs-base-uri}/java-reference/current/extending-neo4j/functions[Extending Neo4j -> User-defined functions].
 
 
 .Call a user-defined function

modules/ROOT/pages/genai-integrations.adoc

@@ -297,12 +297,12 @@ Supported values: +
 
 | taskType
 | STRING
-| The intended downstream application (see link:https://cloud.google.com/vertex-ai/generative-ai/docs/embeddings/get-text-embeddings#api_changes_to_models_released_on_or_after_august_2023[provider documentation]). The specified `taskType` will apply to all resources in a batch. label:new[Introduced in 5.19]
+| The intended downstream application (see link:https://cloud.google.com/vertex-ai/generative-ai/docs/embeddings/get-text-embeddings/[provider documentation]). The specified `taskType` will apply to all resources in a batch. label:new[Introduced in 5.19]
 |
 
 | title
 | STRING
-| The title of the document that is being encoded (see link:https://cloud.google.com/vertex-ai/generative-ai/docs/embeddings/get-text-embeddings#api_changes_to_models_released_on_or_after_august_2023[provider documentation]). The specified `title` will apply to all resources in a batch. label:new[Introduced in 5.19]
+| The title of the document that is being encoded (see link:https://cloud.google.com/vertex-ai/generative-ai/docs/embeddings/get-text-embeddings/[provider documentation]). The specified `title` will apply to all resources in a batch. label:new[Introduced in 5.19]
 |
 |===
 

modules/ROOT/pages/indexes/semantic-indexes/full-text-indexes.adoc

@@ -91,7 +91,7 @@ Removing stop words can help reduce the size of stored data and thereby improve
 In some cases, using different analyzers for the indexed values and query string is more appropriate.
 For example, if handling `STRING` values written in Swedish, it may be beneficial to select the `swedish` analyzer, which knows how to tokenize Swedish words, and will avoid indexing Swedish stop words.
 
-The link:{neo4j-docs-base-uri}/operations-manual/current/reference/procedures/#procedure_db_index_fulltext_listavailableanalyzers[`db.index.fulltext.listAvailableAnalyzers()`] procedure shows all available analyzers.
+The link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_fulltext_listavailableanalyzers[`db.index.fulltext.listAvailableAnalyzers()`] procedure shows all available analyzers.
 
 Neo4j also supports the use of custom analyzers.
 For more information, see the link:{neo4j-docs-base-uri}/java-reference/current/extending-neo4j/full-text-analyzer-provider[Java Reference Manual -> Full-text index analyzer providers].
@@ -135,7 +135,7 @@ For more information on how to configure full-text indexes, refer to the link:{n
 == Query full-text indexes
 
 Unlike xref:indexes/search-performance-indexes/managing-indexes.adoc[search-performance indexes], full-text indexes are not automatically used by the xref:planning-and-tuning/execution-plans.adoc[Cypher query planner].
-To query a full-text index, use either the link:{neo4j-docs-base-uri}/operations-manual/current/reference/procedures/#procedure_db_index_fulltext_querynodes[`db.index.fulltext.queryNodes`] or the link:{neo4j-docs-base-uri}/operations-manual/current/reference/procedures/#procedure_db_index_fulltext_relationships[`db.index.fulltext.queryRelationships`] procedure.
+To query a full-text index, use either the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_fulltext_querynodes[`db.index.fulltext.queryNodes`] or the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_fulltext_queryRelationships[`db.index.fulltext.queryRelationships`] procedure.
 
 [NOTE]
 An index cannot be used while its `state` is `POPULATING`, which occurs immediately after it is created.
@@ -363,19 +363,19 @@ The procedures for full-text indexes are listed in the table below:
 | Usage | Procedure/Command | Description
 
 | Eventually consistent indexes.
-| https://neo4j.com/docs/operations-manual/current/reference/procedures/#procedure_db_index_fulltext_awaiteventuallyconsistentindexrefresh[`db.index.fulltext.awaitEventuallyConsistentIndexRefresh`]
+| https://neo4j.com/docs/operations-manual/current/procedures/#procedure_db_index_fulltext_awaiteventuallyconsistentindexrefresh[`db.index.fulltext.awaitEventuallyConsistentIndexRefresh`]
 | Wait for the updates from recently committed transactions to be applied to any eventually-consistent full-text indexes.
 
 | List available analyzers.
-| https://neo4j.com/docs/operations-manual/current/reference/procedures/#procedure_db_index_fulltext_listavailableanalyzers[`db.index.fulltext.listAvailableAnalyzers`]
+| https://neo4j.com/docs/operations-manual/current/procedures/#procedure_db_index_fulltext_listavailableanalyzers[`db.index.fulltext.listAvailableAnalyzers`]
 | List the available analyzers that the full-text indexes can be configured with.
 
 | Use full-text node index.
-| https://neo4j.com/docs/operations-manual/current/reference/procedures/#procedure_db_index_fulltext_querynodes[`db.index.fulltext.queryNodes`]
+| https://neo4j.com/docs/operations-manual/current/procedures/#procedure_db_index_fulltext_querynodes[`db.index.fulltext.queryNodes`]
 | Query the given full-text index. Returns the matching nodes and their Lucene query score, ordered by score.
 
 | Use full-text relationship index.
-| https://neo4j.com/docs/operations-manual/current/reference/procedures/#procedure_db_index_fulltext_queryrelationships[`db.index.fulltext.queryRelationships`]
+| https://neo4j.com/docs/operations-manual/current/procedures/#procedure_db_index_fulltext_queryRelationships[`db.index.fulltext.queryRelationships`]
 | Query the given full-text index. Returns the matching relationships and their Lucene query score, ordered by score.
 
 |===