Update external xrefs to links and fix table (#203)

Author: recrwplay

modules/ROOT/pages/access-control/built-in-roles.adoc

@@ -361,7 +361,7 @@ SHOW ROLE admin PRIVILEGES AS COMMANDS
 a|Rows: 11
 |===
 
-If the built-in `admin` role has been altered or dropped, and needs to be restored to its original state, see xref:4.4@operations-manual:ROOT:configuration/password-and-user-recovery/index.adoc[Operations Manual -> Password and user recovery].
+If the built-in `admin` role has been altered or dropped, and needs to be restored to its original state, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/configuration/password-and-user-recovery[Operations Manual -> Password and user recovery].
 
 
 [[access-control-built-in-roles-admin-recreate]]
@@ -413,4 +413,4 @@ GRANT ALL ON DATABASE * TO admin
 
 The resulting `admin` role now has the same privileges as the original built-in `admin` role.
 
-Additional information about restoring the `admin` role can be found at xref:4.4@operations-manual:ROOT:configuration/password-and-user-recovery/index.adoc#recover-admin-role[Operations Manual -> Recover the admin role].
+Additional information about restoring the `admin` role can be found at link:{neo4j-docs-base-uri}/operations-manual/{page-version}/configuration/password-and-user-recovery#recover-admin-role[Operations Manual -> Recover the admin role].

modules/ROOT/pages/access-control/manage-roles.adoc

@@ -361,7 +361,7 @@ By default it gives access to the home database and to execute privileges for pr
 1+a|Rows: 6
 |===
 
-More information about the built-in roles can be found in xref:4.4@operations-manual:ROOT:authentication-authorization/built-in-roles/index.adoc[Operations Manual -> Built-in roles].
+More information about the built-in roles can be found in link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/built-in-roles[Operations Manual -> Built-in roles].
 
 There are multiple versions of this command, the default being `SHOW ALL ROLES`.
 To only show roles that are assigned to users, the command is `SHOW POPULATED ROLES`.

modules/ROOT/pages/access-control/manage-users.adoc

@@ -113,8 +113,6 @@ GRANT SHOW PRIVILEGE
 
 (see xref::access-control/dbms-administration.adoc#access-control-dbms-administration-privilege-management[DBMS PRIVILEGE MANAGEMENT privileges])
 
-|===
-
 [source, privilege, role="noheader"]
 ----
 GRANT SHOW USER
@@ -187,8 +185,6 @@ GRANT CREATE USER
 
 (see xref::access-control/dbms-administration.adoc#access-control-dbms-administration-user-management[DBMS USER MANAGEMENT privileges])
 
-|===
-
 [source, privilege, role="noheader"]
 ----
 GRANT DROP USER
@@ -468,7 +464,7 @@ SHOW USERS
 |===
 
 When first starting a Neo4j DBMS, there is always a single default user `neo4j` with administrative privileges.
-It is possible to set the initial password using xref:4.4@operations-manual:ROOT:configuration/set-initial-password/index.adoc[neo4j-admin set-initial-password], otherwise it is necessary to change the password after the first login.
+It is possible to set the initial password using link:{neo4j-docs-base-uri}/operations-manual/{page-version}/configuration/set-initial-password[neo4j-admin set-initial-password], otherwise it is necessary to change the password after the first login.
 
 .Show user
 ======
@@ -536,7 +532,7 @@ Consequently, it is never possible to get the plaintext of a password back out o
 A password can be set in either fashion at any time.
 ** The optional `PLAINTEXT` in `SET PLAINTEXT PASSWORD` has the same behavior as `SET PASSWORD`.
 ** The optional `ENCRYPTED` is used to recreate an existing user when the plaintext password is unknown, but the encrypted password is available in the _data/scripts/databasename/restore_metadata.cypher_ file of a database backup.
-See xref:4.4@operations-manual:ROOT:backup-restore/restore-backup/index.adoc#restore-backup-example[Operations Manual -> Restore a database backup -> Example]. +
+See link:{neo4j-docs-base-uri}/operations-manual/{page-version}/backup-restore/restore-backup#restore-backup-example[Operations Manual -> Restore a database backup -> Example]. +
 With `ENCRYPTED`, the password string is expected to be in the format of `<encryption-version>`, `<hash>` or `<salt>`, where, for example:
 *** `0` is the first version and refers to the `SHA-256` cryptographic hash function with iterations `1`.
 *** `1` is the second version and refers to the `SHA-256` cryptographic hash function with iterations `1024`.
@@ -695,7 +691,7 @@ Consequently, it is never possible to get the plaintext of a password back out o
 A password can be set in either fashion at any time.
 ** The optional `PLAINTEXT` in `SET PLAINTEXT PASSWORD` has the same behavior as `SET PASSWORD`.
 ** The optional `ENCRYPTED` is used to update an existing user's password when the plaintext password is unknown, but the encrypted password is available in the _data/scripts/databasename/restore_metadata.cypher_ file of a database backup.
-See xref:4.4@operations-manual:ROOT:backup-restore/restore-backup/index.adoc#restore-backup-example[Operations Manual -> Restore a database backup -> Example]. +
+See link:{neo4j-docs-base-uri}/operations-manual/{page-version}/backup-restore/restore-backup#restore-backup-example[Operations Manual -> Restore a database backup -> Example]. +
 With `ENCRYPTED`, the password string is expected to be in the format of `<encryption-version>`,`<hash>` or `<salt>`, where, for example:
 *** `0` is the first version and refers to the `SHA-256` cryptographic hash function with iterations `1`.
 *** `1` is the second version and refers to the `SHA-256` cryptographic hash function with iterations `1024`.

modules/ROOT/pages/access-control/privileges-writes.adoc

@@ -126,7 +126,7 @@ DENY DELETE ON GRAPH * RELATIONSHIPS bar TO regularUsers
 [NOTE]
 ====
 Users with `DELETE` privilege, but restricted `TRAVERSE` privileges, will not be able to do `DETACH DELETE` in all cases.
-See xref:4.4@operations-manual:ROOT:authentication-authorization/access-control/index.adoc#detach-delete-restricted-user[Operations Manual -> Fine-grained access control] for more info.
+See link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/access-control#detach-delete-restricted-user[Operations Manual -> Fine-grained access control] for more info.
 ====
 
 
@@ -350,7 +350,7 @@ DENY WRITE ON GRAPH neo4j TO regularUsers
 [NOTE]
 ====
 Users with `WRITE` privilege but restricted `TRAVERSE` privileges will not be able to do `DETACH DELETE` in all cases.
-See xref:4.4@operations-manual:ROOT:authentication-authorization/access-control/index.adoc#detach-delete-restricted-user[Operations Manual -> Fine-grained access control] for more info.
+See link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/access-control#detach-delete-restricted-user[Operations Manual -> Fine-grained access control] for more info.
 ====
 
 

modules/ROOT/pages/aliases.adoc

@@ -19,7 +19,7 @@ Please note that the local alias will be resolved while executing the command.
 Privileges are defined on the database, and not the local alias.
 
 A remote alias can be used for connecting to a database of a remote Neo4j DBMS, use clauses, setting a user's home database and defining the access privileges to the remote database.
-Remote aliases requires configuration to safely connect to the remote target, which is described in xref:4.4@operations-manual:ROOT:manage-databases/remote-alias/index.adoc[Connecting remote databases].
+Remote aliases requires configuration to safely connect to the remote target, which is described in link:{neo4j-docs-base-uri}/operations-manual/{page-version}/manage-databases/remote-alias[Connecting remote databases].
 It is not possible to impersonate a user on the remote database or to execute an administration command on the remote database via a remote alias.
 
 Aliases can be created and managed using a set of Cypher administration commands executed against the `system` database.
@@ -151,7 +151,7 @@ A timeout of zero is treated as an infinite timeout and will be bound by the tim
 | Duration
 
 | Default value
-| xref:4.4@operations-manual:ROOT:reference/configuration-settings/index.adoc#config_dbms.routing.driver.connection.connect_timeout[dbms.routing.driver.connection.connect_timeout]
+| link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/configuration-settings#config_dbms.routing.driver.connection.connect_timeout[dbms.routing.driver.connection.connect_timeout]
 
 |===
 
@@ -171,7 +171,7 @@ It is recommended to set maximum lifetime to a slightly smaller value than the o
 Zero and negative values result in lifetime not being checked.
 
 | Default value
-| xref:4.4@operations-manual:ROOT:reference/configuration-settings/index.adoc#config_dbms.routing.driver.connection.max_lifetime[dbms.routing.driver.connection.max_lifetime]
+| link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/configuration-settings#config_dbms.routing.driver.connection.max_lifetime[dbms.routing.driver.connection.max_lifetime]
 
 |===
 
@@ -191,7 +191,7 @@ Negative values are allowed and result in unlimited acquisition timeout.
 Value of `0` is allowed and results in no timeout and immediate failure when connection is unavailable.
 
 | Default value
-| xref:4.4@operations-manual:ROOT:reference/configuration-settings/index.adoc#config_dbms.routing.driver.connection.pool.acquisition_timeout[dbms.routing.driver.connection.pool.acquisition_timeout]
+| link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/configuration-settings#config_dbms.routing.driver.connection.pool.acquisition_timeout[dbms.routing.driver.connection.pool.acquisition_timeout]
 
 |===
 
@@ -211,7 +211,7 @@ Negative values are allowed and result in unlimited pool.
 Value of `0` is not allowed.
 
 | Default value
-| xref:4.4@operations-manual:ROOT:reference/configuration-settings/index.adoc#config_dbms.routing.driver.connection.pool.max_size[dbms.routing.driver.connection.pool.max_size]
+| link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/configuration-settings#config_dbms.routing.driver.connection.pool.max_size[dbms.routing.driver.connection.pool.max_size]
 
 |===
 
@@ -228,7 +228,7 @@ Value of `0` is not allowed.
 One of `DEBUG`, `INFO`, `WARN`, `ERROR`, or `NONE`.
 
 | Default value
-| xref:4.4@operations-manual:ROOT:reference/configuration-settings/index.adoc#config_dbms.routing.driver.logging.level[dbms.routing.driver.logging.level]
+| link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/configuration-settings#config_dbms.routing.driver.logging.level[dbms.routing.driver.logging.level]
 
 |===
 
@@ -698,7 +698,7 @@ CREATE ALIAS `northwind` FOR DATABASE `northwind-graph-2020`
 === Creating remote database aliases
 
 Database aliases can also point to remote databases by providing an url and the credentials of a user on the remote Neo4j DBMS.
-See xref:4.4@operations-manual:ROOT:manage-databases/remote-alias/index.adoc[Connecting remote databases] for the necessary configurations.
+See link:{neo4j-docs-base-uri}/operations-manual/{page-version}/manage-databases/remote-alias[Connecting remote databases] for the necessary configurations.
 
 Creating remote aliases also allows `IF NOT EXISTS` and `OR REPLACE` clauses.
 Both check for any remote or local database aliases.

modules/ROOT/pages/clauses/call.adoc

@@ -47,10 +47,10 @@ Calling a `VOID` procedure in the middle of a larger query will simply pass on e
 [NOTE]
 ====
 Neo4j comes with a number of built-in procedures.
-For a list of these, see xref:4.4@operations-manual:ROOT:reference/procedures/index.adoc[Operations Manual -> Procedures].
+For a list of these, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/procedures[Operations Manual -> Procedures].
 
 Users can also develop custom procedures and deploy to the database.
-See xref:4.4@java-reference:ROOT:extending-neo4j/procedures.adoc#extending-neo4j-procedures[Java Reference -> User-defined procedures] for details.
+See link:{neo4j-docs-base-uri}/java-reference/{page-version}/extending-neo4j/procedures#extending-neo4j-procedures[Java Reference -> User-defined procedures] for details.
 ====
 
 

modules/ROOT/pages/clauses/delete.adoc

@@ -93,7 +93,7 @@ Relationships deleted: 2
 
 [NOTE]
 ====
-For `DETACH DELETE` for users with restricted security privileges, see xref:4.4@operations-manual:ROOT:authentication-authorization/access-control/index.adoc#detach-delete-restricted-user[Operations Manual -> Fine-grained access control].
+For `DETACH DELETE` for users with restricted security privileges, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/access-control#detach-delete-restricted-user[Operations Manual -> Fine-grained access control].
 ====
 
 

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

@@ -36,18 +36,18 @@
 * `LOAD CSV` is often used in conjunction with the query hint `PERIODIC COMMIT`; more information on this may be found in xref::query-tuning/using.adoc#query-using-periodic-commit-hint[[deprecated\]#`PERIODIC COMMIT` query hint].
 
 .Configuration settings for file URLs
-xref:4.4@operations-manual:ROOT:reference/configuration-settings/index.adoc#config_dbms.security.allow_csv_import_from_file_urls[dbms.security.allow_csv_import_from_file_urls]::
+link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/configuration-settings#config_dbms.security.allow_csv_import_from_file_urls[dbms.security.allow_csv_import_from_file_urls]::
 This setting determines if Cypher will allow the use of `+file:///+` URLs when loading data using `LOAD CSV`.
 Such URLs identify files on the filesystem of the database server.
 Default is _true_.
 Setting `dbms.security.allow_csv_import_from_file_urls=false` will completely disable access to the file system for `LOAD CSV`.
 
-xref:4.4@operations-manual:ROOT:reference/configuration-settings/index.adoc#config_dbms.directories.import[dbms.directories.import]::
+link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/configuration-settings#config_dbms.directories.import[dbms.directories.import]::
 Sets the root directory for `+file:///+` URLs used with the Cypher `LOAD CSV` clause.
 This should be set to a single directory relative to the Neo4j installation path on the database server.
 All requests to load from `+file:///+` URLs will then be relative to the specified directory.
 The default value set in the config settings is _import_.
-This is a security measure which prevents the database from accessing files outside the standard xref:4.4@operations-manual:ROOT:configuration/file-locations/index.adoc[import directory],
+This is a security measure which prevents the database from accessing files outside the standard link:{neo4j-docs-base-uri}/operations-manual/{page-version}/configuration/file-locations[import directory],
 similar to how a Unix `chroot` operates.
 Setting this to an empty field will allow access to all files within the Neo4j installation folder.
 Commenting out this setting will disable the security feature, allowing all files in the local system to be imported.
@@ -241,7 +241,7 @@ The xref::clauses/use.adoc[`USE` clause] can not be used together with the `PERI
 
 [NOTE]
 ====
-Queries with the `PERIODIC COMMIT` query hint can not be routed by xref:4.4@operations-manual:ROOT:clustering/internals/index.adoc#causal-clustering-routing[Server-side routing].
+Queries with the `PERIODIC COMMIT` query hint can not be routed by link:{neo4j-docs-base-uri}/operations-manual/{page-version}/clustering/internals#causal-clustering-routing[Server-side routing].
 ====
 
 .Query

modules/ROOT/pages/clauses/use.adoc

@@ -61,7 +61,7 @@ CALL {
 In subqueries, a `USE` clause may appear as the second clause, if directly following an xref::clauses/call-subquery.adoc#subquery-correlated-importing[importing `WITH` clause]
 
 When executing queries against a Fabric database, in addition to referring to databases in the DBMS, the `<graph>` may also refer to a graph mounted through the Fabric configuration.
-For more information, see xref:4.4@operations-manual:ROOT:fabric/index.adoc[Operations Manual -> Fabric].
+For more information, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/fabric[Operations Manual -> Fabric].
 
 
 [[query-use-examples]]

modules/ROOT/pages/databases.adoc

@@ -531,7 +531,7 @@ Subsequently, the database access mode can be switched back to read-write using
 Altering the database access mode is allowed at all times, whether a database is online or offline.
 
 Database access modes can also be managed using the configuration parameters `dbms.databases.default_to_read_only`, `dbms.databases.read_only`, and `dbms.database.writable`.
-For details, see xref:4.4@operations-manual:ROOT:manage-databases/configuration/index.adoc#manage-databases-parameters[Configuration parameters].
+For details, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/manage-databases/configuration#manage-databases-parameters[Configuration parameters].
 If conflicting modes are set by the `ALTER DATABASE` command and the configuration parameters, i.e. one says read-write and the other read-only, the database will be read-only and prevent write queries.