Change external xrefs to links

modules/ROOT/pages/introduction.adoc

@@ -9,7 +9,7 @@ Each HTTP request can include a list of statements, and for convenience you can
 
 The server guards against orphaned transactions by using a timeout.
 If there are no requests for a given transaction within the timeout period, the server will roll it back.
-You can configure the timeout in the server configuration, by setting xref:3.5@operations-manual:ROOT:reference/configuration-settings/index.adoc#config_dbms.rest.transaction.idle_timeout[Operations Manual -> Configuration settings `dbms.rest.transaction.idle_timeout`] to the number of seconds before timeout.
+You can configure the timeout in the server configuration, by setting link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/configuration-settings#config_dbms.rest.transaction.idle_timeout[Operations Manual -> Configuration settings `dbms.rest.transaction.idle_timeout`] to the number of seconds before timeout.
 The default timeout is `60` seconds.
 
 Responses from the HTTP API can be transmitted as JSON streams, resulting in better performance and lower memory overhead on the server side.
@@ -20,7 +20,7 @@ To use streaming, supply the header `X-Stream: true` with each request.
 * Literal line breaks are not allowed inside Cypher statements.
 * Open transactions are not shared among members of an HA cluster.
 Therefore, if you use this endpoint in an HA cluster, you must ensure that all requests for a given transaction are sent to the same Neo4j instance.
-* Cypher queries with `USING PERIODIC COMMIT` (see xref:3.5@cypher-manual:ROOT:query-tuning/using/index.adoc#query-using-periodic-commit-hint[Cypher Manual -> `PERIODIC COMMIT` query hint]) may only be executed when creating a new transaction and immediately committing it with a single HTTP request (see xref::/actions/begin-and-commit-a-transaction-in-one-request.adoc[Begin and commit a transaction in one request] for how to do that).
+* Cypher queries with `USING PERIODIC COMMIT` (see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/query-tuning/using#query-using-periodic-commit-hint[Cypher Manual -> `PERIODIC COMMIT` query hint]) may only be executed when creating a new transaction and immediately committing it with a single HTTP request (see xref::/actions/begin-and-commit-a-transaction-in-one-request.adoc[Begin and commit a transaction in one request] for how to do that).
 * When a request fails the transaction will be rolled back.
 By checking the result for the presence/absence of the `transaction` key you can figure out if the transaction is still open.
 ====
@@ -29,6 +29,6 @@ By checking the result for the presence/absence of the `transaction` key you can
 ====
 In order to speed up queries in repeated scenarios, try not to use literals but replace them with parameters wherever possible.
 This will let the server cache query plans.
-See xref:3.5@cypher-manual:ROOT:syntax/parameters/index.adoc#cypher-parameters[Cypher Manual -> Parameters] for more information.
+See link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/syntax/parameters#cypher-parameters[Cypher Manual -> Parameters] for more information.
 ====
 

modules/ROOT/pages/security/index.adoc

@@ -13,7 +13,7 @@ The functionality described in this section has been deprecated and will be remo
 [role=deprecated]
 == Introduction
 
-Authentication and authorization are enabled by default in Neo4j (refer to xref:3.5@operations-manual:ROOT:authentication-authorization/enable/index.adoc[Operations Manual -> Enabling authentication and authorization]).
+Authentication and authorization are enabled by default in Neo4j (refer to link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/enable[Operations Manual -> Enabling authentication and authorization]).
 This means that requests to the HTTP API must be authorized using the username and password of a valid user.
 
 When Neo4j is newly installed, the default user `neo4j` has the default password `neo4j`.