Update links with their redirects (#2458)

Author: stefano-ottolenghi

modules/ROOT/pages/authentication-authorization/built-in-roles.adoc

@@ -827,7 +827,7 @@ These include the rights to perform the following classes of tasks:
 
 * Manage xref:authentication-authorization/database-administration.adoc[database privileges] to control the rights to perform actions on specific databases:
 ** Manage access to a database and the right to start and stop a database.
-** Manage link:{neo4j-docs-base-uri}/cypher-manual/current/indexes-for-search-performance/[indexes] and link:{neo4j-docs-base-uri}/cypher-manual/current/constraints/[constraints].
+** Manage link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/search-performance-indexes/overview/[indexes] and link:{neo4j-docs-base-uri}/cypher-manual/current/constraints/[constraints].
 ** Allow the creation of labels, relationship types, or property names.
 ** Manage transactions.
 * Manage xref:authentication-authorization/dbms-administration.adoc[DBMS privileges] to control the rights to perform actions on the entire system:

modules/ROOT/pages/authentication-authorization/dbms-administration.adoc

@@ -72,7 +72,7 @@ CREATE ROLE serverViewer IF NOT EXISTS;
 
 All DBMS privileges are relevant system-wide.
 Like user management, they do not belong to one specific database or graph.
-For more details on the differences between graphs, databases, and the DBMS, refer to link:{neo4j-docs-base-uri}/cypher-manual/current/introduction/cypher_neo4j/[Cypher Manual -> Cypher and Neo4j].
+For more details on the differences between graphs, databases, and the DBMS, refer to link:{neo4j-docs-base-uri}/cypher-manual/current/introduction/cypher-neo4j/[Cypher Manual -> Cypher and Neo4j].
 
 image::privileges_grant_and_deny_syntax_dbms_privileges.svg[width="800", title="Syntax of GRANT and DENY DBMS privileges"]
 

modules/ROOT/pages/authentication-authorization/limitations.adoc

@@ -19,14 +19,14 @@ The known limitations and implications of Neo4j's role-based access control secu
 [[access-control-limitations-indexes]]
 == Security and indexes
 
-As described in link:{neo4j-docs-base-uri}/cypher-manual/current/indexes-for-search-performance/[Cypher Manual -> Indexes for search performance], Neo4j {neo4j-version} supports the creation and use of indexes to improve the performance of Cypher queries.
+As described in link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/search-performance-indexes/overview/[Cypher Manual -> Indexes for search performance], Neo4j {neo4j-version} supports the creation and use of indexes to improve the performance of Cypher queries.
 
 Note that the Neo4j security model impacts the results of queries, regardless if the indexes are used or not.
 When using non full-text Neo4j indexes, a Cypher query will always return the same results it would have if no index existed.
 This means that, if the security model causes fewer results to be returned due to restricted read access in xref:authentication-authorization/manage-privileges.adoc[Graph and sub-graph access control],
 the index will also return the same fewer results.
 
-However, this rule is not fully obeyed by link:{neo4j-docs-base-uri}/cypher-manual/current/indexes-for-full-text-search[Cypher Manual -> Indexes for full-text search].
+However, this rule is not fully obeyed by link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/semantic-indexes/full-text-indexes/[Cypher Manual -> Indexes for full-text search].
 These specific indexes are backed by _Lucene_ internally.
 It is therefore not possible to know for certain whether a security violation has affected each specific entry returned from the index.
 In face of this, Neo4j will return zero results from full-text indexes in case it is determined that any result might be violating the security privileges active for that query.
@@ -51,7 +51,7 @@ CREATE FULLTEXT INDEX userNames FOR (n:User|Person) ON EACH [n.name, n.surname];
 [NOTE]
 ====
 Full-text indexes support multiple labels.
-See link:{neo4j-docs-base-uri}/cypher-manual/current/indexes-for-full-text-search/[Cypher Manual -> Indexes for full-text search] for more details on creating and using full-text indexes.
+See link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/semantic-indexes/full-text-indexes//[Cypher Manual -> Indexes for full-text search] for more details on creating and using full-text indexes.
 ====
 
 After creating these indexes, it would appear that the latter two indexes accomplish the same thing.

modules/ROOT/pages/authentication-authorization/load-privileges.adoc

@@ -14,7 +14,7 @@ CREATE ROLE roleLoadCidr
 This section explains how to use Cypher to manage load privileges.
 All load privileges apply to the whole system.
 Like DBMS privileges, they do not belong to one specific database or graph.
-For more details on the differences between graphs, databases, and the DBMS, refer to link:{neo4j-docs-base-uri}/cypher-manual/current/introduction/cypher_neo4j/[Cypher Manual -> Cypher and Neo4j].
+For more details on the differences between graphs, databases, and the DBMS, refer to link:{neo4j-docs-base-uri}/cypher-manual/current/introduction/cypher-neo4j/[Cypher Manual -> Cypher and Neo4j].
 
 image::privileges_grant_and_deny_syntax_load_privileges.svg[width="800", title="Syntax of GRANT and DENY load Privileges"]
 

modules/ROOT/pages/backup-restore/online-backup.adoc

@@ -56,7 +56,7 @@ For more information, see xref:backup-restore/online-backup.adoc#online-backup-c
 
 [NOTE]
 ====
-`neo4j-admin database backup` is not supported in link:https://neo4j.com/cloud/aura/[Neo4j Aura].
+`neo4j-admin database backup` is not supported in link:https://neo4j.com/product/auradb/[Neo4j Aura].
 ====
 
 [[backup-command-syntax]]

modules/ROOT/pages/cloud-deployments/neo4j-gcp.adoc

@@ -27,7 +27,7 @@ The Neo4j Deployment Manager template takes several parameters as inputs, deploy
 === Important considerations
 
 * The deployment of cloud resources incurs costs.
-** Refer to the link:https://cloud.google.com/products/calculator/[GCP pricing calculator]for more information.
+** Refer to the link:https://cloud.google.com/products/calculator[GCP pricing calculator]for more information.
 
 * The Neo4j Deployment Manager template deploys a new VPC, containing a single subnet based in the requested region.
 ** Unlike Azure and AWS where subnets are aligned to specific zones, GCP subnets are regional (and VPCs are global).

modules/ROOT/pages/clustering/clustering-advanced/multi-data-center-routing.adoc

@@ -145,7 +145,7 @@ Please contact Neo4j Professional Services if you think that you need a custom p
 .Use load balancing from Neo4j drivers
 ====
 Once enabled and configured, the custom load balancing feature is used by drivers to route traffic as intended.
-See the link:{neo4j-docs-base-uri}/drivers-apis/[Neo4j Drivers manuals] for instructions on how to configure drivers to use custom load balancing.
+See the link:{neo4j-docs-base-uri}/create-applications/[Neo4j Drivers manuals] for instructions on how to configure drivers to use custom load balancing.
 ====
 
 

modules/ROOT/pages/configuration/configuration-settings.adoc

@@ -2262,7 +2262,7 @@ m|+++2097152+++
 [frame="topbot", stripes=odd, grid="cols", cols="<1s,<4"]
 |===
 |Description
-a|Selects whether to conform to the standard https://tools.ietf.org/html/rfc4180 for interpreting escaped quotation characters in CSV files loaded using `LOAD CSV`. Setting this to `false` will use the standard, interpreting repeated quotes '""' as a single in-lined quote, while `true` will use the legacy convention originally supported in Neo4j 3.0 and 3.1, allowing a backslash to include quotes in-lined in fields.
+a|Selects whether to conform to the standard https://datatracker.ietf.org/doc/html/rfc4180 for interpreting escaped quotation characters in CSV files loaded using `LOAD CSV`. Setting this to `false` will use the standard, interpreting repeated quotes '""' as a single in-lined quote, while `true` will use the legacy convention originally supported in Neo4j 3.0 and 3.1, allowing a backslash to include quotes in-lined in fields.
 |Valid values
 a|A boolean.
 |Default value

modules/ROOT/pages/configuration/plugins.adoc

@@ -66,12 +66,12 @@ The following plugins are supported:
 | Neo Semantics
 | `n10s`
 |
-| link:https://neo4j.com/labs/nsmtx-rdf/[Neo Semantics]
+| link:https://neo4j.com/labs/neosemantics/[Neo Semantics]
 |===
 
 For more information on using plugins in a different Neo4j setup, see:
 
-* link:{neo4j-docs-base-uri}/desktop-manual/current/operations/instance-management/#_install_plugins[Neo4j Desktop -> Install a plugin]
+* link:{neo4j-docs-base-uri}/desktop/current/operations/instance-management/#_install_plugins[Neo4j Desktop -> Install a plugin]
 * xref:docker/plugins.adoc[Docker -> Plugins]
 * xref:/kubernetes/plugins.adoc[Kubernetes -> Plugins]
 * link:{neo4j-docs-base-uri}/java-reference/{page-version}/extending-neo4j/project-setup/#_build_dependencies[Java-Reference -> Setting up a plugin project].

modules/ROOT/pages/database-administration/composite-databases/querying-composite-databases.adoc

@@ -7,7 +7,7 @@
 //Make an image that sets up the example?
 //The query examples assume that we have a setup similar to that in <<example-create-a-single-instance-fabric-setup>>.
 
-The examples featured in this section make use of the two Cypher clauses: link:{neo4j-docs-base-uri}/cypher-manual/current/clauses/use[`USE`] and link:{neo4j-docs-base-uri}/cypher-manual/current/clauses/call-subquery[`CALL {}`].
+The examples featured in this section make use of the two Cypher clauses: link:{neo4j-docs-base-uri}/cypher-manual/current/clauses/use[`USE`] and link:{neo4j-docs-base-uri}/cypher-manual/current/subqueries/call-subquery/[`CALL {}`].
 
 [[composite-databases-queries-graph-set-up]]
 == Graph set-up